Skip to content
Licensing & Support

Is Agno free? Understanding the Apache 2.0 license

Yes. The Agno SDK and AgentOS are open source under Apache 2.0, commercial use included. Paid plans connect the Control Plane to live deployments.

Cosette CresslerContent & Product Marketing Lead

November 16, 20268 min read

Yes. Agno is free and open source under the Apache License 2.0. You can build commercial products on the Agno SDK and AgentOS and change the code to suit you, without paying Agno or asking permission.

The paid plans are optional: they connect the hosted AgentOS Control Plane to live deployments and add team features such as extra seats and role-based access control.

Teams usually ask this question twice. An engineer asks it before the first pip install agno, and someone from legal or procurement asks it again before the agents ship. Both want to know whether the code costs money, and legal also needs to see what the license requires in return.

This article isn't legal advice, so check with your own counsel before making decisions that depend on the license.

What's open source in Agno?

Agno Inc. licenses everything in the agno-agi/agno repository under Apache 2.0, with a LICENSE file at the root that reads "Copyright 2025-2026 Agno Inc." Each published package carries its own copy of the same license and declares Apache in its PyPI metadata:

PackageWhat it isLicense
agnoThe SDK: agents, teams, workflows, memory, knowledge, tools, and AgentOS (agno.os)Apache 2.0
agnoctlThe agno command-line tool for scaffolding, running, and connecting to AgentOSApache 2.0
agno-infraInfrastructure tooling for deploying agent apps to AWS or DockerApache 2.0

AgentOS, the runtime that serves your agents over REST and MCP, ships inside the agno package. That means the API server, authentication, approvals, scheduling, and tracing are all under the same license as the framework, and you run them in your own infrastructure.

The Agent UI chat interface lives in a separate repository under the MIT license, which is also permissive.

The one piece outside the open-source repositories is the AgentOS Control Plane at os.agno.com, a hosted web interface for managing your deployments. It connects straight from your browser to your runtime.

What does Agno charge for?

Agno charges for the Control Plane when you point it at a live deployment, plus team and enterprise features on top. Running the framework and serving agents costs nothing on any plan.

PlanPriceWhat it adds
Free$0/monthRun your agent platform in your own cloud at any scale. Full Control Plane against a local AgentOS, unlimited.
Pro$150/monthConnects the Control Plane to one live AgentOS deployment, with three team seats, role-based access control, and email support
EnterpriseCustomEnd-user identity and roles, audit logs, custom RBAC with per-resource scoping, security reviews, and hands-on build help

Pro add-ons include extra seats at $30/month each and extra connections at $95/month. SAML SSO costs $300/month. None of the plans charge for serving, so your costs at scale are your own infrastructure and your model provider's bill.

You don't need any plan to run Agno in production. AgentOS serves its REST API (and an MCP server, if you turn it on) whether or not you ever open the Control Plane.

What does the Apache 2.0 license let you do?

Apache 2.0 gives you broad rights at no cost. Section 2 grants a "perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable" copyright license to reproduce the code and prepare derivative works, and to display, perform, sublicense, and distribute it.

In practice, that covers the cases most teams care about:

  • Commercial use. The license has no field-of-use limits and no fees, so you can build paid products and internal tools on Agno.
  • Modification. You can change any part of the code, including AgentOS, and keep a private fork.
  • Closed-source products. Section 4 lets you put your own license terms on your modifications, or on a derivative work as a whole, as long as you meet the license's conditions for the Agno code inside it.
  • Hosting. Nothing in Apache 2.0 stops you from running Agno as part of a hosted service for your customers.
  • Charging for support. Section 9 lets you charge for support, or take on warranty and indemnity obligations, on your own behalf.

What do you have to do in return?

Most of Apache 2.0's conditions kick in when you redistribute the code, for example by shipping a modified copy of Agno in a package or in software your customers install. Section 4 asks you to:

  1. Give recipients a copy of the license.
  2. Mark any files you modified with a prominent notice that you changed them.
  3. Keep the copyright, patent, trademark, and attribution notices from the source.
  4. Include the attribution notices from the project's NOTICE file, if it has one.

