Deployment
Choose the deployment model that fits your organisation.
Deployment Options
ContinueOps is available as managed SaaS, a hybrid connector, or a self-hosted appliance. Choose the model that matches your data residency, network, and operational requirements.
Managed SaaS (Recommended)
Included in every plan
The fastest way to get started. We host the control plane and execution agent; you access the dashboard and API. Tenant isolation, encrypted storage, and automatic updates are included.
Sign up and start building runbooks immediately
Always on the latest release with no maintenance windows
Row-level security and encrypted storage per tenant
No extra hosting charges
Hybrid Connector
ContinueOps hosts the control plane while a signed Rust connector runs inside your VPC. Runbooks are fetched over mTLS and executed locally, so cloud credentials never leave your network.
Control plane - runbook editor, approvals, audit log, dashboards.
- Runbook registry
- Approvals (HOL)
- Evidence + reports
Signed binary. Pulls runbooks, executes locally, streams results.
IAM credentials never leave this boundary.
- Outbound-only mTLS - No inbound ports; works behind NAT and firewalls
- Credentials stay local - IAM roles and secrets remain in your VPC
- Lightweight binary - Single statically-linked executable with signed releases
Self-Host (ContinueOS Appliance)
Run the full stack on your own infrastructure for complete control over data residency and update cadence. Ships as a pre-configured appliance image.
- Bootable ISO / VHD / RAW / OVA - Deploy to bare metal, VMware, Hyper-V, Proxmox, or KVM
- Air-gapped updates - Apply signed update bundles without outbound connectivity
- No inbound ports - Outbound-only mTLS to any required services
Supported Distributions
ContinueOS images and packages are built for common platforms and orchestrators.
- AWS Marketplace AMI - Launch via the EC2 console or CloudFormation
- ISO, VHD, RAW and OVA - Bootable images for on-premises and private cloud
- Kubernetes-ready - Helm chart and container images for Kubernetes deployment
- Offline update bundles - Signed patches for restricted environments
System Requirements
Recommended sizing for self-hosted and hybrid deployments.
- Minimum - 8 vCPU / 32 GB RAM / 200 GB SSD
- Recommended - 8 vCPU / 64 GB RAM / 200 GB SSD
- Network - Outbound HTTPS (443) only; no inbound ports required