Codity One starts at the Premium allowance and is set with you. The figures below are the floor the agreement builds on, not a rate card.
Customannual agreementSee the Codity One plan
Three pooled meters, per seat, per month. Every surface draws from the same pool: dashboard, webhook, CLI, plugin and API alike.
| Meter | Codity One allowance | Beyond the pool |
|---|---|---|
| Review / scan jobs | From 45 / seat / mo | Set in your agreement |
| Chat / navigation messages | From 500 / seat / mo | Set in your agreement |
| Automation actions | From 400 / seat / mo | Set in your agreement |
The same work costs the same wherever you start it. A review run from the CLI and the same review run from a pull request both spend one job.
One job is one pass over a diff or a repository, whichever surface asked for it.
From 45 / seat / mo on Codity One
One message is one question and the answer to it.
From 500 / seat / mo on Codity One
One action is one change Codity makes or drafts on your behalf.
From 400 / seat / mo on Codity One
Reading what Codity has already produced is not metered, and neither is running the organisation. Only new work is.
The pooled meters are the only usage limit Codity One carries.
Allowances are quoted per seat and spent by the organisation. One engineer having a heavy week does not need a plan of their own.
Each meter refills on the first day of your billing month. Unused runs do not carry over.
Admins are notified at 80, 100 and 120 percent of a pool, so the first anyone hears of an overage is not the invoice.
Codity One does not meter into a public rate card. What happens past a pool — more capacity, a hard cap, or a true-up at renewal — is written into your agreement.
On-prem deployment, custom and self-hosted models, dedicated API capacity and org-wide rollups are all available on Codity One. They are listed, with what each one covers, on the Premium screen.
Back to pricing. If you are sizing a rollout and want the numbers checked against your volume, contact@codity.ai.
