Agentic Index
Agno vs Letta (2026)
Both vendors last verified
Choose Agno for a general purpose high performance agent runtime. That verdict is the Agentic Index coverage score, graded from each vendor's own published materials.
Choose Letta when persistent, inspectable memory is the defining requirement. Agno runs on a free plan or Pro from $150 a month under Apache 2.0, and Letta's ladder goes from a free tier to Pro and the API plan at $20 a month each, the API plan billed by usage on top, with self hosting free. Letta now ships Letta Agent and Letta Code beside its Agent SDK and self hosted App Server.
On the Agentic Index agent infrastructure ranking, Agno clears the bar and Letta does not. Agno documents all five production contract capabilities in full; Letta documents two of the five in full. 33 of the 186 vendors in the lane clear it. See the agent infrastructure ranking
This comparison is published by Agentic Index, an independent agentic AI vendor research platform. Agno and Letta are each graded against the same 14 capability Agentic Index taxonomy, from the vendor's own public materials under the Agentic Index verification standard, alongside 1,165 researched vendors. No vendor pays for placement and no vendor has reviewed this page. How this evidence is graded
Choose Agno if
- You want a fast, straightforward runtime for many kinds of agents
- Multi agent coordination with built in memory covers your state needs
- Predictable plan pricing beats metered credit consumption for your usage
Choose Letta if
- Agents that remember, learn, and persist across sessions are the product
- You want to inspect and edit agent memory state directly rather than trust a black box
- The MemGPT research lineage and stateful architecture match your technical bet
| Feature | A Agno |
L Letta |
|---|---|---|
| Action & orchestration | ||
|
Integrations & Tool Calling Ability to connect agents to real systems through native integrations, OAuth-authenticated actions, custom tools, APIs, webhooks, or MCP-compatible tools. |
||
|
AgnoIntegrations & Tool Calling The Agno SDK ships more than 100 toolkits, alongside MCP tools and custom tools that agents call to act in outside systems. SourceAgno, agno.com homepage and docs.agno.com/tools/mcpread 2026-09-21 |
||
|
LettaIntegrations & Tool Calling Agents connect to stdio, HTTP and SSE MCP servers, take controller-owned external tools registered on the App Server, use reusable skills, and reach GitHub repositories and Slack through native integrations. SourceLetta, docs.letta.com/agent-sdk/mcp and self-hosting/app-server/external-toolsread 2026-09-21 |
||
|
Workflow Orchestration Ability to sequence, branch, retry, route, and combine deterministic workflow nodes with autonomous agent steps. |
||
|
AgnoWorkflow Orchestration The SDK gives three patterns, agents, teams that delegate across member agents, and workflows that run ordered steps with loops, parallel branches and approval gates, so deterministic steps and agent steps combine in one run. SourceAgno, agno.com homepage and docs.agno.com/workflowsread 2026-09-21 |
||
|
LettaWorkflow Orchestration Agents delegate to specialized subagents for task breakdown and parallel execution, agents in an organization communicate and collaborate, and agents share memory files backed by Git, so work runs across several steps and agents. SourceLetta, docs.letta.com/configuration/subagents, concepts/shared-memory and pricingread 2026-09-21 |
||
|
Triggers & Channel Coverage How agents wake up and where they work: schedules, webhooks, message events, CRM events, inbox events, chat, email, voice, and collaboration tools. |
||
|
AgnoTriggers & Channel Coverage The Scheduler creates cron jobs that execute AgentOS endpoints and tracks their run history, so an agent, team or workflow starts without a person initiating it, and AgentOS interfaces serve agents in Slack, WhatsApp and other chat apps. SourceAgno, docs.agno.com/scheduler/overview and agno.com homepageread 2026-09-21 |
||
|
LettaTriggers & Channel Coverage Schedules send one time or recurring prompts, such as daily briefings or hourly triage, without anyone asking, and agents can create their own schedules. Agents also run as Slack, Discord, Telegram, WhatsApp and Signal bots and through a GitHub action. SourceLetta, docs.letta.com/configuration/schedules and self-hosting/channelsread 2026-09-21 |
||
| Knowledge & context | ||
|
Knowledge Grounding & RAG Ability to ground agent behavior in company data through document ingestion, retrieval, external knowledge APIs, semantic search, or RAG layers. |
||
|
AgnoKnowledge Grounding & RAG Knowledge loads files, URLs or raw text into a knowledge base backed by a vector store, and the agent searches it to ground its response; a published pages mode keeps Markdown and vectors in sync with a documentation site and shows the page revision behind each result. SourceAgno, docs.agno.com/knowledge/overviewread 2026-09-21 |
||
|
LettaKnowledge Grounding & RAG Agents read the customer's files on the computers they run on and the GitHub repositories they are given access to, so knowledge comes in through tools on each run. There is no document index or retrieval store over the customer's knowledge apart from the agent's own memory. SourceLetta, docs.letta.com/platform/cloud-agents/github and platform/computersread 2026-09-21 |
||
|
Memory & State Persistence Ability to persist context across a run, conversation, workflow, user, team, or longer-term memory layer. |
||
|
AgnoMemory & State Persistence Memory stores facts per user_id in the configured database and loads them into later runs across conversations, with a memory mode controlling when records are created, updated or deleted, alongside sessions scoped to a single conversation. SourceAgno, docs.agno.com/memory/overviewread 2026-09-21 |
||
|
LettaMemory & State Persistence Each agent keeps memory blocks and MemFS, a Git versioned memory filesystem it reads, writes and reorganizes itself. Memory is shared across all of that agent's conversations and optionally with other agents, and background dreaming reflects on it and improves it. SourceLetta, docs.letta.com/concepts/memfs and configuration/memoryread 2026-09-21 |
||
| Control & trust | ||
|
Human Oversight & Guardrails Approval steps, consent checkpoints, escalation rules, structured guardrails, policy constraints, and pause/resume controls. |
||
|
AgnoHuman Oversight & Guardrails Human-in-the-loop covers agents, teams and workflows: user confirmation requires explicit approval before a tool executes, user input and dynamic user input pause for information, and external tool execution hands a call outside the agent's control, with approvals managed from the AgentOS control plane. SourceAgno, docs.agno.com/hitl/overview and agno.com homepageread 2026-09-21 |
||
|
LettaHuman Oversight & Guardrails Permissions give allowlist and approval controls over which tools an agent may run, and the Agent SDK exposes permission modes with interactive tool approvals, so a person approves a gated call before it executes. SourceLetta, docs.letta.com/configuration/permissions and agent-sdk/permissionsread 2026-09-21 |
||
|
Security, Identity & Governance RBAC, SSO, auditability, encryption, least-privilege tool access, compliance posture, and data handling policy. |
||
|
AgnoSecurity, Identity & Governance AgentOS offers JWT authentication across REST, MCP, A2A and WebSocket requests, roles as named bundles of scopes, service accounts and per-user data isolation, with basic RBAC on Pro, a SAML SSO add-on, and per-resource RBAC and audit logs on Enterprise. The site shows a SOC 2 badge with no report, auditor or date, and the attestation details sit in a trust center at trust.agno.com. SourceAgno, docs.agno.com/agent-os/security/overview and agno.com/pricingread 2026-09-21 |
||
|
LettaSecurity, Identity & Governance Organization permissions control who can access agents and conversations, alongside API key authentication, secrets storage, and role based access control with SAML or OIDC SSO on Enterprise. Letta publishes no attestation, certification or trust center. SourceLetta, docs.letta.com/pricing and teams/permissionsread 2026-09-21 |
||
|
Observability & Auditability Traces, logs, execution histories, metrics, audit events, and debugging detail for production agent behavior. |
||
|
AgnoObservability & Auditability Tracing records execution spans in the customer's own database, covering run input and output, model calls, tool calls with timing, results and errors, team delegation and workflow steps, viewable in the control plane or queryable through the AgentOS API; retention is unlimited on every plan and Enterprise adds audit logs. SourceAgno, docs.agno.com/agent-os/tracing/overview and agno.com/pricingread 2026-09-21 |
||
|
LettaObservability & Auditability Each turn streams the agent's reasoning, assistant messages, tool calls and results for inspection, and MemFS keeps a Git history of every memory change. There is no audit log separate from runtime traces, trace export or retention by plan. SourceLetta, docs.letta.com/agent-sdk/messages and concepts/memfsread 2026-09-21 |
||
|
Deployment & Data Residency Deployment modes and options, including SaaS, dedicated cloud, VPC, on-prem, hybrid, local runtime, and self-hosting. |
||
|
AgnoDeployment & Data Residency The open source runtime runs in the customer's own cloud, with deployment templates for Docker, AWS, Azure, GCP, Helm, Modal, Railway and Render. Agno says data never leaves the customer's system, and Enterprise adds a self hosted control plane. SourceAgno, agno.com/pricing and docs.agno.com/deploy/templatesread 2026-09-21 |
||
|
LettaDeployment & Data Residency Letta runs fully locally or on the customer's own infrastructure through a self hosted App Server, with no Letta account required. Agents can also run in Letta managed cloud sandboxes or on the customer's own laptop, workstation or cloud VM. SourceLetta, docs.letta.com/self-hosting and platform/computersread 2026-09-21 |
||
| Solution readiness | ||
|
Prebuilt Agents, Templates & Packs Ready-made workflows, packaged employees, templates, blueprints, industry solutions, and role-specific agents that reduce time-to-value. |
||
|
AgnoPrebuilt Agents, Templates & Packs Agno publishes complete agent applications as templates, each with its own repository: Scout, a company intelligence agent across web, Slack, Drive, wiki and CRM sources; Dash, a self-learning data agent; and Coda, a code companion for pull request review and issue triage in Slack. Each works on its own. SourceAgno, docs.agno.com/deploy/templatesread 2026-09-21 |
||
|
LettaPrebuilt Agents, Templates & Packs Letta's site hosts a catalog of 22 installable Mods, official and community, each with a letta install command, alongside bundled skills, and Letta ships Letta Agent as a ready agent through the app and CLI. Sourceletta.com mod catalogread 2026-10-25 |
||
| Platform extensibility | ||
|
Model Flexibility & Routing Ability to work across multiple foundation models, route tasks to different models, or let buyers bring their own providers and keys. |
||
|
AgnoModel Flexibility & Routing The developer sets each agent's model by choosing a provider model class and model id, from a catalog spanning OpenAI, Anthropic, Google, open-weight hosts and gateways, and agents on different models can run side by side. SourceAgno, docs.agno.com/models/overview and agno.com homepageread 2026-09-21 |
||
|
LettaModel Flexibility & Routing The customer connects model providers with their own keys or coding plans and switches an agent's model at any time, with Letta Auto as an optional routed choice, so model choice sits with the customer. SourceLetta, docs.letta.com/configuration/models and pricingread 2026-09-21 |
||
|
APIs, SDKs & MCP Extensibility Composability layer: stable APIs, SDKs, MCP tool consumption/serving, custom tools, and integration into internal systems. |
||
|
AgnoAPIs, SDKs & MCP Extensibility Agents built with the Python SDK are served by AgentOS over a REST API, as an MCP server, over A2A and through chat interfaces, with a published API reference and authentication on each route. SourceAgno, docs.agno.com/agent-os/security/overview and agno.com/pricingread 2026-09-21 |
||
|
LettaAPIs, SDKs & MCP Extensibility The Letta Agent SDK embeds stateful agents in the customer's own applications, with a published reference. The App Server has a WebSocket protocol and remote client API, the API plan gives API key access for automated workloads, and agents connect to editors over the Agent Client Protocol. SourceLetta, docs.letta.com/agent-sdk, self-hosting/app-server and pricingread 2026-09-21 |
||
|
Testing, Debugging & Optimization Testing, debugging, scoring, retries, fallbacks, quality gates, and optimization loops for improving agent workflows before and after deployment. |
||
|
AgnoTesting, Debugging & Optimization Evals turn expected behavior into repeatable checks that run in development and CI: an accuracy eval runs the agent and has an evaluator model compare its response with the expected output, alongside agent as judge, reliability and performance evals. SourceAgno, docs.agno.com/evals/overviewread 2026-09-21 |
||
|
LettaTesting, Debugging & Optimization Letta documents an evaluation harness for Letta Cloud agents, with datasets, rubric and tool graders, and pass or fail gates that set the exit code. Every page of it is marked legacy, and none appears in the current docs index. Sourcedocs.letta.com/v1-sdk/evalsread 2026-10-25 |
||
| Specialist automation | ||
|
Browser & Computer Use Browser, desktop, or remote/local computer control for workflows that cannot be handled through stable APIs alone. |
||
|
AgnoBrowser & Computer Use Interactive browsing in Agno runs through third party engines such as Browserbase, Stagehand and AgentQL, each bought separately. The product has no browser, desktop or computer control of its own, and its Web Browser toolkit opens URLs in a browser without operating the page. SourceAgno, docs.agno.com/tools/toolkits/others/web-browser and /tools/toolkits/web-scrape/browserbaseread 2026-09-21 |
||
|
LettaBrowser & Computer Use An agent's computer is a Letta cloud sandbox or the customer's own machine, where it runs code and handles files. The 0.31.8 changelog lists a built in browser-use skill. What that skill controls, and how, is not described in the docs. Sourcedocs.letta.com reference/changelogread 2026-10-25 |
||
Pricing snapshot
Sourced from the Index pricing dataset · open each vendor's profile for full detail.
| Pricing | A Agno |
L Letta |
|---|---|---|
|
Entry price Lowest public entry point |
Pro from $150 a month, with a free tier and a free open source runtime. Enterprise is custom. | Pro at $20/mo, and the API plan at $20/mo plus usage. A free tier exists, Enterprise is custom, and self hosting is free. |
|
Pricing confidence How public the numbers are |
Public, exact | Public, exact |
|
Billing Primary billing axis |
Flat. The hosted control plane is a monthly subscription with no usage metering, and Pro add ons are priced per seat, per live connection and for SAML SSO. | Usage on top of flat monthly plans. Pro and Teams Pro, the latter per seat, carry a Letta Auto quota with pay as you go overage beyond it, and the API plan bills per active agent, per second of tool execution and for model usage. |
|
Variable cost Workload / overage exposure |
Low variable cost | High variable cost |
|
Free tier / trial Try before you buy |
Free tierTrial
|
Free tier
|
|
Buying motion Self-serve vs sales call |
Mixed | Mixed |
|
Pricing verified When this pricing was last checked |
Product updates
Newest first, each linked to its source.
Agno
-
· Agent capability
CompanyOS, a new part of AgentOS, gives agents ongoing areas of responsibility called Products, each with Sources such as repositories, documentation, local Markdown files and websites.
Source -
· Deployment / data residency
Agno v3.1.4 adds a sandbox parameter so ClaudeAgent and CodexAgent run their whole harness process inside an isolated computer for each session, with DockerSandbox as a provider the customer operates and AgentCoreSandbox on Amazon Bedrock AgentCore Runtime.
Source -
· Security / enterprise
Role based access control and user management come to AgentOS in Agno 3.1.0, with a role store, scope policies, an audit log, a user directory and an admin interface.
Source
Letta
-
· Agent capability
Agents running apps inside a Letta Code sandbox can now expose those apps' ports, so a service the agent starts can be reached from outside the sandbox.
Source -
· Workflow orchestration
Letta Code v0.34.40 extends its subagents with one setting that picks the runner for each subagent, either Letta or an outside coding worker such as Claude Code or Codex.
Source -
· Observability / auditability
Every subagent task in Letta Code v0.34.38 now writes a full JSONL event log, including tasks run by remote workers on connected computers.
Source
More comparisons with Agno or Letta
Other matchups in agent infrastructure platforms
Not the pairing you were after? These compare a different set of agent infrastructure platforms on the same 14 capabilities.