Deployment

Cloud convenience, dedicated isolation or customer-controlled deployment.

AIRRP supports multiple operating models so organisations can choose where the platform runs and how operational trust is managed.

Governed contextTraceable decisionsHuman accountability
Why it matters

The product model stays consistent; the trust boundary changes.

Deployment choice should follow data residency, integration boundaries, regulatory expectations, operational ownership, support requirements and the client’s security model.

Cloud

AIRRP Cloud

AIRRP-operated SaaS for organisations that want the fastest managed operating model.

Dedicated

AIRRP Dedicated

Isolated managed AIRRP environment for stronger separation and enterprise requirements.

Private

AIRRP Private

Customer-controlled deployment for on-premise, sovereign, private-cloud or highly restricted environments.

Edge

AIRRP Edge Gateway

Customer-controlled outbound bridge for approved private/internal data sources.

Support

Controlled Support Access

Named, scoped, time-bounded support access subject to client approval.

License

Signed Entitlement

Support for local signed entitlement patterns, including restricted-connectivity scenarios.

Start managed, expand as requirements mature.

SaaS for SME and enterprise use

AIRRP Cloud can provide a straightforward path for organisations that do not need to operate the infrastructure themselves.

  • Managed application platform
  • Tenant isolation
  • Central updates
  • Standard integration paths
Keep the deployment inside the client trust boundary.

Private and managed-cloud scenarios

AIRRP Private can support customers that require their own infrastructure, managed cloud, sovereign boundary or restricted connectivity.

  • Customer-controlled infrastructure
  • Private integrations
  • Local operational ownership
  • Air-gap-compatible entitlement pattern
Remote support should be explicit, not permanent.

Support remains governed

Where remote support is enabled, the model should be named, scoped, approved, time-bounded and auditable.

  • Client approval
  • Purpose limitation
  • Automatic expiry
  • Audit trail
See AIRRP in context

From Context to Confidence.

Choose the deployment model that matches your security and governance requirements—not a one-size-fits-all default.