Pricing

Priced on what you connect, not on how much you store.

Antvia runs inside your own cloud or data centre. You are already paying for the storage and the compute, and we are not going to sell it back to you with a margin on top. Here is what the meter actually counts.

What the meter counts

Three things, and none of them is a person or a byte.

Sources, for Antvia Data

One source is one system we connect, land, model and keep running. A finance ERP is a source. A warehouse management system is a source. Ten more tables inside one of them is not.

Volume does not enter this. The infrastructure is yours.

Metrics, for Antvia Intelligence

A metric is a definition the business has agreed on and the platform will enforce at query time. Revenue is a metric. The forty charts that read revenue are not, and neither are the people reading them.

Charts, dashboards and readers are unmetered.

Getting it standing, once

Deployment into your environment, the first sources wired, governance and access mapped to how your organisation is actually structured. A one-off, quoted against the scope, not a rolling fee.

Then a subscription, monthly or annual.

Before you commit

Start with a pilot in our environment.

A flat fee, a fixed access window, and a real deployment running against your own data rather than a demo dataset. You bring the source that has been difficult, not the clean one. At the end of the window you have seen the platform do the work, and you have something to point at internally.

If you go on to deploy, the pilot fee comes off the first invoice. If you do not, you keep what we found and we keep nothing of yours.

Ask for a pilotSee it running first

What we ask for before quoting

  1. The systems. Which ones have to be in scope, and which are known to be messy.
  2. The decisions. What the business argues about that better numbers would settle.
  3. Where it has to run. Your cloud, your data centre, and what compliance requires of it.

Thirty minutes is usually enough to price it properly.

The part most contracts leave vague

What the bill does when you grow.

More readers

Nothing changes. Giving the whole operations floor access to the same governed number is a decision about who should see it, not a budget request.

More data

Nothing changes with us. Your infrastructure bill moves the way it always would, and you keep the ability to tune it because you own it.

More systems, more definitions

This is where it moves, and deliberately so. A new source is real work to connect and keep running. A new governed metric is real work to agree and enforce. You can see the increase coming before you commit to it.

Common questions

Asked on most first calls.

Does the price go up when our data volume grows?

No. Antvia runs on your own infrastructure, so the storage and compute bill is already yours and we do not resell it back to you. What we charge for is the number of sources we keep connected and modelled, and that number moves when you add a system, not when a table gets bigger.

Do we pay per user?

No. Reader seats are not metered, so the person who opens a report once a quarter costs the same as the person who never closes it. Widening access is a decision about who should see the number, not a decision about budget.

What does the pilot cost?

A flat fee, quoted up front, for a fixed access window in our environment. It is a real deployment against your own data, not a slide deck, and the fee is credited if you go on to deploy.

What happens to the price if we leave?

Nothing you have to negotiate. The substrate is open source and stays with you, and your bronze, silver and gold data is exported in open formats. What ends is the subscription and our layer on top of it.

Tell us what you are connecting.

Once we know the systems and the definitions, the number is straightforward and we will put it in writing. Before that, anyone quoting you a figure is guessing.

Book a call