Skip to content

System Deployment Options

Crux VPN supports multiple deployment models to accommodate a variety of infrastructure and security requirements. Depending on your operational preferences, you can run Crux VPN as a fully managed service or host the components within your own environment.

SaaS

The fastest way to get started with Crux VPN is to use it as a service hosted by Sirius. In this configuration, all core components including the web UI, API services, and database are operated in Sirius-managed infrastructure on Azure. Customers access the Crux VPN management interface via a web portal to onboard users, register devices, and configure network parameters.

Self-Hosted

Alternatively, Crux VPN can be deployed in a self-hosted configuration. This involves installing the web UI, API services, and associated database on infrastructure that you manage. Reference architectures for self-hosted deployments on both Azure and Oracle Cloud Infrastructure are currently in development.

Arqit SKA-Platform™ Integration

Crux VPN requires integration with Arqit’s SKA-Platform™ (SKA-P) to function. SKA-P is responsible for delivering and rotating quantum-safe symmetric keys after the initial ML-KEM-1024 key exchange. SKA-P is available in two deployment models:

  • PaaS (hosted by Arqit): Use the hosted version of SKA-P as a platform service.
  • Self-Hosted: Deploy your own private instance of SKA-P on-premises or in your preferred cloud environment.

All combinations of Crux VPN and SKA-P deployments are supported. For example, Crux VPN can be used as a SaaS while connecting to a privately hosted instance of SKA-P—or both can be self-hosted within your infrastructure. Access to SKA-P requires an Enterprise Agreement with either Sirius or Arqit.