Three tiers.One you canstart today.
Starter is in the product now and you reach it by signing up. Growth and Enterprise are quoted after a short fit review, because the price depends on where you run it, which boundary the governance record may not cross, and what support you need. There is no checkout button on this page, because there is no checkout behind it.
- No checkout flow
- No card fields
- No list price invented to fill the space
Starter, Growth, Enterprise.
The names, the prices exactly as they are stated, and the feature lists as they exist. Nothing in these three cards is aspirational, which is why two of them do not carry a number.
- Self-serve today
Starter
Included for self-serve evaluation
For a single organization proving the governance workflow against real assets.
What it lists- Private organization on signup
- Model registry and trust score
- Promise ledger
- Databricks connection path
- Fit review first
Growth
Quoted after fit review
For teams operationalizing governance across products, policies, and evidence workflows.
What it lists- Multiple teams and workflows
- Governance exports
- Advanced monitoring surfaces
- Implementation support
- Fit review, then contract
Enterprise
Contracted annually
For regulated deployments needing security review, custom rollout, and procurement support.
What it lists- SSO and workspace controls
- Deployment and rollback planning
- Databricks co-sell support
- Security and compliance review
What changes between them.
The same three lists, set against each other so they can be read in one pass. This is deliberately not an exclusion grid: a line missing from a column is not being withheld from you, it has not been stated yet, and the fit review is where it gets stated.
| Compared on | StarterSelf-serve today | GrowthFit review first | EnterpriseFit review, then contract |
|---|---|---|---|
| How you get it | Included for self-serve evaluation | Quoted after fit review | Contracted annually |
| Who it is for | For a single organization proving the governance workflow against real assets. | For teams operationalizing governance across products, policies, and evidence workflows. | For regulated deployments needing security review, custom rollout, and procurement support. |
| What the tier lists |
|
|
|
Scroll sideways to compare all three.
SSO and workspace controls are named on Enterprise and nowhere else, so treat that as a real line. Everything else on this page is a list of what a tier states, not a list of what the tiers next to it lose.
What is the same whichever tier you land on.
These are properties of the product rather than features of a plan, so they do not move with the price and they are not held back to make a higher tier look better.
It fails closed.
When the system is uncertain it denies rather than guesses, and it shows an empty state rather than a plausible one. No tier gets a version that fills the gap with something invented.
The evidence is yours.
Governance outcomes are written back as Unity Catalog tags on the asset, evidence is exported to Delta through the SQL Statement Execution API with an idempotent MERGE, and reports are generated artifacts. Stop using Ileri tomorrow and the evidence is still sitting in your workspace.
The deployment is source-visible.
Docker Compose for local and single-host, Helm charts for the API and the web service, a Databricks App that runs inside your own workspace, and the whole infrastructure tree in the open. Your platform team can read the operational shape before anyone signs anything.
Records are organization-scoped.
Every query is organization-scoped in application code. On the core governance path (Promise Ledger, Trust Score, audit, compliance evidence, cross-modal risk) that scoping is backed by Postgres row-level security with FORCE ROW LEVEL SECURITY, pinned to the request connection.
That database layer covers the governance core, not every service. Saying otherwise would be the kind of claim this page exists to avoid.
What a fit review actually is.
A short conversation whose only job is to size three things. It is not a qualification call and it is not a demo you have to sit through, because the demo is already open and you can drive it yourself.
- 01
Deployment scope
Where Ileri runs and what it governs. Docker Compose on a single host, Helm on your cluster, a Databricks App inside your own workspace, or Lakebase for transactional state on Databricks managed Postgres. The target changes the operational work, so it changes the price.
- Docker Compose
- Helm
- Databricks App
- Lakebase
- 02
Data residency
Where the governance record lives and which boundary it may not cross. The Databricks App profile is read-only by construction, registers only the governance GET endpoints, and authenticates with the workspace’s own OAuth through the platform’s forwarded identity, so on that path data does not leave your tenant. Every other target needs the question asked out loud.
- ILERI_READ_ONLY=true
- ILERI_WORKSPACE_AUTH
- one workspace, one tenant
- 03
Support needs
Who you need on the other end, how quickly, and for what. Where we do not have something we will say so rather than describe a service level that has never been measured or published.
- no published SLA
- no uptime figure
You leave with a price or with the reason there is not one yet. Both of those are more useful than a number invented to keep a deal moving.
The ones that come before a number.
Answered the way they would be answered on the call, which is the only way worth answering them.
Why is there no public price for Growth or Enterprise?
Because the number depends on things this page cannot know: where you run it, which boundary the governance record may not cross, and what support you need. A list price printed before those answers is a placeholder, and a placeholder on a pricing page is a promise you get to break later. Starter is stated here because it is the one tier that depends on none of that. You sign up and you have it.
What actually happens in a fit review?
Three things get sized: deployment scope, data residency, and support needs. Those are the three that move the price, so those are what the conversation is for. You can open the live demo and create an account before it, during it, or instead of it.
Can we start without talking to anyone?
Yes. Starter is in the product today. Create an account and you get a private organization, model registry and trust score, the promise ledger, and the Databricks connection path. Nothing on that route requires a call, an email, or a form.
What happens to our data, and what do we keep?
Governance outcomes are written back as Unity Catalog tags on the asset itself, evidence is exported to Delta through the SQL Statement Execution API with an idempotent MERGE so a re-run reconciles rather than duplicates, and reports are generated artifacts. If you stopped paying tomorrow, the evidence would still be in your workspace, in formats you already query. On the Databricks App path the question is narrower still: it runs inside your own workspace as a single self-contained container, so the data does not leave your tenant by construction.
Do we need Databricks to use this?
The three lakehouse write paths are Databricks: Unity Catalog tag write-back, Delta export, and Model Serving inference table reads. The deployment targets are wider than that, covering Docker Compose for local and single-host, Helm charts for both services, and source-visible self-host manifests. If you have no lakehouse then the catalog write-back is the specific part you do not get, and that is worth knowing before a call rather than after one.
What is deliberately not on this page?
No certification, no uptime or SLA figure, no customer names, and no latency or throughput number. Ileri is not SOC 2 certified, not ISO 27001 certified, and not FedRAMP authorized. It has controls in code and it does not have attestations, and a control is not an attestation. If certification is a hard procurement gate for you, put that in the first message and we will tell you where it stands rather than manage the question.
What changes if we go from Growth to Enterprise?
Enterprise is contracted annually and states SSO and workspace controls, deployment and rollback planning, Databricks co-sell support, and security and compliance review. Growth is quoted and states multiple teams and workflows, governance exports, advanced monitoring surfaces, and implementation support. Both start from the same conversation, so you do not have to pick before it.
Start today. Price it later.
The starter tier does not wait on a conversation, and the conversation does not wait on a decision. Open the demo, create an account, then tell us what you actually need.
Ìlérí is Yoruba for promise. A price you cannot stand behind is the easiest one to break.