ROC as a Service

Your operations center, hosted your way

A remote operations center is software, not a building. Run it in our cloud, in your own cloud account, or entirely on-premise — and change your mind later without changing product.

Isometric scene of one operations centre served from a cloud platform to on-premise consoles and a video wall
Deployment

Three ways to run the same software

Kubernetes in the cloud, Docker Compose at the edge — identical artifacts.

Our cloud

The fastest path: we operate it, you log in. Suited to teams who want operations capability rather than infrastructure ownership.

Your cloud

Deploy into your own account — AWS, Hetzner, DigitalOcean and similar — choosing the region that fits your data and latency requirements.

Fully on-premise

Air-gapped or site-local deployment with the same software, for operations where nothing may leave the facility.

Locality

Where your data lives is a decision, not a default

Pick the region, pick the latency

Remote operations are sensitive to both jurisdiction and round-trip time. Deployment choice is how you control each.
  • Data residencyChoose the provider and region so that footage and telemetry stay inside the legal boundary your organisation operates under.
  • Latency to the operationPut the compute close to the aircraft. For live control, the distance between operator and vehicle is measured in milliseconds, not kilometres.
  • Same software everywhereKubernetes in the cloud and Docker Compose on-premise run the same artifacts, so on-prem is not a stripped-down variant.
Data locality
LEGAL BOUNDARYOTHER REGIONCLOUD · YOUR REGIONshortround tripKUBERNETESDOCKER COMPOSEON-PREMISEOPERATORAIRCRAFTFOOTAGE · TELEMETRYleave the boundaryROUND TRIPvia another region
Footage and telemetry go wherever the compute runs. Remote operations are sensitive to both jurisdiction and round-trip time.

Design your deployment

Tell us your data-residency and latency constraints and we will map them to an architecture.