selfhost.directory

The index of self-hostable projects — ranked, categorized and served with live updates.
Own your data and stop giving it to big tech.

agno logo

Self-host agno

v3.1.12

Framework and runtime for self-hosted AI agent platforms

ReleaseOpen SourceApache-2.0
Updated2 weeks ago
LanguagePython
Setup difficultyModerate
Stars
43 169
Port
8000 (AgentOS REST API and MCP server (production))
Install with Docker Compose
AgentOS Control Plane dashboard with chat interface and monitoring

What is agno?

Agno provides a three-layer platform for AI agents: an SDK for building agents with multiple frameworks, a runtime (AgentOS) that serves agents as a secure API and MCP server, and a web-based Control Plane for monitoring and management. Self-hosted deployments use Docker Compose with PostgreSQL (pgvector) for persistence, featuring JWT-based RBAC, multi-tenant isolation, 100+ toolkit integrations, scheduling, OpenTelemetry observability, human-in-the-loop approvals, and chat interfaces for Slack, Telegram, WhatsApp, Discord, A2A, and AG-UI. Templates cover Docker, Kubernetes (Helm), Railway, AWS, GCP, Azure, Fly, Render, and Modal. A local quickstart runs on port 7777 with SQLite; production uses port 8000 with PostgreSQL and requires JWT verification keys.

Should you self-host agno?

agno scores 79/100 on selfhost.directory (how scoring works) and ranks #13 of 209 in AI Agents. It has 43 169 GitHub stars, +547 in the last 30 days.

It shipped 69 stable releases in the past year. The latest, v3.1.12, came out on 29 October 2026. New versions land roughly every 1 days.

Setup is moderate: expect some configuration beyond a single command. It is Apache-2.0-licensed and written mostly in Python.

Its closest alternative on selfhost.directory is Orca (91/100, 122 912 stars). It scores higher overall, so compare the two before you pick. See agno vs Orca side by side.

Features

  • 100+ Toolkit Integrations
  • Agent Evaluation
  • Agent Storage
  • Chat Interfaces
  • Context Providers
  • Control Plane UI
  • Human in the Loop
  • MCP Server
  • Multi-agent Teams
  • Multi-framework support
  • Observability
  • REST API
  • Scheduling
  • Security & Auth
  • Workflows

agno README

The self-managing agent platform

Introduction

Agno is a self-managing agent platform. Build agents for your company, product, or customers. Run them as durable services on AgentOS. Put them to work automating company operations.

How to install agno

Install agno with Docker Compose

Environment variables
OPENAI_API_KEY, JWT_VERIFICATION_KEY, AGENTOS_URL, MCP_CONNECT_SECRET, DB_PASS, SLACK_BOT_TOKEN, SLACK_SIGNING_SECRET, PARALLEL_API_KEY

git clone https://github.com/agno-agi/agentos-docker.git agentos cd agentos

cp example.env .env

Edit .env and set OPENAI_API_KEY

docker compose up -d --build

Local development with hot reload

How to configure agno

  • OPENAI_API_KEYKey for the default model (OpenAIResponses) and the default OpenAIEmbedder
  • JWT_VERIFICATION_KEYPublic key or shared secret for JWT verification
  • JWT_JWKS_FILEPath to a JWKS file. Alternative to JWT_VERIFICATION_KEY
  • RUNTIME_ENVdevRuntime environment (dev or prd)

    values: dev, prd

  • AGNO_TELEMETRYtrueSet to false to disable telemetry for agents, teams, workflows

    values: true, false

agno releases & version history

@ Every self-hosted release, weekly

One Monday email with the week's stable releases across the directory.

FAQ

What is the default model in Agno?

The default model is OpenAIResponses which requires OPENAI_API_KEY.

What environment variables does Agno read?

Agno reads provider API keys (OPENAI_API_KEY, ANTHROPIC_API_KEY, GOOGLE_API_KEY, GROQ_API_KEY), AgentOS security keys (OS_SECURITY_KEY, JWT_VERIFICATION_KEY, JWT_JWKS_FILE), CLI settings (AGENTOS_URL, AGNO_ADMIN_TOKEN), and debug flags (AGNO_DEBUG, AGNO_TELEMETRY).

More in AI Agents

Rate this project

Click to rate — no account needed.

0 comments

Posting as guest
Loading comments…