Enterprise
The governance gate, run at organization scale.
Same open-source gate — no gated build — plus the controls an organization needs around it: SSO and SCIM provisioning, org-wide RBAC, audit-grade retention, deployment in your VPC or fully air-gapped, and a contract that stands behind it with SLAs. BAAs and DPAs available.
Deployment
Your boundary decides the model. All three keep your data inside it.
There is no AnchorGate cloud that sees your traffic — that is a design decision, not a roadmap gap. The only question is who operates the stack and where.
Managed in your cloud
single-tenant, run by us
We operate the full stack inside your AWS, GCP, or Azure account. You get the gate without the pager; your prompts, PII, and ledger never cross your network boundary.
- Private tenancy — no shared control plane, no pooled infrastructure
- Data isolation — ledger and telemetry live in your account
- Bring your own encryption keys via your cloud KMS
Hybrid
your data plane, our control plane
AnchorProxy and the evidence ledger run in your network; we manage the control plane. Requests and PII stay inside your boundary — only policy bundles and posture metadata cross it.
- Token traffic never leaves your VPC
- Managed policy compilation, upgrades, and posture reporting
- The default when residency rules are strict but ops capacity is thin
Air-gapped on-prem
fully offline
Every component — proxy, engine, dashboard, ledger — deployed inside your infrastructure with no egress at all. Trust Packets verify offline by design, so the evidence story survives the air gap.
- No phone-home, no external dependencies at runtime
- Offline updates delivered as signed bundles
- Signed evidence verifiable without ever calling us
Access control
Who can do what, decided once, enforced everywhere.
Identity comes from your IdP, authority is scoped per workspace, and spend is capped at the gate — the same place policy is enforced.
SSO and SCIM provisioning
Sign-in through Okta, Azure AD / Entra ID, or any SAML / OIDC provider, with JWT auth for service-to-service calls. SCIM keeps seats in step with your directory: deprovision someone in the IdP and their access at the gate is gone with them.
RBAC over orgs and workspaces
Roles are scoped per workspace inside an organization hierarchy, and policy authoring is separated from policy approval — nobody reviews their own rules. Admin actions land on the same audit trail as everything else.
Budgets and rate limits
Spend budgets and rate limits set per organization, workspace, team, or key — enforced at the gate, not reconciled after the invoice arrives. Caps are hard by default; you choose where soft warnings are enough.
Key management and network controls
Provider credentials stay vaulted; teams get scoped virtual keys you can issue, rotate, and revoke individually. IP and geo allowlists decide which networks may reach the gate at all.
Audit & data
Every admin action on the same signed ledger as every request.
The gate already keeps a signed record of what your agents did. Enterprise extends that discipline to the humans operating it — who changed which policy, who granted which role, who rotated which key — with retention and export on your terms.
- Org-wide audit logs — every policy change, role grant, and key action recorded
- Custom retention windows for logs, traces, and decision evidence
- Scheduled export to your data lake — S3, GCS, or warehouse
- Bring-your-own encryption keys for evidence at rest
- Admin APIs — automate the control plane from your own tooling
Compliance
Evidence mapped to frameworks — not badges on a footer.
Compliance conversations go faster when the answers are mechanisms. These are the three that carry an enterprise security review.
Control catalogues, computed
Posture against the EU AI Act, ISO/IEC 42001, and SOC 2 control catalogues is computed from signed decision evidence — what your gates actually did, not what a policy PDF says they should do.
Your boundary, your scope
Self-hosted and air-gapped deployment means prompts and PII never leave your network. That is the fact that actually shortens GDPR and HIPAA scoping conversations — not a badge in a footer.
The paperwork
BAAs and DPAs signed on Enterprise agreements, plus working sessions for your security questionnaires and architecture reviews. Bring the ugly spreadsheet; it is usually the fastest path to a yes.
The relationship
A contract that stands behind the gate.
The software is open source either way. What Enterprise adds is people and paper: guaranteed response, a named engineer, and commitments you can hold us to.
SLAs in the contract
Response-time SLAs on support, and uptime SLAs where we operate the deployment. Written down and signed — accountability is the product here.
Dedicated onboarding
A named engineer works your rollout: verify-mode first, policy authoring with your GRC team, then the flip to fail-closed enforcement when the numbers say you are ready.
Priority 24/7 support
A private channel with the people who build the gate, around the clock for incidents. Escalation paths are defined before you need them, not during.
A seat at the roadmap
Enterprise requirements are weighted in planning the same way design-partner requirements are today. What ships, ships to open source — never features taken back.
Built on the same six pillars
Policy Enforcement
A deterministic policy DSL — IF condition THEN redact, alert, or block — compiled, human-approved, and evaluated before a request leaves. No LLM judging LLMs: the same input always gets the same verdict.
Learn more →
PII Redaction
SSNs, emails, Luhn-validated card numbers, and phone numbers stripped inline — before the request reaches any model provider. Responses and streamed output are scanned too.
Learn more →
MCP Security
Deny-by-default: exact-string target allowlists (wildcards deliberately unsupported), shell invocations rejected outright, and single-use task-bound tokens that burn on first use.
Learn more →
Signed Evidence
Every decision signed with ECDSA P-256 over RFC 8785 canonical JSON, appended to an immutable ledger, graded L1–L5. An auditor can replay who acted, what was touched, and which policy fired.
Learn more →
Compliance Posture
Control catalogues for the EU AI Act, ISO/IEC 42001, and SOC 2 map directly onto decision evidence. Posture is computed from what the gates actually did — not from a policy document.
Learn more →
Shadow-AI Discovery
Feed it DNS and HTTP egress logs and it inventories calls to 16+ AI provider domains — surfacing the copilots and scripts nobody registered. You can’t govern traffic you can’t see.
Learn more →
FAQ
Enterprise questions, answered plainly
- Can AnchorGate run fully air-gapped?
- Yes. Every component — proxy, engine, dashboard, ledger — deploys inside your infrastructure with no egress, and updates arrive as signed offline bundles. The evidence model was built for this: Trust Packets verify offline, so an auditor can check signatures without anything ever calling us.
- Which identity providers does SSO support?
- Okta and Azure AD / Entra ID are the well-trodden paths, and any SAML or OIDC provider works. SCIM provisioning keeps seats synchronized with your directory, and JWT authentication covers service-to-service access. Deprovisioning in the IdP removes access at the gate — there is no separate user list to forget about.
- Do you sign BAAs and DPAs?
- Yes, on Enterprise agreements. Worth knowing before that conversation: in self-hosted and air-gapped deployments your prompts, PII, and evidence never reach us at all, which tends to make the data-processing discussion short.
- Is the Enterprise build different from the open-source one?
- No — there is no gated build. Enterprise is the same gate plus what an organization needs around it: SSO and SCIM, org-wide RBAC, audit retention and export, deployment options, and a contract with SLAs. What ships as open source stays open source.
- Are you SOC 2 or ISO 27001 certified?
- We won’t claim certifications we don’t hold — over-claiming is exactly what this product exists to prevent. What AnchorGate gives you is your own posture: control catalogues for SOC 2, ISO/IEC 42001, and the EU AI Act computed from signed decision evidence. And because the deployment is self-hosted, our certification status matters far less than usual — your data never reaches us.
Bring us your security review.
Enterprise conversations here start with the questionnaire, not a demo script. Send the spreadsheet, the residency constraints, and the deployment you actually need — we'll come back with mechanisms, not adjectives.
Talk to usor email hello@anchorgate.ai