Pricing
Priced per environment, not per incident
Charging by investigation would give you a reason not to investigate, which defeats the point. Production and staging are what you pay for.
Why per environment
Pricing shapes behaviour long before anyone reads the invoice, and most usage-based models for this kind of tool shape it badly.
The obvious model would be per investigation. It sounds fair — you pay for what you use — and it is exactly wrong, because it puts a price on the moment someone is deciding whether a number looks odd enough to look into. At the margin, a per-investigation price does not produce revenue. It produces a shrug and a guess.
That matters more here than in most categories, because the failures this product is built for are the quiet ones. Nobody hesitates to investigate a pipeline that crashed. The 38% shortfall on a run that reported success is caught by somebody who thought a figure looked slightly off and decided to check — precisely the decision a per-use price discourages.
Per seat has the same defect in a different place. Confirming or rejecting a diagnosis is what calibrates the system, so the more people who can do it the better the product gets. Charging per head shrinks that sample deliberately.
So the unit is the environment: a thing that exists whether or not anything went wrong this month, and whose value does not change with how carefully you use it.
Design partner
Free
during the pilot
For teams willing to give us real incidents and honest feedback while we build. Limited places.
- Up to 3 pipelines
- 1 agent
- Full investigation engine
- Direct line to the people building it
Team
Contact us
per environment
For a data platform team running production pipelines that matter.
- Unlimited pipelines
- Up to 10 agents
- Source control and database integrations
- Remediation pull requests
- Audit log and scoped access
Enterprise
Contact us
For estates with multiple environments, strict data residency, or a security review to satisfy.
- Everything in Team
- SSO and SCIM
- Custom redaction and retention policies
- Self-hosted control plane
- Named support
Full comparison
Everything that makes an investigation trustworthy — evidence records, citations, topology and drift — is in every plan, including the free one. Those are not premium features; they are the product. What varies is scale, integration surface and the controls a larger organisation needs.
| Design partner | Team | Enterprise | |
|---|---|---|---|
| Investigations | Included | Included | Included |
| Evidence records and citations | Included | Included | Included |
| Pipeline topology and drift notes | Included | Included | Included |
| Pipelines | Up to 3 | Unlimited | Unlimited |
| Agents | 1 | Up to 10 | Unlimited |
| Environments | 1 | Priced per environment | Priced per environment |
| Database and scheduler discovery | Included | Included | Included |
| Source control integration | — | Included | Included |
| Remediation pull requests | — | Included | Included |
| Audit log | 90 days | 12 months | Configurable |
| Scoped access roles | — | Included | Included |
| SSO and SCIM | — | — | Included |
| Custom redaction rules | Defaults only | Included | Included |
| Configurable retention | — | Within bounds | Included |
| Data residency selection | — | — | Included |
| Self-hosted control plane | — | — | On request |
| Support | Direct, informal | Business hours | Named contact |
What counts as an environment
The billing unit, defined precisely — because a vague unit is how a bill becomes a surprise.
An environment is a set of systems you would investigate as one thing. Usually that maps to production, staging, and sometimes a disaster-recovery estate. The test is practical rather than architectural: if an incident in one place would never send you looking at the other, they are separate environments.
What an environment explicitly does not depend on:
- How many database instances it contains
- How many pipelines run in it
- How many agents you deploy to reach its network segments
- How many people look at the results
- How many incidents happen in it
A single production environment with twelve SQL Server instances, an Airflow deployment and forty bespoke services is one environment. That is deliberate: estates of exactly that shape are the reason this product exists, and a model that charged per instance would penalise the people it is built for.
What is deliberately not metered
Four things we could charge for and do not, because charging would make the product worse.
Each of these is a case where a meter would change behaviour in a direction that damages the thing you are paying for.
| What | Why not |
|---|---|
| Investigations | A per-investigation price teaches teams to guess instead of investigate — which is precisely the behaviour this product exists to replace. |
| Seats | Confirming and rejecting diagnoses is how accuracy gets measured. Charging per head shrinks the sample and makes the product worse for everyone. |
| Evidence storage, within reason | Retention is a policy you set for security reasons, not a line item we sell back to you. Nobody should be choosing a shorter window to save money. |
| Re-investigation | A conclusion that does not survive new evidence was never a conclusion. Re-running has to be free or nobody will do it. |
Common questions
Why no prices on this page?
Is staging a separate environment?
What if we have twelve SQL Server instances in one environment?
Does the agent count towards anything?
What happens if we stop paying?
Can we trial it on a real incident before committing?
Related: design partners for what a pilot involves; security for retention, residency and access; and the product for what is actually included.
Get started
Not sure which applies?
Tell us what you run and how it breaks. We will tell you honestly whether this helps yet — including if the answer is not yet.