One core product. Pricing follows the complexity of your operating scope.
RegAlign is not sold as a cut-down starter product followed by a “real” version. The commercial scope changes when the organisation, regulated perimeter, reporting, migration, configuration or support requirement becomes materially more complex. Numeric pricing is shared privately with qualified prospects and remains subject to the current product, commercial and release authority for the proposed engagement.
Standard product-led onboarding is included where the engagement stays inside the normal configuration and data-preparation envelope. Material migration, configuration, group setup, data remediation or integration work is scoped separately from the actual work required. Subscription complexity does not automatically create a fixed implementation fee.
Onboarding scope and timing are agreed for each engagement. This page does not make a universal implementation-time commitment.
- Commercial structure is agreed for the named engagement.
- Scope and timing are limited and agreed per engagement.
- One or two named success criteria are agreed with the customer.
- Conversion and renewal terms are recorded in the applicable agreement where approved.
- Any reference-price protection is contractual rather than implied by this page.
- Continuity, insurance, liability and exit terms are disclosed and agreed for each engagement.
- Jersey TCB remains the current primary buyer-validation scope; other jurisdictions require separate evidence-led scoping.
This page does not authorise a named pilot, production use, deployment or customer commitment.
Shared across RegAlign and RiskAlign
Founding-customer availability is shared across RegAlign and RiskAlign and remains subject to the approved portfolio, product and commercial authority. Exact availability, discount and renewal terms are shared privately with qualified prospects; this page does not create a customer commitment or publish a numeric price or discount.
Request the engagement scopeRegAlign
The core product for a normal regulated-firm deployment.
A regulated firm whose requirements stay inside the current standard product and configuration envelope. Jersey TCB remains the primary buyer-validation scope; other regulatory perimeters are scoped against current evidence.
- Core RegAlign capability within the currently evidenced product scope
- One primary supported regulatory perimeter / jurisdiction where the relevant rule pack and controls are evidenced for the engagement
- JFSC Code-paragraph traceability where applicable to the agreed Jersey scope
- Today — curated six-slot opener as the daily landing
- Compass-assisted features only where separately enabled and evidenced for the engagement
- Governance index — every tunable in one read-only view
- Board-pack assembly workflow within the currently evidenced product scope
- Audit/provenance controls within the currently evidenced scope; known limitations remain disclosed
- Standard product-led onboarding where the engagement remains inside the normal configuration and data-preparation envelope
- Written renewal terms in the applicable agreement
- Material migration, data remediation or bespoke configuration work
- Custom integrations beyond currently supported standard exports
- Group or cross-jurisdiction capability that is not evidenced for the named engagement
- Dedicated hosted environment unless separately qualified and approved
More complex organisation / regulatory perimeter
The same core product, with greater organisational or regulatory complexity.
A group, multi-permission business or other organisation where regulated entities, permissions, jurisdictions, reporting, configuration, migration or support requirements materially increase scope and delivery burden.
- The same core RegAlign product — this is not a feature-unlock tier
- Additional supported regulatory perimeter / jurisdiction scope where evidenced and agreed
- Group-view or cross-entity reporting requirements where supported by the current product
- Named workflow walkthroughs and configuration inside the current standard envelope
- Compass/AI usage and availability scoped separately where enabled and evidenced
- Governance and board-defensibility outputs within current evidenced capability
- Engagement-specific support terms agreed before activation
- Unverified cross-jurisdiction group roll-up
- Custom code outside the supported configuration envelope
- Dedicated hosted environment unless separately qualified and approved
- Material implementation effort unless separately scoped
Enterprise / Custom
For requirements that genuinely sit outside the standard delivery envelope.
Large or unusual cross-jurisdiction deployments, material custom integrations, dedicated-environment requirements, unusual migration or data-residency needs, or enhanced delivery/support that requires separate qualification.
- RegAlign scope agreed for the named engagement
- Scoped configuration, migration and integration work where technically supportable
- Custom group/reporting requirements where evidenced and technically supportable
- Compass/AI usage terms scoped separately where enabled and evidenced
- Dedicated-environment option only where technically, security and commercially qualified
- Named delivery treatment where agreed
- Custom commercial terms recorded in the applicable agreement
- Automatic list-price discount
- Unscoped custom work
- Any capability, environment or deployment status not separately evidenced and approved
Adviser-led arrangements are commercially separate from an ordinary firm licence. Under the approved architecture, unrelated production clients remain separately entitled and accountable. Any future accredited partner or Practice Mode access is controlled partner enablement across authorised client contexts — not one low-cost licence covering an unlimited client book.
This describes the approved commercial architecture only. It does not state that Practice Mode is currently implemented, live or available for activation.
- Renewal pricing and terms are recorded in the applicable agreement where approved.
- Any reference-price protection is contractual and engagement-specific.
- Multi-year terms or discounts are subject to the applicable commercial authority.
- Continuity, insurance, liability and exit terms are disclosed and agreed for each engagement.
- Public numeric pricing and discounts are not published; the sheet is shared privately with qualified prospects.
- Founding-customer availability is shared with RiskAlign and remains subject to current authority.
RegAlign vs Excel, GRC and consultancy
Honest side-by-side on eight criteria, including where each alternative beats us — and when RegAlign is the wrong answer.
See what we have today, and what we do not
Current security posture and known limitations, with controlled diligence material available at the appropriate stage.
Request the pricing sheet
Provide the firm and engagement context. The request is reviewed against the current product, commercial and release authority before any sheet or terms are issued.