Infrastructure pricing for regulated digital finance.
ZenithBlox is priced as regulated infrastructure, not developer tooling. Pricing reflects deployment complexity, regulated workflows, jurisdictions, connectors, policy rulebooks, and transaction value at risk — not the number of users, developers, or API call volume.
Four revenue streams. Distinct economics. Distinct procurement.
The streams are not interchangeable — they map to different procurement processes, margin profiles, and risk allocations.
Platform subscription
Annual access to the full ZenithBlox infrastructure stack — Universal Adapters, BloxBlueprint, the BPSC Compiler, and the FrontierBlox Engine. Tiered by institution size, deployment complexity, and regulatory scope.
Transaction & usage fees
Activated on production go-live. Applied to regulated flows — settlement, tokenised assets, CBDC operations, trade documents, compliance verifications. Bounded by pre-agreed fee bands and annual caps.
Enterprise & sovereign licensing
Multi-year licensing for central banks, government platforms, market infrastructure, and sovereign cloud or on-premise deployments. Pricing reflects deployment topology, jurisdictional scope, and SLA tier.
Professional services
Time-bounded implementation, regulatory mapping, adapter configuration, and pilot-to-production support. Designed to accelerate deployment, not to create dependency. Each engagement has defined scope, timeline, and exit criteria.
Three tiers. Defined by deployment scope, not by feature gating.
Every tier includes the full platform. Tier placement is driven by production environments, regulated workflows, connectors, jurisdictions, and SLA requirements.
Institutional
Regional banks, asset managers, payment providers. Up to 3 active workflows. Up to 2 jurisdictions. Standard enterprise SLA.
- Full platform stack
- Standard enterprise SLA (99.9%)
- Pre-built adapters: SWIFT, ERP, AML/KYC
- Annual term · multi-year options available
- Onboarding professional services
Enterprise
National banks, large custodians, market infrastructure. Up to 10 active workflows. Up to 5 jurisdictions. Enhanced SLA and dedicated account team.
- Full platform stack
- Enhanced SLA (99.95%) · dedicated account team
- Production-tier adapter library
- Multi-jurisdiction rulebook support
- Pilot-to-production professional services included
- Custom workflow modelling support
Sovereign & Tier-1
G-SIBs, central banks, government platforms. Unlimited workflows. Multi-jurisdictional deployment. Sovereign SLA. Custom commercial structure.
- Full platform stack & Atlas extension
- Sovereign SLA · 24/7 named-engineer support
- Sovereign cloud or on-premise deployment
- Regulator-authored rulebook support
- Custom corridor & integration engagement
- Multi-year strategic commercial structure
Published ranges are indicative. Final pricing is the output of a procurement conversation that reflects deployment scope, regulatory requirements, and the institution's profile.
What determines where a deployment lands.
Tier placement and final pricing follow seven structural drivers. Each maps to a procurement question that compliance, risk, and infrastructure teams already know how to answer.
The number of distinct production environments the control plane governs — including sandbox, staging, and disaster-recovery pairs where required.
The number of distinct workflows under pre-execution governance. Each workflow has its own rulebook scope, its own decision artefact lineage, and its own audit trail.
The number and type of institutional and rail connectors in production. SWIFT, core banking, ERP, AML/KYC, custody, and execution-rail adapters each carry their own integration profile.
Each jurisdiction requires a distinct regulatory rulebook and may trigger composite-rulebook evaluation. Multi-jurisdictional deployments compose rulebooks in priority order with conflict resolution rules.
Public cloud, private cloud, sovereign cloud, or on-premise. Sovereign and on-premise deployments carry their own commercial structure and certification requirements.
Production SLA tier (99.9%, 99.95%, sovereign 24×7), named-engineer support, and incident-response window. Sovereign SLAs include rulebook-emergency procedures.
Transaction-fee structure is bounded by pre-agreed fee bands, annual caps, corridor-specific rates by jurisdiction pair, and committed-volume bundles. Predictable cost exposure is a contractual requirement.
Transaction fees are bounded by contract — not by market volatility.
Every transaction-fee agreement is bounded at execution. Rates do not fluctuate outside the contractual band without written amendment.
All transaction rates are defined within a contractual band at execution. Rates do not move outside the band without written amendment.
Clients may elect an annual maximum transaction-fee cap. Once the cap is reached, further transactions within the period are processed at zero marginal fee cost.
Clients committing to minimum annual transaction volumes receive pre-agreed discounted rates for the bundle period.
Cross-border transaction corridors may carry fixed-rate schedules by jurisdiction pair, providing full cost predictability for corridor flows.
Transaction fees are not activated during the paid pilot phase. They activate on production go-live sign-off — typically 8–16 weeks after pilot commencement. A 30-day grace period applies at go-live for volume ramp.
Transaction fees: monthly in arrears against contracted rate schedule. Subscription fees: annual in advance (standard) or quarterly in advance by agreement. Net 30 from invoice date.
Institutions validate before they commit. Commercial structure follows the validation path.
Design-in
Workflow scoping, regulatory mapping, and policy-rulebook drafting with compliance, risk, and legal counsel. Paid or unpaid scoping engagement, depending on workflow complexity. No production data. No rails. Output: workflow specification and rulebook draft.
Pilot
Controlled pilot deployment with limited counterparties. Full enforcement on bounded scope. Paid pilot fee covers infrastructure, adapter configuration, and pilot-period professional services. Transaction fees are not yet active. Output: pilot decision artefacts, supervisor review where required, go-live readiness assessment.
Production
Annual subscription commences. Transaction fees activate on production go-live sign-off. Professional services for new workflows, new jurisdictions, and rulebook evolution. Output: governed production workflow with audit-grade evidence.
What an institutional procurement team should expect.
Annual (standard) with multi-year options: 3-year (10% subscription discount, fixed-price term) and 5-year (15% subscription discount, strategic partnership pricing, enhanced SLA, dedicated account team).
60-day written notice required for non-renewal. Renewal price escalation is CPI-linked with a contractual cap (3–5% annually).
No per-seat, per-developer, or per-team licensing. Team growth does not trigger cost escalation. Pricing reflects deployment scope and transaction value at risk.
Standard enterprise SLA at 99.9% production uptime. Enhanced SLA at 99.95%. Sovereign SLA includes 24×7 named-engineer support and rulebook-emergency procedures.
Tenant-isolated by default. Sovereign deployments support in-jurisdiction data residency and on-premise execution. Cross-tenant access is architecturally impossible.
Standard governing law is Singapore law with SIAC arbitration. Alternative governing law negotiable for sovereign deployments.