A thin SDK over open contracts. Nothing you can't walk away from.
Every agent is a lean, standalone service. It speaks the open A2A standard and needs no AgentOS database to run.
What your engineers actually touch.
Bring the agent you already wrote
A thin SDK wraps your existing LangGraph or Agents-SDK service. No rewrite, no framework migration, no AgentOS database dependency.
pip install agentos-sdk One north-south governance contract
The platform governance API is the single public surface: identity, tenancy, policy, roles, skills, workflow lifecycle and observability reads.
POST /v1/orchestrate A2A and MCP, not a private protocol
Agents speak the open agent-to-agent standard over gRPC and HTTP, so they are portable in and portable out. Tool interfaces follow the same principle.
a2a:// agent.acme.internal Any Kubernetes, including yours
EKS, AKS, GKE or on-prem. Self-hosted and bring-your-own-cloud keep data entirely inside your environment.
helm install agentos ./chart Hard isolation, federated identity
A walled-off workspace per customer, OIDC federation to Okta or Entra, secrets in Vault, and authorization always re-derived on our side.
AGENTOS_IDENTITY_PROVIDER=okta Traces your existing stack can read
Governance-grade audit alongside ordinary telemetry — streamable to Datadog, Splunk or S3, correlated to the exact policy version that ran.
otel → datadog | splunk | s3