Pricing
Pay for usage, not seats.
Homany charges for the AI work you actually run - not for the size of the team around it. Collaborators ride free, admins govern spend, and you can bring your own model keys when it suits you.
- Free reviewers, approvers, and client collaborators.
- AI usage governed by per-team budgets you control.
- Bring your own model keys, or use bundled tokens.
Pay for usage, not seats
Planning, execution, and reporting aren't metered. You pay for the AI actions agents run - nothing else scales with headcount.
Collaborators ride free
Reviewers, approvers, and clients join at no per-seat cost, so visibility never trades off against budget.
Admins control spend
Per-team token budgets and usage reporting keep consumption predictable and legible from day one.
Free
For a first workspace and trying agents out.
$0alwaysFree collaborators always included.
- Sheets, Gantt, Kanban, dashboards, forms
- Unlimited free collaborators
- Bring your own AI model keys
- Agents to try, with a starter token allowance
- Most popular
Pro
For teams running real delivery with agents on.
Usage-based+ AI tokensPay for the AI tokens you use. Final rates confirmed in a quote.
- Everything in Free
- Per-team token budgets and usage reporting
- Agents across every team, scoped and audited
- EU / GCC data residency options
Max
For regulated and sovereignty-sensitive deployments.
Customper environmentScoped to your deployment, residency, and support needs.
- Everything in Pro
- On-premise and private-cloud deployment
- Customer-owned keys and audit export
- SSO / SCIM and enterprise support
How to read these plans
- The figures above are structural - collaborators are free on every plan, and what changes between tiers is governance and deployment, not seat count.
- AI consumption is billed by usage on Pro and scoped per environment on Max; final commercial rates are confirmed in a quote for your account.
- Bring-your-own-keys is available on every plan and shifts inference cost onto your own provider contracts.
- Unmetered work surfaces
- Token-consuming AI actions
- Admin-set budget headroom
How tokens work
Most of the platform isn't metered. AI actions are.
Tokens meter the AI work agents do - drafting a status update, cleaning a board, running a first-pass approval. The day-to-day work surfaces your team lives in are not metered.
Think of your usage as three bands: the un-metered work everyone does, the agent/AI actions that consume tokens, and the budget headroom an admin sets as a ceiling.
Because only the middle band is metered, cost tracks how much AI you turn on - not how many people are in the workspace.
- Work surfaces are unmetered - sheets, boards, dashboards, and reporting don't consume tokens.
- Agent actions consume tokens - each AI action draws from the team's budget.
- Budgets are a ceiling - admins cap how much a team can spend.
Collaborator economics
Why reviewers and clients don't cost you a seat.
Seat-based tools make you pay for everyone who touches the work. Homany doesn't - the people around the work are free.
In most tools, looping a client or a reviewer in means buying another full seat, so teams ration access and visibility suffers. Homany inverts that: the people who review, approve, or watch the work join free.
You pay for the AI work that gets done, not for the size of the audience watching it - so the incentive to keep stakeholders out of the loop disappears.
- Reviewers and approvers are free - no seat purchase to bring a stakeholder into the work.
- External clients are free - share progress without taxing visibility.
- You pay for usage - cost tracks AI actions, not audience size.
Admin budget controls
Spend stays predictable because admins set the ceiling.
Consumption pricing only works if finance can see and bound it. Homany gives admins the controls to do both.
Per-team budgets
Set a token budget for each team so heavy and light AI users never subsidize one another.
Usage reporting
See where tokens go by team and by agent, so spend is legible rather than a monthly surprise.
Caps and alerts
Be alerted as a team nears its cap, then raise the budget or let agent actions pause - no silent overage.
Worked examples
What the model looks like for different team shapes.
Qualitative scenarios - they show what does and doesn't drive cost. Exact figures are confirmed in a quote.
- Small delivery team
A five-person team with lots of clients
A boutique team runs many engagements and pulls clients in to review. Most of the headcount on the platform never touches AI.
- Reviewers and clients join as free collaborators - no per-seat cost.
- Cost tracks the handful of agent actions they actually run.
- Predictable from day one: no surprise seats as the client list grows.
- Scaling consultancy
A growing firm turning on agents across teams
A mid-size consultancy enables agents for status updates and reporting across several delivery pods, and wants spend to stay legible.
- Each team gets its own token budget, set by an admin.
- Heavy AI users and light users don't subsidize each other - usage is per-team.
- Budgets cap exposure; usage reporting shows where tokens go.
- Regulated rollout
A regulated org bringing its own model keys
A regulated buyer runs on a controlled deployment and prefers to route AI through its own provider contracts.
- Bring-your-own keys move model spend onto the buyer's existing contracts.
- Homany pricing covers the platform; inference is billed by the buyer's provider.
- On-prem and private-cloud terms are scoped in a direct quote.
Seat vs. usage
What changes when collaborators stop costing you a seat?
Compare a per-seat list price you can recognize against a usage model where collaborators are free and only AI work is billed.
People who participate but don't drive structural work.
People who own sheets, build views, run agents.
What your current per-seat tool charges per editor at list.
Monthly estimate
- Per-seat tool
- $2240/mo
- Homany usage model
- $6.00/mo
Bring your own keys
Use your own model contracts when it suits you.
BYOK lets you route AI through your own provider keys instead of bundled tokens - useful when you already have model contracts or need inference inside your boundary.
Some teams prefer to keep AI spend on their existing OpenAI, Anthropic, Azure, or self-hosted contracts - for negotiated rates, procurement alignment, or data-boundary reasons.
With BYOK, Homany pricing covers the platform and your provider bills the inference. You can also mix: bundled tokens for convenience, your own keys where it matters.
- Keep model spend on your contracts - route inference through providers you already buy from.
- Keep inference in your boundary - use self-hosted models on controlled deployments.
- Mix bundled and BYOK - use Homany tokens where convenient, your keys where it matters.
Pricing FAQ
What buyers ask before they commit.
Compare
Weighing Homany against your current tool?
See how the pricing model and platform stack up against an incumbent.