Elmoz pricing. What it costs, and what drives it.
Three plans, priced on two things: how many systems Elmoz connects to, and how many agents and machine identities it protects. Not per seat, not per finding.
StarterAnnual subscription
A fixed yearly price for a focused scope. No per-seat licence.
GrowthAnnual subscription
Priced per year and scaled to how much of the estate it covers.
EnterpriseIndividually priced
Scoped and priced per organisation.
Extend a planMid-term
Both price drivers can be topped up mid-term. Ask and we scope it.
We reply from [email protected], usually the same working day.
- Three plans: Starter for a first production deployment, Growth for a growing estate, Enterprise for multi-cloud and regulated organisations.
- The price moves with two things only: how many systems Elmoz connects to, and how many agents and machine identities it protects.
- No per-seat licence and no per-finding billing. The whole security and platform team works on one subscription.
- We do not publish a figure, because it depends on the estate. Send the rough shape of yours and you get a real number, not a range.
The three plans, side by side.
Same product in all three. What changes is how much of the estate it covers, and that is what the figure follows.
| Plan | Best for | Typical scope | How it is priced |
|---|---|---|---|
| Starter | A first production deployment | One cloud and the identities around it | Fixed annual price |
| Growth | Agents running in more than one place | Several connected systems | Scaled to volume |
| Enterprise | Large and regulated organisations | Several clouds and identity providers | Individually priced |
What actually drives the price.
Two numbers, both of which you can estimate before talking to anyone.
Which plan fits
Most teams start on Growth. Starter is the right call when one cloud and one identity provider cover almost the whole estate.
Enterprise is about shape rather than size: several clouds, several identity providers, and an audit trail someone outside the team will read.
If the honest answer is that nobody has counted the agents yet, that is the usual starting point, and it is the first thing the inventory answers.
Questions, answered.
What is counted, what is not, and what to do when the numbers are still unknown.
What counts as a protected identity?
Every AI agent, service account, OAuth grant and key that Elmoz inventories and traces. Each identity counts once, however many access paths it turns up in.
Is Elmoz billed per seat or per finding?
Neither. The yearly price depends on the number of connectors and the number of protected identities and agents. Everyone on the security and platform team can use it.
Why is there no price on this page?
Because the honest figure depends on how much of the estate Elmoz covers, and a published range would be wrong for almost everyone who reads it. Send the rough shape of your environment and you get a real number, usually the same working day.
What if we do not know how many agents we have?
That is the normal starting point, and it is the first thing Elmoz answers. Give a rough estimate of cloud accounts and developers, and the plan can be adjusted once the inventory is in.
Before you ask for a number.
What the product does, and what it has found elsewhere.
See what your agents can reach. Before someone else does.
Book a demo and we walk through the access paths in an environment like yours.