Skip to main content
AgentOS runs agents, teams, and workflows as an API service. A production runtime needs to:
  1. Run components on demand through API requests or interfaces such as Slack and Telegram.
  2. Maintain sessions across minutes, days, or weeks.
  3. Preserve state across restarts, replicas, and infrastructure failures.
  4. Protect application routes from unauthenticated access.
  5. Record runs and actions for monitoring.
AgentOS serves native Agno components and adapters for the Claude Agent SDK, LangGraph, DSPy, and Antigravity. This minimal persistent deployment uses PostgreSQL for agent and runtime state:
my_app.py
This script starts a FastAPI application that can scale horizontally. The database persists sessions. Streaming is available by default; JWT authorization, tracing, and scheduling are optional AgentOS settings.

What the runtime gives you

The runtime covers the ground between your agent code and a production service: See Multi-framework support for adapter setup.

Explore

Agent API

Run your agent platform as an API.

Agent Storage

Add durability and persistence.

Observability

Tracing, run history, and audit logs in your own database.

Security and Auth

JWT validation, RBAC scopes, and per-request isolation.

Scheduling

In-process cron and multi-step workflows.

Interfaces

Reach users on Slack, Telegram, WhatsApp, A2A, and AG-UI.