Pick by what may leave your network: from a gateway we run, to only the facts your policy needs, to nothing at all. Every model gives you the same verdicts and the same signed record, and starts in shadow mode.
Point your agent at a gateway we host, in Microsoft Azure Central US. Start in shadow mode, then turn on enforcement: your gateway holds your API credential in a key vault of its own and refuses what your policy does not allow. We keep no request or response body: only the verdict, the rule that decided it and a signed record.
Shadow mode and enforcement
Start with the hosted gateway →Run AgentSafe in your own network. Your credentials stay with you, and you choose whether a request body is evaluated or only its digest leaves.
Shadow mode and enforcement
Install AgentSafe →Run the decision service in your own cloud from our Helm chart, with your own Postgres, egress-only or fully air-gapped. Decisions, signed records and policy stay inside.
Shadow mode and enforcement, under a commercial licence
Ask for a self-managed licence →Headers, including Authorization and cookies, never reach the decision service in any model.
| Data | We run it | Your gateway, our decision | Everything in your environment |
|---|---|---|---|
| Your API credentials | In shadow mode, pass through our gateway in memory on each request and are never stored. With enforcement, your gateway holds them in a key vault of its own, readable only by its own processes. | Stay with you | Stay with you |
| Request and response bodies | A JSON request body up to 64 KiB is evaluated, a larger one only by its digest; never stored. Responses are never kept. | The same, or only the digest and the facts your policy names (set the embedded body limit to 0). Responses stay with you. | Stay with you |
| Method, path and query | Evaluated, and kept 30 days in your reports | Evaluated by our decision service | Stay with you |
| Signed Decision Dossiers | Held by us, exportable at any time | Held by us, exportable at any time | Held by you |
| Signing keys | Ours | Grant and dossier keys ours; your gateway's evidence key is yours | Grant keys in your own secret manager |
helm install decionis oci://<your-registry>/decionis \
--namespace decionis --create-namespace \
--set global.image.tag=<version> \
--set ingress.hosts[0].host=decionis.example.com
# then provide your database connection (the one required secret)
kubectl -n decionis create secret generic decionis-api-secrets \
--from-literal=DATABASE_URL='postgres://USER:PASS@HOST:5432/decionis'The chart and images come with a commercial licence. Ask for registry access.
Start from vertical policy packs and tune them yourself. Guardrails, kill criteria, and evidence requirements load as code — versioned, diffable, and editable for your role and company tier.
Grant exactly the scoped access a decision needs, nothing more. Connectors and the SDK use least-privilege, org-scoped credentials you issue and revoke.
Generate a policy pack from the diagnostic, run it in shadow mode where your data lives, and govern your first workflow without us touching your systems.