Skip to content
Manufacturing & logistics

Keep lines and shipments moving when a cloud region doesn't

Run plant, warehouse and transportation apps active-active in a Global Virtual Cloud that includes your own plant and warehouse servers alongside AWS, GCP and Azure. When a region fails, sites keep serving locally and cloud traffic moves to healthy locations. Workloads with at least two replicas in at least two locations are backed by a 99.999% SLA.
Uptime SLA

99.999%

reduction in cloud spend

30–50%

Use any service from AWS, GCP, or Azure

600+

Manufacturers and logistics teams on Control Plane

Make the plant a location, not a dependency

Scheduling, recipes, quality checks and the ERP and MES integrations behind them now run partly in the cloud, so a regional outage can stop a line whose machines are fine.

Managed Kubernetes turns any Linux server into a node, including the servers on your plant floor. Those servers join the same Global Virtual Cloud as your cloud regions, so line-side workloads run in the plant and the cloud locations add capacity and failover.

Control Plane runs the applications around the line, not the PLCs or safety systems on it.

Deploy onceRun everywhere you choose
Your appGPU pool on LambdaEKS clusterAzure region

Runs in your own accounts · Credits and commitments still count

Keep orders shipping through a regional outage

Warehouse and transportation management, order fulfillment and shipment tracking serve from distribution-center servers and cloud regions at the same time. A failed region drops out of routing while pickers, dispatchers and customers tracking an order reach the locations still up.

Peak season adds replicas where the orders arrive, and Capacity AI sizes each container to what it uses, so peak capacity doesn't sit idle the rest of the year.

Capacity AIRight-sized scaling
Static provisioning
Capacity AI allocationActual demandStatic provisioning

30–50% · Cut compute spend

Reach plant systems without opening the plant

ERP, historians and MES databases sit behind the plant firewall for good reason. Cloud Wormhole runs an agent inside that network and connects workloads to those private endpoints without exposing them to the internet.

The same workloads reach cloud services through Universal Cloud Identity, so a forecasting job can read the historian on site and write to BigQuery without a stored key anywhere.

Zero-trustEvery substrate
VMsBare metalKubernetes

Least-privilege access · Micro-segmentation · Encryption · Immutable audit trail

SOC 2 Type IIPCI DSS Level 1HIPAAGDPR

Plants in two jurisdictions, one way to run them

A manufacturer with plants in the US and Germany can give each region its own Global Virtual Cloud, so each plant's data stays on locations in its own jurisdiction, managed from one console and one spec format.

Any infrastructureOne virtual cloud
KubernetesCloud accountsData centers

VMs · Bare Metal · Edge — Networking · Identity · TLS · Observability · Failover

How plants and warehouses stay up on Control Plane

Example: a plant in Bavaria with a cloud behind it

A manufacturer runs scheduling and vision-based quality inspection for a plant in Bavaria and needs both to survive a cloud outage and a plant server failure.

  1. Plant

    Join the plant servers

    Servers in the plant join as a Managed Kubernetes location and run the line-side services locally.
  2. PlantFrankfurt

    Add an EU cloud location

    A Control Plane location on AWS eu-central-1 in Frankfurt joins the same Global Virtual Cloud as the standby, so the plant's data stays in the EU.
  3. PlantFrankfurt

    Set the order

    The plant serves first. The Frankfurt location sits on a standby routing tier and takes traffic only if the plant location is down.
  4. PlantFrankfurtGPU cloud

    Inspect on the GPUs you have

    Vision models run on a GPU server in the plant, and a GPU location on a neocloud or cloud can join the same Global Virtual Cloud as the fallback.
plant-gvc.yaml

cpln apply --file plant-gvc.yaml

kind: gvc
name: plant-bavaria
spec:
  staticPlacement:
    locationLinks:
      - //location/bavaria-plant-1  # plant servers
      - //location/aws-eu-central-1
    locationOptions:
      - locationLink: //location/bavaria-plant-1
        routingTier: 0
      - locationLink: //location/aws-eu-central-1
        routingTier: 1  # standby

Security that reaches the plant floor

The same controls apply on a plant server as in a cloud region.

  1. Zero-trust networking

    Deny-by-default firewalls on every workload, and mutual TLS between workloads across plants, regions and clouds.
  2. No stored keys

    Universal Cloud Identity issues short-lived credentials, so nothing on a plant server can be copied and reused.
  3. Immutable audit trail

    Every action by people, service accounts and agents is recorded and attributable.
  4. SOC 2 Type II

    Control Plane completed the AICPA SOC 2 Type II audit, performed by Prescient Assurance.

Manufacturing & logistics teams on Control Plane

“Thanks to Control Plane, we've mastered multi-cloud management, fine-tuned Kubernetes efficiency, and saved substantially on costs.”

Jay Eberhard, Senior Platform Engineer, Outrider

Read the case study

Put a plant server in your cloud

Book a demo and we'll join a Linux server to a Global Virtual Cloud while you watch.

Run Unbreakable
Apps and Agents

Sign up free. No cloud accounts required.