Pricing
Start with your own agents. Bring the team into one workspace. Plan how agents work across the company. Every plan is priced per human seat, and an agent never consumes one.
A clear record of your own agents, what they did and what it cost.
One workspace for the team’s goals, work, people, agents and cost.
Compare and improve how agents work across several teams.
Plan how agents work across the company, with the people who run it.
Plans are coming soon. A seat is a human workspace member; agents do not consume seats. AI model and provider fees are separate and stay with your provider.
01 / 03 How a seat is counted
01 People, not agents
A seat is a human member of the workspace: a team lead, a platform engineer, a reviewer. The agents they create and run are recorded, attributed and compared without adding a seat. Model and provider usage stays on your provider invoices; airis shows the estimate beside the work and never bills it.
airis · Sample workspace · Illustrative seat estimate
02 / 03 Compare plans
Each column adds what the next stage needs. History windows and limits describe the hosted airis platform.
| Your workspace | Free | Team | Business | Enterprise |
|---|---|---|---|---|
| Work historySessions, recorded checks and usage basis | 7 days | 90 days | 365 days | Scoped with you |
| Your agents and their workReports, checks and usage kept distinct | ✓ | ✓ | ✓ | ✓ |
| Shared goals and workstreamsTeam view and Your work perspectives | — | ✓ | ✓ | ✓ |
| Cost by agent, person and taskUsage estimate with a stated basis | Your own usage | ✓ | ✓ | ✓ |
| ComparisonsCost, acceptance and time on the same tasks | — | — | ✓ | ✓ |
| Prepared changesSkills, workflows and hooks, reviewed before use | — | Shared skills and workflows | With comparisons and hooks | ✓ |
| Roles and source accessVisibility is an explicit policy | — | — | ✓ | ✓ |
| Rollout planningAcross teams, with data and access requirements | — | — | — | ✓ |
| Support planningOnboarding and named contacts | Open-source documentation | ✓ | ✓ | Planned with you |
History windows, features and limits describe the hosted airis platform, not the local open-source app, and may change before any plan becomes available.
03 / 03 Questions
The short version: people are seats, agents are not, and provider fees are separate. The rest we cover on a call.
No. A seat is a human workspace member: someone who signs in, owns work or reviews it. The agents that person creates and runs are recorded and attributed to them without adding a seat. In the synthetic airis workspace, 12 people and 24 named agents would be 12 seats.
No. Prices cover the airis platform only. Model and provider fees are separate and stay with your providers. airis shows a usage estimate beside the work so the cost basis is visible; an estimate is not an invoice, and airis does not bill it.
The plans are designed to grow with you. Start with your own agents, choose Team when a group shares goals, and to Business for cross-team views and roles. Seats are billed per human, so adding agents never changes the price. Enterprise terms are built with you.
One person, their own agents, the usage estimate for that work with its stated basis, and their recorded checks, for the last 7 days. It is meant for an engineer who wants a clear record of what their agents did and what it cost before the team decides anything.
The open-source agentacct app runs locally on one machine, records your own agent work and needs no account. The plans on this page are for the hosted, multi-team platform. Reading or running the open-source code commits you to nothing.
Book a demo. We walk through the sample workspace, look at cost, quality and speed for one cohort, and then talk about your teams and tools. Then pick one representative workflow of your own, write down its acceptance criteria, and compare later runs on the same terms. Modeled potential is not realized savings.
Pricing
A guided look at the sample workspace, then a conversation about which plan fits your teams.