Why are commercial figures not published?

Every engagement differs in scope, deployment model, obligation surface and assurance requirement. Licensing is quoted against an agreed scope and confirmed in an executed Order Form, so a published figure would be misleading rather than helpful.

Can ARIE be licensed without AIRAS Cloud?

Yes. ARIE, the deterministic regulatory reasoning engine, is licensed independently of the AIRAS Cloud control plane. Organisations that already operate a GRC platform, or software vendors that need regulatory reasoning inside their own product, licence the engine on its own.

Can AIRAS Cloud be licensed without ARIE-driven automation?

Yes. The control plane — register, intake, controls, review routing, evidence and audit history — can be licensed with the baseline ruleset alone, with engine automation, sector packs and bespoke rulesets added later.

Do you support embedded or OEM use?

Yes. An embedded licence allows a software vendor, consultancy or assurance provider to deliver ARIE reasoning inside their own product or service, under defined attribution, versioning and support obligations.

Can we deploy inside our own tenancy or on-premise?

Yes. Dedicated single-tenant, private-cloud and sovereign deployment options are available where data residency, isolation or sectoral requirements demand it. The deployment model is agreed before contracting.

Is a pilot required before a full licence?

It is not required, but most regulated organisations start with the controlled eight-week pilot. It validates the engine against real obligations and converts into a production licence with the configuration and evidence already in place.

Packages and licensing

Licence the platform, the engine, or both.

AIRAS Cloud and the ARIE regulatory engine are licensed separately or together. Scope, deployment model and assurance obligations differ in every regulated environment, so commercial terms are quoted against an agreed scope and confirmed in an executed Order Form — not published as a list price.

Request licensing information About the ARIE engine

AIRAS Cloud — Platform Licence

The full governance control plane.

For organisations that want one accountable record of every AI system, with assessment, control, review, decision, monitoring and evidence in a single governed environment.

Complete AI, model and agent register with named owners
Guided adaptive intake and document-based discovery
ARIE-driven qualification, role and classification
Controls, evidence requirements and completeness reporting
Reviewer routing with segregation of duties
Append-only audit history and exportable decision packs

Licensed per organisation, by governed scope and deployment model.

ARIE — Engine Licence

Regulatory reasoning, licensed on its own.

For organisations that already run a GRC, risk or assurance platform and need defensible, versioned regulatory reasoning rather than another interface.

Deterministic qualification against the statutory definition
Operator role determination and prohibited-practice gating
High-risk classification following the annex structure
Obligation mapping with evidence requirements
Versioned rulesets with reassessment on material change
Integration API and reasoning trace for every conclusion

Licensed independently of AIRAS Cloud, with annual support and ruleset updates.

ARIE — Embedded / OEM Licence

Ship regulatory reasoning inside your own product.

For software vendors, consultancies and assurance providers that want to deliver AI Act reasoning to their own customers without building a regulatory engine.

Embedded engine rights within an agreed product boundary
Defined attribution, versioning and update obligations
Technical schedule covering interfaces and support tiers
Partner enablement and reasoning-methodology briefing
Optional white-labelled evidence and decision output

Structured as an OEM agreement with a defined product and distribution scope.

Private and Sovereign Deployment

Isolation where residency demands it.

For regulated environments where the deployment model itself is part of the control set: dedicated tenancy, private cloud or on-premise operation.

Dedicated single-tenant or customer-tenancy deployment
EU data residency by default, sovereign options on request
Deployment, backup and recovery runbooks
Named technical contact and change-control process
Security, privacy and resilience documentation pack

Quoted against the agreed architecture and operating responsibilities.

Enterprise Pilot

Validate before you commit.

A controlled eight-week programme against your own obligations, structured to convert directly into a production licence.

Configured environment for one business unit or programme
Registered AI assets and structured assessments
Selected use cases taken through full review and decision
One integration proof and architecture for future integrations
Role-based training and a production-conversion roadmap

Fixed-scope programme, quoted per pilot and confirmed in an Order Form.

Partner, Reseller and Advisory Licensing

Deliver AIRAS to your own clients.

For advisory firms and systems integrators that govern AI on behalf of client organisations and need a licensed, multi-client operating model.

Multi-client operating model with tenant isolation
Practitioner enablement and methodology training
Co-delivery model for assessments and evidence packs
Defined referral, reseller or delivery-partner structure

Agreed per partner, based on delivery model and client footprint.

How licensing is structured

Scope first, architecture second, commercials last.

01
Define the governed estate
Which business units, which AI systems, which obligations and which frameworks are in scope.
02
Choose platform, engine or both
AIRAS Cloud as the control plane, ARIE as the reasoning engine, or the engine embedded in your own product.
03
Agree the deployment model
Multi-tenant EU hosting, dedicated tenancy, private cloud or sovereign operation, with residency and isolation set out.
04
Contract against an Order Form
Commercial terms, service levels, support tier and data-processing schedule are confirmed in an executed Order Form.

Licensing enquiry

Tell us the shape of the engagement.

Use the structured fields below. It routes directly to the team, and you receive an acknowledgement immediately.

Full name

Work email

Organisation

Country or region

What would you like to licence?

ARIE can be licensed on its own, or as the reasoning engine inside AIRAS Cloud.

Deployment preference

Preferred commercial structure

Scope of use(optional)

Industry(optional)

Organisation size(optional)

Approximate number of AI use cases(optional)

Current governance maturity(optional)

Procurement stage(optional)

Your role in the decision(optional)

Timeline

Job title(optional)

Phone number(optional)

Anything else we should know(optional)

Please keep this general. Do not include confidential, personal or regulated information.

I agree that AIRAS Cloud may use the details provided to respond to this licensing enquiry.

Sent over an encrypted connection and stored in a restricted-access record.

Common questions

Licensing questions

Ready to see AIRAS Cloud against your real obligations?

Book a walkthrough or start a licensing conversation. No commercial commitment and no confidential information required.

No commercial commitment. No confidential information required.