Get in touch
Let's scope a managed SAFi deployment.
We will discuss your environment, deployment requirements, security controls, expected usage and path to internal ownership, then provide a scoped estimate with a not-to-exceed cap for setup and a monthly figure for operations.
Request a quote
Tell us about your deployment
Only the first four fields are required. Everything below them helps us quote faster, but if you do not know the answers yet, leave them alone and say so in the message. Working them out with you is part of scoping.
Before you write
What helps us quote quickly
None of this is required to start a conversation, but the more of it you can answer, the sooner we can put a real number in front of you rather than a range.
If you do not know the answers yet, say so. Working them out with you is part of the scoping phase.
- Your environment. In-house Linux servers, or which cloud account, or whether you want us to recommend and size a host.
- Deployment preference. Docker or bare-metal, and any operating standards we need to meet.
- Expected usage. Roughly how many users, and how many governed turns a month.
- Model providers. Which AI providers you already have keys and approvals for.
- Security controls. Whether you need bastion access with session logging, and what your egress policy looks like.
- Support window. Business hours or extended coverage.
- Recovery objectives. How much downtime and data loss the agreement has to guarantee against.
- Path to ownership. Whether you want your team trained to take over, and roughly when.
What happens next
From first email to running deployment
-
A scoping conversation
We talk through your environment, security requirements and expected load. No obligation, and no pressure to decide on the call.
-
A written estimate
A setup estimate with a not-to-exceed cap, a monthly operating fee, and the SLA tier that fits, laid out in a statement of work and service agreement.
-
Your security review
You review the software, the access model and the agreement at your own pace. SAFi is open source, so your team can read every line of what we will run.
-
Deployment and go-live
The six-step onboarding, usually a few days end to end. Then monitoring starts and the SLA clock begins.
Want to look before you talk?
Run the live demo and try to make it break policy. That is what it is there to demonstrate. Then read the source and the developer guide.
You can also just run it yourself with Docker. If self-operating turns out to be straightforward for your team, that is a perfectly good outcome. The managed service exists for the cases where it is not.