agno — Agent Frameworks

What is agno?

Agno is three layers you can adopt one at a time: a Python SDK for agents, teams and workflows; AgentOS, a FastAPI service that turns them into a REST API with sessions, JWT-scoped access, scheduling and OpenTelemetry traces written to a database you own; and a web control plane for watching runs. The first two are Apache-2.0 and run wherever containers run; apart from a usage ping you can switch off, nothing has to reach Agno. The control plane is the part that does not follow that rule — free against a runtime on your own machine, and a paid plan to point it at a deployed one. The project also moves quickly, with breaking changes in most minor releases, so pin a version before you build on it.

What can you do with agno?

An agent is a model, a set of tools and instructions — Twenty lines give you a working agent: choose a model, hand it tools such as a working folder or web search, write the instructions as prose, and run it. Responses stream to the terminal while you iterate on the wording.
Give it a database and the conversation survives the process — Attaching a database turns on sessions: runs grouped under a session ID and tied to a user ID, so earlier messages can be replayed into the next request. Memory goes further and extracts durable facts about each user that follow them into later conversations.
A knowledge base the agent decides when to search — Load files, URLs or raw text into a knowledge base backed by one of the supported vector databases. The default is what the docs call Agentic RAG — the agent searches when it judges it needs to, rather than context being injected on every turn — and agents can write new insights back into it.
Teams delegate, workflows follow a fixed path — A team has a leader that coordinates, routes or broadcasts work to members, each with its own role and tools. A workflow is the opposite: steps in a set order with loops, conditions and parallel branches. Agno's own docs are candid that a team costs extra model calls, latency and tokens.
AgentOS turns the agents you wrote into a service — Wrap them in AgentOS and you get a FastAPI app: a run endpoint per agent, team and workflow, streaming responses, JWT-checked permissions, a cron scheduler inside the same process, and execution traces written to your own database. Slack, Telegram and an MCP server are switches, not projects.
Context Providers keep the tool list short — Rather than mounting a dozen Slack tools next to a dozen Drive tools, each external system sits behind one read tool and one optional write tool, with a small sub-agent doing the actual calls. Agno's docs give the reason plainly: past twenty tools, models start picking the wrong one.

Before you choose agno

The SDK and AgentOS are Apache-2.0, but the control plane is Agno's hosted product: as of August 2026, free against an AgentOS on your machine, $150/month to connect a deployed one, self-hosted only on Enterprise.
Upgrades cost real work: v1 to v2 needed a database migration script, 8 of the 10 v2 minor releases through v2.9.0 shipped breaking changes, and a v3 alpha was tagged in August 2026.

Star history

17 Aug to 28 Aug · +213

41.7k42k

Frequently asked questions

Is agno free for commercial use?

agno is released under the Apache-2.0 licence — OSI-approved open source, which permits commercial use.

How can agno be deployed?

agno is available as Self-hosted / Runs locally.

Documentation

Reproduced from the agno-agi/agno README, published under Apache-2.0. Read the original ↗

Introduction

Agno is a framework and runtime for agent platforms. Build agents, run them as a service, manage your platform using a web UI.

Build your agent platform using the Agno SDK.
Run your agent platform using the AgentOS runtime.
Manage everything using the AgentOS UI.

Agno allows you to own your agent stack. Maintain control of your data, memory, and security posture (JWT-based RBAC), and turn your agent platform into a learning loop with simulations and usage data.

Get started

Hand this prompt to your coding agent (Claude Code, Cursor, Codex):

Help me set up my agent platform.

Clone https://github.com/agno-agi/agentos-railway into a folder called
agent-platform, cd in, read the README, and follow the get started guide.

Your coding agent will set up your agent platform and run it locally using Docker, giving you a REST API for serving your agents, a Postgres database for storing your data and traces, an MCP server, and a control plane.

Deploying somewhere else? Use the same prompt but point it to a different repo. The starter templates are identical except for the deploy scripts: swap agentos-railway for agentos-docker, agentos-aws, agentos-gcp, agentos-azure, agentos-fly, agentos-render, agentos-modal, or agentos-helm.

Prefer to code by hand?

Features

Production API. 50+ endpoints with SSE and websockets to build a product on top.
Storage. Store sessions, memory, knowledge, and traces in your own database.
100+ integrations. Connect to GitHub, Slack, Postgres, and more using pre-built toolkits.
Context Providers. Access live data from Slack, Drive, wikis, MCP, and custom sources.
Human approval. Pause runs for user confirmation. Block tools that require admin approval.
Observability. Monitor with OpenTelemetry tracing, run history, and audit logs.
Security. Get JWT-based RBAC and multi-user, multi-tenant isolation out of the box.
Interfaces. Expose your agents via Slack, Telegram, WhatsApp, Discord, AG-UI, A2A.
Scheduling. Cron-based scheduling and background jobs with no external infrastructure.
Deploy anywhere. Run on any cloud platform that runs containers. Docker, Railway, AWS, GCP.

Use Agno with your coding agent

Two options:

Recommended: Add Agno docs as an MCP server. Add docs.agno.com/mcp to your favourite coding agent.
Add Agno docs as an indexed source. In Cursor: Settings → Indexing & Docs → Add https://docs.agno.com/llms-full.txt. Also works in VSCode, Windsurf, and similar tools.

Read the full guide here.

Community

X: follow for releases and demos
Newsletter: monthly updates on what’s shipping

Telemetry

Agno sends a telemetry event per agent run so we know which model providers to prioritize. Prompts, messages, and outputs are never sent. Disable by setting AGNO_TELEMETRY=false.