Enterprise pricing
One license, two shapes.
Both from $24,000 per year.
Invoiced, not charged to a card. Hosted enterprise on our cloud, or an on-prem license per node, from the same floor. The number is the floor rather than a quote: what the commitment covers is set with you, because a thousand actions a month and a million are not the same agreement.
The shape
What the license is
One agreement, one invoice, one number a finance team can plan against. This is what both shapes share; the section under it is where they differ.
| What | In the license |
|---|---|
| Term | Annual, invoiced, renewed by agreement rather than by silence |
| Floor | From $24,000 per year, on either shape |
| Volume | A committed number of actions, set with you and written into the agreement |
| Seats | Negotiated for the people who act, approve and administer |
| Viewer seats | Free and unlimited, on both |
| Projects | Unlimited |
| Governance | The same rules, roles, ceilings, approvals and record on both |
| Included with it | Observability export and relays for internal systems, on both |
| The agreement carries | Data processing terms, service levels and support terms, plus the grant to run it yourself where you do |
One row is worth reading twice. Viewer seats are free because an audit that costs money per reader stops being read.
The two shapes
Hosted enterprise, and the on-prem license
Same floor, same governance, same agreement. What differs is who holds the machine, what is included in the number, and what the meter reads.
| Hosted enterprise | On-prem license | |
|---|---|---|
| Billed | Annual, from $24,000 per year | Annual per node, from $24,000 per year |
| What the number includes | The setup we run for you, and its upgrades | The software, the operator tooling and its upgrades |
| Where it runs | Our cloud, in a place your organization is alone in | Your cloud, your private subnet or your building |
| Dedicated setup | Your own address on a node nobody else is on, where the agreement warrants it | Every deployment is dedicated; that is the offer |
| The meter | The actions your setup took, counted on the node we run and shown to you in the console | A signed usage record: counts, dates, a signature, and nothing else crosses the boundary |
| Records kept | Your retention setting on the setup we run | As long as your own policy says, because the table is in your database |
| The console | enterprise.atmon.ai/console, an email and nothing else on the door | Ships inside your node and answers on your own address |
Which one you take is a security question rather than a price question, and the security page writes out what each offer promises. Both are drawn on the deployment page.
The meter
What gets counted, and what never does
The unit is an action: one call made to a system on your behalf, of the kind that changes something or reads something for the work. It is the same unit on both shapes.
On your own machines the deployment counts them itself and produces a signed usage record at the end of a period: counts, dates, a signature. That record is the invoice basis and the one thing that crosses the boundary out of your network.
On our cloud the counting happens on the node we run for you. Either way the same counts are in your own console and your own dashboards, so the invoice is checkable against numbers you already hold.
- Never billed Work that was refused by your own rules. A limit that fires costs nothing, which is what keeps a strict policy from being an expensive one.
- Never billed Work parked for a person. Waiting for an approval is not an action, whether the answer comes in a minute or never comes at all.
- Never billed Looking things up. Finding which action fits and reading what it needs are how the work gets aimed, and charging for them would price a question.
- Never billed by us Model calls. You register your own model address and key, and you pay your own provider for what it costs. We are not a model provider and never resell one.
The number
Why the floor is where it is
An enterprise deployment is an annual, invoiced agreement with data processing terms, service levels and a security review behind it. Below the floor, the work of doing that properly costs more than the contract.
Publishing the floor rather than hiding it saves both sides a call. If it is above what your department can commit today, the self-serve product on atmon.ai is the honest answer, and it carries the same governance.
Said plainly
What the number does not buy you today
- Live providers atmon is in beta. GitHub is the first live provider account it can reach, every other connection is still a stand-in, and no price changes that fact.
- A certificate There is no outside security audit and no compliance certificate to hand your reviewer. The security page is what we have, including what it does not claim.
- Single sign-on On the enterprise roadmap and not built. The honest table says what exists and what does not.
- A quote The floor is a floor. What your commitment costs depends on the volume you commit to and the seats you need, and it is written down before anything is signed.
Reach the team
Start the conversation
hello@atmon.ai. Tell us which department goes first, which systems the work has to touch, and what your security review asks for. A reply comes from the team.