Symbiont is the policy-governed runtime for AI agents. The open core — Cedar authorization, sandboxed execution, cryptographic tool verification — is Apache 2.0. Symbiont Enterprise adds the operational layer security teams need to deploy agents against sensitive systems: tamper-evident audit, human approval gates, and chat-platform adapters.
Everything below the API stays open. What enterprise adds is what you actually need to put an agent in front of a regulator, a CISO, or a customer.
Every policy decision — every permitted call, every denial, every approval — recorded into a hash-chained log. Replayable, exportable, and structured for the security team that has to answer the next question.
Mark sensitive actions in policy. The agent pauses; a human operator reviews the request — with the full call context — and approves or denies before execution proceeds. No silent privilege escalation.
Run an agent inside Slack, Microsoft Teams, or Mattermost. Approval requests, audit notifications, and operator interactions live where your team already does — not in another dashboard nobody opens.
Symbiont uses Cedar — AWS’s open authorization language — for every agent action. Policies are version-controlled, formally analyzable, and reviewed by your security team like any other infrastructure-as-code artifact.
Live view of every agent in the fleet — calls per minute, policy hits and denials, pending approvals, top tools, anomaly flags. Drill into any decision and replay the full audit trail with the exact policy that fired.
Plug the operator console into your IdP — SAML 2.0 or OIDC. Scope reviewer, approver, auditor, and admin roles separately so your incident-response process maps to the people who run it.
Self-hosted in your VPC, your Kubernetes cluster, or fully air-gapped on-prem. Your data never leaves your perimeter; the runtime, audit log, and policy store all live where your security team already governs.
Direct access to the engineers who build Symbiont. Production SLAs, long-term-supported releases with backported security patches, and policy-authoring workshops to get your first agent in production safely.
Same runtime, same primitives, same trust model. Enterprise is the operational layer on top — not a fork.
SchemaPin verifies every tool schema. AgentPin anchors agent identity to a domain. ToolClad declares what each tool does. Cedar enforces policy. The runtime is Rust-native, sandboxed, and Apache 2.0.
Enterprise wraps that with the operations layer required to run it in production: tamper-evident audit, human approval gates, real-time dashboards, SSO, private deployment, and engineering support — under a commercial license.
If yours isn’t here, email sales@thirdkey.ai — we’ll route you to a security engineer.
Model output is never treated as execution authority.