PricingNot final

One tier is real. One is not priced. One does not exist yet.

Self-hosting is free and always will be. OpenRegs Cloud has no prices attached because they have not been decided, and putting a plausible-looking number here would be the same mistake as an agent that guesses at a provision. The third column is not a plan at all — it is the list of things a large firm asks for first, every one of which is deliberately outside the first Cloud release.

This page is a placeholder. Nothing below is an offer, a quote, or a commitment to a figure. Cloud pricing will be published before Cloud opens — until then, the honest answer is that we do not know yet. What Cloud will and will not do in its first release is set out on the Cloud page, and these columns are held against it.

Self-hosted

Run the engine yourself. This tier is not a trial and does not expire.

FreeOpen source, forever

The full pipeline, Apache-2.0
Every published regime, CC BY 4.0 — today that is one fixture
REST and MCP serving in your own network
The change feed, the control-mapping tooling and the CI integrations
Community support

Start from the repository

Cloud

Not open

Hosted serving of verified releases, so nobody on your side operates the pipeline.

Not yet pricedPricing set before Cloud opens

Managed serving of verified public regime releases, over REST and MCP
Accounts, organisations, and API keys with rotation and revocation
Per-key metering and usage-based billing
A console, and a public status page
One region

Join the waitlist

Enterprise

Later

The things a large firm asks for first, and the reason none of them is for sale yet.

Not offeredOutside the first Cloud release

Private regimes — needs tenancy isolation designed before it is built
Signed attestation and audit-log export — a different promise from the stamp on a response
A freshness SLA — nothing to measure until a real corpus ships on a cadence
SSO and SCIM — the seam is left where they will go

Read the first-release scope