Priced to your scale, not a public list
Every Haidrun deployment is a regulated, private network. What changes between tiers is how much you move, which modules you run, where it runs and the service level your regulator expects — never the technology underneath, and never the compliance. Tell us your volume and we’ll scope the rest.
- Issuance (HSC) & payments
- Full compliance stack — included
- Shared capacity · sandbox + limited production
- FIPS 140-3 L3 HSM · fully managed by Haidrun
- REST API + OpenAPI · standard support
- Custodial wallets
- Native SDK + HVM (EVM contracts)
- Reserved capacity · staging environment
- 99.5% availability SLA
- Priority support · guided onboarding
- Treasury & reserves · tokenization engine
- Dedicated HSM appliance in your cloud
- Region of your choice · you hold the keys
- 99.9% SLA + automatic credits · RTO < 60 min
- 24×7 support
- Full RWA suite · consumer / B2C apps
- Physical HSM per client · your data centre
- Customer-led key ceremony (M-of-N quorum)
- 99.95% SLA · DR site · RTO < 15 min
- 24×7 + named TAM · white-glove onboarding
The non-negotiables, at every tier
Some things aren’t an upsell. Every deployment — a first pilot or a bank settling at scale — ships with the same performance, security and, above all, the same full compliance stack built into the protocol.
Deterministic finality
Final, irreversible settlement in under 500 ms — no forks, no reorgs. Availability and recovery are set per tier (see the matrix).
HSM-first by default
All signing keys in FIPS 140-3 Level 3 HSMs, TLS 1.3 / mTLS, AES-256 at rest, RBAC + MFA + JIT, and an immutable 7-year audit trail.
The full stack — every tier
KYC, KYB, AML monitoring, sanctions/PEP screening, risk scoring, case management, SAR and EDD, plus reserve attestation — identical whether you settle a million or a billion.
EVM-compatible HVM
Deploy Solidity with standard EVM tooling and parallel execution on your private Layer 1.
Your cloud or ours
Oracle Cloud, Google Cloud, Azure or AWS — or private cloud / on-premises — multi-AZ by default.
Standard APIs & SDK
Versioned REST APIs (OAuth 2.0 + JWT), auto-generated OpenAPI specs, and a native SDK to build on.
What changes as you scale
Every tier runs the same private Layer 1, the same APIs and the same compliance stack. Moving up a tier changes your volume, your control and your service level — not your integration, so there’s no re-platforming and no migration project waiting at the next stage of growth. All pricing is by quote.
| Capability | PilotUp to 1M/mo | Growth1M–25M/mo | Enterprise25M–250M/mo | Institutional250M–1B+/mo |
|---|---|---|---|---|
| Capacity & service level | ||||
| Volume & throughput | Up to 1M / moShared capacity pool | 1M–25M / moReserved capacity | 25M–250M / moReserved + burst headroom | 250M–1B+ / mo15k–30k TPS dedicated¹ |
| Availability SLA⁴ | 97.5%No service credits | 99.5%Credits on request | 99.9%Automatic service credits | 99.95%Automatic service credits |
| Resilience & recovery | Multi-AZBest-effort recovery | Multi-AZRTO < 4 h | Multi-AZ + multi-regionRTO < 60 min · RPO < 15 min | + DR site²RTO < 15 min · RPO < 1 min |
| Environments | Sandbox³ + limited production | + Staging | + Full production | + Multi-region |
| Money modules | ||||
| Custodial wallets | — | ✓ | ✓ | ✓ |
| Treasury & reserves | — | — | ✓Reserve management & treasury tooling | ✓+ Multi-currency reserve operations |
| Tokenization & real-world assets | — | — | Tokenization engineRWA suite as add-on | Tokenization engine+ full RWA suite, B2C apps |
| Compliance — identical at every tierRegulation doesn’t scale with your volume, so neither does this. Every tier ships the full compliance stack — we don’t sell a lighter version of an obligation you can’t hold lightly. | ||||
| KYC & tiered client identification | ✓ | ✓ | ✓ | ✓ |
| KYB & beneficial-owner verification | ✓ | ✓ | ✓ | ✓ |
| AML monitoringSanctions & PEP screening — EU / UN / OFAC | ✓ | ✓ | ✓ | ✓ |
| Dynamic risk scoring & risk-based limits | ✓ | ✓ | ✓ | ✓ |
| Case management, SAR generation & EDD | ✓ | ✓ | ✓ | ✓ |
| Reserve attestationMiCA / GENIUS | ✓ | ✓ | ✓ | ✓ |
| Security & deployment | ||||
| HSM tenancy & key ceremonyFIPS 140-3 L3 signing is in every tier | Dedicated partition, shared applianceStandard ceremony | Dedicated partition, shared applianceStandard ceremony | Dedicated appliance in your cloudCustomer-witnessed ceremony | Physical HSM per client, your data centreCustomer-led, M-of-N quorum |
| Residency & perimeter | EU regionsOur secure perimeter | EU regionsOur secure perimeter | Region of your choiceYour cloud account, you hold the keys | Region of your choiceYour data centre, no shared infrastructure |
| Assurance | Platform pen-test summaryReports on request | Platform pen-test, full reportReports on request | + Remediation planAnnual customer audit | Dedicated pen-testAnnual audit + on-site |
| Who runs it | Fully managed by Haidrun | Fully managed by Haidrun | Your cloud account, we operate | Your infrastructure, we support |
| Developer & support | ||||
| SDK & integration | REST API + OpenAPI | + Native SDK & HVMEVM contracts | + Integration support | + Custom endpointsDedicated integration |
| Support & onboarding | Business hoursSelf-serve onboarding | Priority, business hoursGuided onboarding | 24×7Guided + integration support | 24×7 + named TAMWhite-glove onboarding |
¹ 15,000–30,000 TPS in production depending on infrastructure; up to 65,000 TPS in optimised lab conditions. Volume bands are indicative and confirmed per engagement.
² DR is a warm standby site with documented RTO/RPO, in addition to active multi-region — not instead of it.
³ Sandbox is an isolated test network with synthetic assets. It is not connected to public networks and carries no SLA.
⁴ The platform is engineered for 99.99% availability with a sub-5-minute recovery-time objective; the availability and recovery figures above are the contractual SLA backed by service credits — deliberately set below the engineered target so the commitment is defensible.
Why it’s a quote, not a price tag
A regulated, private money network is never one-size-fits-all. We scope each engagement to a few clear variables — then give you a single, predictable commercial model.
Your scale
Transaction volume and throughput set the tier — from a controlled pilot to bank-grade settlement.
Your build
The modules you run (issuance, payments, treasury, tokenization, RWA, consumer) and where you deploy — our cloud, yours, or on-prem.
Your service level
The availability SLA, resilience and support your regulators and operations require — the compliance stack is already the same at every tier.
Do smaller tiers get less compliance?
No. The full compliance stack — KYC, KYB, AML monitoring, sanctions/PEP screening, risk scoring, case management, SAR, EDD and reserve attestation — ships at every tier. Regulation doesn’t scale with your volume, so neither does this.
Why don’t you publish prices?
Because every Haidrun deployment is a private, regulated network scoped to your volume, modules, deployment model and service level. A public price list would misrepresent that. We move quickly to a clear quote once we understand your scale.
Can we move between tiers?
Yes. Every tier runs the same private Layer 1, APIs and compliance stack, so throughput scales through infrastructure with a documented, zero-downtime path — you step up without re-platforming or a migration project.
How is transaction volume measured?
By the monthly volume of on-network transactions across the modules you run. The bands above are indicative; we confirm the exact definition and thresholds during scoping.
Is this the price for the whole platform?
Pricing covers the Haidrun platform and the modules in your tier. This page is informational and not an offer; the applicable commercial agreement governs the engagement.
Tell us your volume — we’ll scope a package
Share where you are today and where you’re heading. We’ll map you to the right tier and put a clear quote in front of you.