You pay for what you screen and what you monitor.
Three tiers, set by capability and institution size. Two metering units, both defined on this page. We publish the structure — every axis you will be charged on, and every commercial term that can move the bill. We do not publish rates, because the right rate depends on your volume and your jurisdictions.
What this page tells you
- The four things you pay on
- How a screened entity and a monitored transaction are counted
- What each tier includes, and who it is designed for
- Where we are as a company, stated plainly
Why there are no numbers on this page
We are pre-revenue and have no customers yet. That means we have no rate card that has survived contact with a real institution, and publishing one would be a guess dressed as a policy.
So we publish the structure instead. Every axis you can be billed on is named below. Every commercial term a procurement team asks about is answered below, or marked as still open. The rate is not published because it is not yet set. Minimum spend, contract term and overage treatment are settled per institution, in a conversation.
If you want the short version: the price is a platform subscription plus consumption, the consumption units are screened entities and monitored transactions, and the tier you sit in is set by which capabilities you turn on and how large your institution is.
What you pay on
Four components. Most institutions are billed on the first three.
Platform access
The tenant itself: a logically isolated tenant, the evidence ledger, the operator console, API access, user seats, and support. Charged as a recurring subscription. Set by tier and by institution size.
What moves it: tier, number of users, support terms.
Screening usage
Metered per screened entity, per month.
What moves it: the size of your customer and counterparty book.
Monitoring usage
Metered per monitored transaction.
What moves it: your payment and transfer volume.
Assurance
Charged only if you need assurance work beyond a standard security review — a bespoke DPA, or support for your own penetration test.
What moves it: the assurance work you need — which we will itemise in the quote rather than describe as a package.
How the units are counted
A metering unit is only useful if you can forecast against it. Both are defined here.
Screened entity
A unique customer, counterparty, or related party held under screening during a billing month.
- Counted once per month, however many times it is re-screened in that month. Continuous screening does not multiply the bill.
- An entity you have offboarded and are no longer screening stops counting the month you stop screening it.
Monitored transaction
One payment or transfer evaluated by the platform.
- Counted on evaluation, not on outcome. A transaction that produces no alert is still an evaluated transaction.
What is not metered
- Alerts. You are not charged for the platform finding something.
- Cases, investigations, or filings raised from those alerts.
- Evidence records, audit exports, or reporting packs.
- API calls that read your own data.
We will not build a pricing model that makes a compliance team hesitate before opening a case.
Tiers
Priced by capability and institution size. Every figure is on request.
| Comparison point | Core | Complete | Enterprise |
|---|---|---|---|
| Designed for | An EMI, digital lender, or payment firm whose obligation is screening its customer book — often standing up a financial crime function for the first time. | A mid-size bank or a scaled payment firm running both a customer book and a payment flow, with an in-house financial crime team and an examination cycle. | An institution that must satisfy its own model-governance requirements — multiple jurisdictions, a group structure, or a supervisor who asks to see how models are governed. |
| Core capability | Sanctions, PEP, and adverse-media screening at onboarding and on an ongoing basis. Entity resolution across your book. Alert triage and disposition. | Everything in Core, plus transaction monitoring across your payment flow, fraud and AML detection, full case management, and the filing workflow up to the point of submission. | Everything in Complete, delivered against your own constraints: model-governance evidence depth, support terms, and negotiated commercial terms. |
| Metered on | Screened entities | Screened entities + monitored transactions | Screened entities + monitored transactions |
| Deployment | Multi-tenant SaaS, logically isolated tenant | Multi-tenant SaaS, logically isolated tenant | Multi-tenant SaaS, logically isolated tenant |
| Price | Contact us | Contact us | Contact us |
| Next step | Get pricing for the Core tier | Get pricing for the Complete tier | Get pricing for the Enterprise tier |
We do not mark a tier “most popular.” We have no customers, so we have no basis for it. When we do, the label will reflect what institutions actually bought.
Add-on modules
These can be enabled on any tier rather than forcing an upgrade:
Narrative risk intelligence
Additional risk signals on entities already in your book, delivered with the same evidence record as any other finding.
Governance operations
Policy and model version control with approval workflows, and evidence lineage an examiner can follow.
Custom watchlists
Your own lists, screened to the same standard as everything else you screen, with the same match evidence on every hit.
Autonomous compliance agents
Investigation packaging and regulatory-change monitoring, with a human approval step before anything leaves the platform.
One capability we are not selling yet
At least one capability in the platform depends on a network of participating institutions. That network does not exist, because we have no customers. It is not on any tier, not in any quote, and not counted in anything we claim we can do for you today. We will price it when it can do what its name promises.
Who this is for
RegNovaIQ is built for institutions outside the top 20.
That is a design decision, not a fallback. The largest global banks run long-established in-house platforms and buy on terms built around them. The economics and the integration model that suit them do not suit anyone else.
We build for the institution that has the same regulatory obligation and none of that:
- Mid-size and regional banks — a full obligation across screening, monitoring, and filing, met by a team that is counted in tens rather than hundreds.
- Payment firms and PSPs — high transaction volume, thin margin per transaction, and a supervisor who expects the same evidence a bank produces.
- Digital lenders — fast onboarding, a customer book that grows faster than the compliance headcount.
- Electronic money institutions — a licence condition to meet from a standing start, often with an examination already scheduled.
- Crypto-asset and payment-adjacent firms under a new regime — an obligation that arrived before the tooling did.
Who this is not for, today
If you are a top-20 global institution with an established in-house financial crime platform, we are not the right vendor for you yet. We would rather say that here than in month three of a procurement cycle.
In every tier
These are not upsells. They are the floor, and they are the same on Core as on Enterprise.
- Tenant isolation. Your data is scoped to your tenant, and cross-tenant isolation is exercised as a gate on every release.
- The evidence trail. Every decision records its inputs, the model version in force, and the policy context, and that record can be retrieved and examined.
- You remain the decision-maker. The platform evidences, and it recommends. A filing, an offboarding, or a disposition is your institution’s decision, and the record shows it was yours.
- Audit export. Reporting packs and evidence bundles you can hand to an examiner without assembling them by hand.
- Role-based access control with full attribution on every action.
- Phishing-resistant strong authentication. WebAuthn / FIDO2 hardware-token MFA.
- Encryption in transit and at rest.
- Versioned APIs across screening, alerts, and risk, with published contracts.
- Data retention controls you configure, within the minimums your own regulator sets.
A tier changes what the platform does. It does not change how your data is protected or how a decision is evidenced.
Procurement questions
The questions a number would otherwise have answered.
Is there a minimum spend?
We have not published a standard minimum. Whether an annual minimum applies, and at which tiers, is stated in your quote before you sign.
Do you require a long-term contract?
We have not published a standard term. The default term, the terms available to you, and the notice period are stated in the quote.
How does the price change as we scale?
Consumption is metered, so screening and monitoring costs move with your book and your volume. Platform access does not move with volume; it moves when you change tier or add users.
What happens if our volume spikes in one month?
We have not published a standard overage term. It will be written into your quote rather than left open, because an unbounded overage term is not something a vendor risk review should accept from anyone.
Is there a pilot or proof of concept, and does it cost?
Ask us. We have not published standard pilot terms, so duration, scope, and whether it is chargeable are agreed case by case.
Are there design-partner terms?
We are pre-revenue and building against real institutional requirements, so early institutions have influence over the roadmap that later ones will not. We have not published formal design-partner terms.
What third-party data costs will we incur?
If a source you require must be licensed by you directly, we will tell you before you sign, not after.
Where does the platform run?
RegNovaIQ is delivered as hosted SaaS on Microsoft Azure in the EU. Other deployment models are not offered today.
What are your payment terms and currency?
We have not published standard terms. Currency, invoicing frequency, and payment terms are stated in the quote.
Which entity do we contract with?
NOVAIQ LIMITED, company number 16948483, registered in England and Wales.
What happens to our data if we leave?
Not published yet, deliberately. Three values make this answer worth anything — the export formats, the window in which an export can be requested after termination, and the deletion timeline with the evidence that deletion occurred — and we will not publish a version that is missing any of them. Ask for the clause during procurement and hold us to it.
Does your SOC 2 status affect our procurement?
Yes, and you should assume it will. We hold no SOC 2 report. No SOC 2 examination has been completed. ISO 27001 is not held. If your vendor-risk policy requires either at signature, we cannot meet it today. See below.
Where we are, stated plainly
A compliance vendor that shades the truth about itself is not a compliance vendor. So:
- Pre-revenue. No customers. No institution is live on RegNovaIQ today. Nothing on this site is a customer claim, and no tier on this page has an occupant.
- No production client traffic. The platform has not carried a live client workload.
- We hold no SOC 2 report. No SOC 2 examination has been completed. ISO 27001 is not held. If either changes, we will say so on the day it changes, and not before.
- NVIDIA Inception member since 3 September 2026. A programme membership, not a certification, and not a customer.
- NOVAIQ LIMITED, company number 16948483, incorporated 7 January 2026, England and Wales. Registered office: Flat 137 Leon House, 233 High Street, Croydon, England, CR0 1FX. SIC 62012. The public record is on the Companies House register.
- Founders: William Davis (Co-Founder).
What this means for the price: we will not quote as though we have a track record we do not have. Ask what we will commit to contractually, and hold us to the answer.
Tell us your volume, and we will put a number in front of you.
Two figures start a quote: how many entities you screen, and how many transactions you monitor.
It will be among the first numbers we have written for an institution like yours. We will show you how we arrived at it.