Octopus
Request a demo
Deployment & Infrastructure

Run Octopus as SaaS, in your cloud, or on bare metal

The platform does not change shape based on where it runs. Choose the model your policy, network posture, and sovereignty rules require.

See Octopus in actionSecurity and compliance
Delivery modelsSaaS · Private Cloud · Bare Metal
Cloud targetsAWS · Azure · Google Cloud
Offline postureAir-Gapped & On-Premise
Platform parity100% Feature Parity
01

Where Octopus runs

Managed service, customer cloud, or disconnected infrastructure. Agents, integrations, and operator workflows stay the same in every model.

OCTOPUS CLOUDOctopus Managed SaaSOctopus operates the platform. You connect sites outbound and start without standing up infrastructure.
AWS VPC / EKSAmazon Web ServicesDeploy into your AWS account. VPC isolation, customer-managed keys, and regional residency you control.
AZURE VNET / AKSMicrosoft AzureRun in your Azure subscription with VNet controls, Entra ID sign-in, and sovereign-region options.
GCP VPC / GKEGoogle Cloud PlatformInstall in your GCP project with VPC Service Controls and the residency policy your organisation sets.
RACK / VM / KUBERNETESBare Metal & On-Premise Data CentresInstall on your racks, VMs, or Kubernetes cluster. No public cloud dependency required.
DISCONNECTED / DARK SITEOffline & Air-Gapped EnvironmentsOperate with no outbound internet. Local AI inference, local map tiles, and controlled update media.
02

Three models, one platform

The same integrations, rule engine, agents, and operator interface in every column. A procedure written in one model runs unchanged in the others.

AspectManaged SaaSCustomer Cloud (AWS / Azure / GCP)Offline / Bare Metal
Who operates itOctopusYour cloud and platform teamsYour infrastructure team
Where data livesOctopus cloud regionsYour cloud account and regionYour facility or dark site
Compute and orchestrationOctopus-managedEKS, AKS, or GKE in your VPCKubernetes, VMs, or rack servers
Network postureOutbound connections from sitesInside your VPC or VNetFully inside your perimeter; air-gapped where required
AI inferenceOctopus-hosted modelsIn your cloud tenancyOn-prem models; no outbound calls
GIS and map tilesManaged tile serviceYour cloud or approved tilesLocal / offline tile caches
Updates and patchingOctopusScheduled with your change processMedia or staged transfer you approve
Typical fitMulti-site commercial operations, guarding companiesRegulated enterprises with cloud standardsBanking, government, defense, emergency centres
03

Edge connectors to the core you choose

Site systems stay where they are. Edge connectors bridge cameras, access, sensors, drones, and SIEM into the Octopus core (SaaS, your cloud VPC, or a bare-metal cluster) and out to operator consoles and mobile responders.

Octopus coreIngest and correlateOne incident from many sitesRules and Mission AIPolicy first, then judgementAct and auditCommands out, record writtenSite edgeCameras and VMSLive and recordedAccess and intrusionDoors, zones, badgesSensors and IoTField devicesDrones and patrolsAerial and groundSIEM and directoryCyber and identityOSINT connectorsPublic and licensedOperators and fieldBrowser consolesQueue, map, videoMobile respondersEncrypted field appDevice commandsLock, PTZ, dispatchAudit trailWho did what, when
Cameras and VMS → Rules and Mission AI → Browser consolesOne site signal travelling through the core you chose to the response it triggers.
Site edgeOctopus core
  • 01Cameras and VMS
  • 02Access and intrusion
  • 03Sensors and IoT
  • 04Drones and patrols
  • 05SIEM and directory
  • 06OSINT connectors
DecisionOctopus core
  • 01Ingest and correlate
  • 02Rules and Mission AI
  • 03Act and audit
Operators and fieldOctopus core
  • 01Browser consoles
  • 02Mobile responders
  • 03Device commands
  • 04Audit trail
04

From sizing to cutover

The same sequence in every model. Only who provisions the environment and where the bits land changes.

01 / 04Scope

Architecture and sizing
  • 01Confirm sites, connectors, and residency
  • 02Choose SaaS, cloud VPC, or bare metal
  • 03Size compute, storage, and AI inference
  • 04Map identity and network boundaries
Defense campus: sizing pack
  1. 01Confirm air-gap and local map tiles
  2. 02Size GPU nodes for on-prem inference
  3. 03Lock Entra ID / AD as the IdP
05

Your identity provider, your keys, your perimeter

Sign-in, privilege, and encryption follow the model you already run. The platform does not invent a parallel identity system.

AD · ENTRA · OIDC · SAMLDirectory and SSOActive Directory, Entra ID, Kerberos, OpenID Connect, and SAML. SCIM for account lifecycle.
PASSKEYS · HARDWARE KEYSPasswordless and MFAPasskeys, hardware security keys, authenticator apps, and one-time codes by SMS or email.
LEAST PRIVILEGERole and site authorityPrivileged actions granted by role: unlock, camera control, dispatch, export. Every grant is recorded.
DATA STAYS WHERE POLICY SAYSLocal AI and sovereigntyInference and operational data stay in the tenancy or facility your policy names. Air-gapped installs keep both local.
06

Certified for the environments that demand proof

The same certification set applies across SaaS, customer cloud, and on-premise installs where the certified scope covers the deployment.

  • ISO270012022Information security management
  • ISO270172015Security for cloud services
  • ISO270182019Protection of personal data in the cloud
  • ISO277992016Information security in health environments
  • ISO20000-12018IT service management
  • AS9100 Rev. DAerospace quality management
Security and compliance

Tell us where it has to run

Bring your hosting, residency, and air-gap constraints to the demo. We will map them to SaaS, your cloud, or bare metal.

Request a demoSecurity and compliance