Keep claims and care apps answering when a cloud fails
- Uptime SLA
99.999%
- reduction in cloud spend
30–50%
- Use any service from AWS, GCP, or Azure
600+
Built for regulated health data
The platform's controls are audited. Your application's own controls and agreements stay yours.
HIPAA
Control Plane's compliance program covers HIPAA. Ask us for the documents your security review needs.SOC 2 Type II
Control Plane completed the AICPA SOC 2 Type II audit, performed by Prescient Assurance.Encrypted in transit and at rest
Data is encrypted in transit and at rest, and workloads talk to each other over mutual TLS across regions and clouds.Immutable audit trail
Every action by people, service accounts and agents is recorded and attributable, on every provider in the Global Virtual Cloud.
Payers and providers on Control Plane
When the provider's app stops, so does the claim
A visit becomes a claim, the claim goes to the payer, and the payer pays the provider. Every step runs on an app. When one of them is down, the claim waits, and so does the payment.
On Control Plane those apps run in more than one location at once, so a failed zone, region or provider sends users to the location that is still serving.
Claims and eligibility that keep answering
Claims intake, eligibility checks, member portals and the analytics behind them serve from more than one provider at once, in the AWS, GCP or Azure regions you choose. Open enrollment and month-end spikes add replicas where the traffic lands, and Capacity AI sizes each container to what it uses, so the second provider doesn't double the bill.
30–50% · Cut compute spend
Patient portals and scheduling for providers
Patient portals, scheduling, care coordination and the integrations between clinical systems run active-active, so staff and patients reach a working app while a failed location drops out of routing.
The EHR stays where it is. Cloud Wormhole connects these apps to its database in your data center or VPC without opening the firewall, and your clinical recovery plans stay yours.
Least-privilege access · Micro-segmentation · Encryption · Immutable audit trail
Choose where patient data runs, location by location
A Global Virtual Cloud lists exactly which locations it runs in. A US-only app stays on US regions across AWS, GCP and Azure, and a Canadian or EU deployment gets a Global Virtual Cloud of its own.
Adding or removing a region is a change to the spec, not a new environment to build and certify from scratch.
Runs in your own accounts · Credits and commitments still count
How claims and care apps stay up on Control Plane
Example: a payer's provider portal on Azure adds GCP
A payer runs a provider portal on Azure that hospitals use every day to check eligibility and submit claims. Its database lives in the payer's own data center.
Reach the database in place
A Cloud Wormhole agent runs inside the data center, so the app reaches its database privately from any location.Run the app on two providers
The app deploys to Azure East US 2 and GCP us-east1 from one spec. Both serve traffic, and both are in the US.Route on health
Readiness probes take a failing replica out of the pool, and geo-DNS sends each hospital user to the nearest healthy location.Drill it on a schedule
Take one location out of routing during a quiet hour and record the result for the contingency-plan test.
cpln apply --file provider-portal-gvc.yaml
kind: gvc
name: provider-portal
spec:
staticPlacement:
locationLinks:
- //location/azure-eastus2
- //location/gcp-us-east1 # US regions only
locationOptions:
- locationLink: //location/azure-eastus2
routingTier: 0
- locationLink: //location/gcp-us-east1
routingTier: 0 # both serve
Healthcare teams on Control Plane

“We migrated 8 environments from AWS to Control Plane and no one noticed! Everything just worked. It sounds anticlimactic, but I'm telling you, that's not the norm. What the team at Control Plane is doing is rocket-science-level work.”
See your claims app on two providers
Book a demo and we'll map a failover drill to your contingency plan.