Agno's repository doesn't ship a NOTICE file today, so in most cases the job comes down to shipping the license and Agno's copyright notice with any code you distribute and marking the files you changed.

Section 6 covers trademarks: the license doesn't grant rights to Agno's trademarks, beyond what you need to describe where the code came from. Sections 7 and 8 provide the code "as is," without warranty, and limit contributors' liability.

How does the Apache 2.0 patent grant work?

Section 3 gives you a patent license from every contributor, on the same perpetual and royalty-free terms as the copyright grant. It covers patent claims a contributor holds that their contribution necessarily infringes, alone or combined with the project. So a contributor can't hand code to the project and later sue you over a patent that code reads on.

The grant has one condition. If you file a patent lawsuit claiming that Agno, or a contribution to it, infringes a patent, your patent licenses under Apache 2.0 for Agno end on the date you file. The explicit patent grant is one of the clearest differences between Apache 2.0 and shorter permissive licenses such as MIT, whose text doesn't mention patents.

How is Apache 2.0 different from source-available licenses?

Apache 2.0 is an OSI-approved open-source license. Source-available licenses publish the code too, but they restrict how you can use it.

The Elastic License 2.0 (ELv2) is a common example. It bars you from providing the software to third parties as a hosted or managed service that exposes a substantial set of its features. It also forbids working around license-key functionality or removing the licensor's notices. Elastic describes ELv2 as a source-available license that isn't OSI-approved.

Apache 2.0 has no clauses like these. You can host Agno for your customers, and the code contains no license keys to work around. If you're comparing agent frameworks, read each project's LICENSE file instead of the badge on its README, since a project can mix licenses across packages.

Here's how the three licenses compare on the questions teams ask most:

QuestionApache 2.0MITElastic License 2.0
OSI-approved open sourceYesYesNo
Commercial useYesYesYes, with limits
Offer it to customers as a hosted or managed serviceYesYesNot with a substantial set of its features
Explicit patent grantYesNoYes

Read the full license in the Agno repository, and see Run your AgentOS to deploy it in your own cloud.

Checked against the Agno v3.2.0 repository and pricing page, plus the Apache License 2.0 text, on 16 November 2026. Plans and prices change, so check the linked pages before you rely on the figures above.

Sources

Frequently asked questions

Yes. Agno Inc. publishes Agno under the Apache License 2.0, an OSI-approved open-source license, and the full source lives on GitHub. The only closed piece is the hosted Control Plane at os.agno.com, which you do not need to run Agno.

Yes. Agno Inc. licenses Agno under Apache 2.0, which grants a royalty-free license with no limits on commercial use. You can build and sell products on the Agno SDK and AgentOS without paying Agno.

Yes. Apache 2.0 has no field-of-use limits and charges no fees, so you can sell products built on Apache 2.0 code or run it inside a paid service. If you distribute the code itself, ship the license with it and mark the files you changed.

Yes. Apache 2.0 places no restriction on hosting, so you can run Agno inside a SaaS product or a managed service you sell. Source-available licenses such as ELv2 bar offering the software as a managed service.

Agno uses the Apache License 2.0. Every Agno package, from the core agno SDK to the agnoctl CLI, ships the same license file, and the copyright notice names Agno Inc.

Yes. AgentOS ships inside the agno package under Apache 2.0, and you run it in your own infrastructure. The hosted Control Plane at os.agno.com is the separate, optional interface that Agno’s paid plans cover for live deployments.

If you redistribute Agno’s code, Apache 2.0 requires you to pass along the license with its copyright and attribution notices intact, and to mark the files you changed. Using Agno to build and run your own service does not require a credit in your product’s interface.

Yes. Apache 2.0 does not require you to publish your modifications. If you distribute the modified code, ship the license and the original notices with it, and mark the files you changed.

The SDK and AgentOS are free, and serving agents costs nothing on any plan. You can use the Control Plane at no cost against a local AgentOS, and connecting it to a live deployment starts with the Pro plan at $150/month. Enterprise pricing is custom.