Skip to content
Financial services

Keep risk and research running when a cloud goes down

Run research, risk and client-facing apps active-active in a Global Virtual Cloud across AWS, GCP, Azure and Oracle Cloud Infrastructure (OCI). When one provider fails, users are routed to the locations that are still up. 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+

Controls you can hand an examiner

Control Plane is certified for the standards card data and customer records fall under. The controls in your own application stay yours to certify.

  1. PCI DSS Level 1

    Control Plane is a Level 1 PCI DSS compliant platform, assessed on site every year. A responsibility matrix shows which controls are ours and which are yours.
  2. SOC 2 Type II

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

    Every action by people, service accounts and agents is recorded and attributable, across every provider in the Global Virtual Cloud.
  4. Least-privilege access

    Fine-grained policies decide who and what can touch each workload, secret and cloud service, with short-lived credentials instead of stored keys.

Hedge funds and investment banks on Control Plane

Research compute that grows with the backtest

Quant research arrives in bursts: a backtest across ten years of tick data, a model retrain, a parameter sweep. On Control Plane those jobs run on workers that scale with the queue and drop to zero when it empties, across every location in your Global Virtual Cloud.

GPU work can run in any location with GPUs, including a neocloud or your own servers joined to the same Global Virtual Cloud, so a GPU shortage at one provider doesn't stall the research team.

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

30–50% · Cut compute spend

Risk and client apps on more than one provider

Risk analytics, client portals and the services behind them serve from more than one provider at the same time. When a provider fails, users are routed to the locations still up, with no restore step and no runbook.

Existing clusters join as locations through Bring Your Own Kubernetes, so nothing is rebuilt. The second location runs lean: autoscaling grows it as traffic arrives and Capacity AI sizes each container to what it uses.

Any infrastructureOne virtual cloud
KubernetesCloud accountsData centers

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

Regulators want a tested exit plan. Make it a drill.

On Control Plane the second provider is already part of the Global Virtual Cloud and already taking traffic. Testing the exit means taking one location out of routing and checking that customers land on the other.

The same GVC spec runs on every provider. The plan you show an examiner is the configuration you run in production.

Zero-trustEvery substrate
VMsBare metalKubernetes

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

SOC 2 Type IIPCI DSS Level 1HIPAAGDPR

How a fund or a bank stays up on Control Plane

Example: a quant research platform adds a second provider

A hedge fund runs its research platform and risk service on EKS in AWS us-east-1. Backtests queue up when capacity runs short, and the risk service has no second provider.

  1. EKS

    Bring the existing cluster in

    The EKS cluster joins Control Plane as a location through Bring Your Own Kubernetes. Nothing is rebuilt.
  2. EKSus-east4

    Add a second provider

    A Control Plane location on GCP us-east4 joins the same Global Virtual Cloud. The risk service deploys to both from one spec, and both serve.
  3. EKSus-east4GPU cloud

    Add GPUs where they are

    A GPU location on a neocloud joins as well, and backtest workers scale with the queue in whichever location has room.
  4. EKSus-east4GPU cloud

    Run the exit drill

    Take AWS out of routing during a quiet hour. The risk service keeps answering from GCP, and the audit trail records every step.
research-gvc.yaml

cpln apply --file research-gvc.yaml

kind: gvc
name: research
spec:
  staticPlacement:
    locationLinks:
      - //location/fund-eks-us-east-1  # existing EKS cluster
      - //location/gcp-us-east4
      - //location/gpu-neocloud  # GPU servers
    locationOptions:
      - locationLink: //location/fund-eks-us-east-1
        routingTier: 0
      - locationLink: //location/gcp-us-east4
        routingTier: 0  # both serve

Financial services teams on Control Plane

“For every minute that our sales tax API, if it were to go down, our customers are not able to collect roughly $4,000,000 in sales tax that they should be collecting.”

Pujun Bhatnagar, Co-Founder and CEO, Kintsugi

Read the case study

Test your exit plan on a live second provider

Sign up free, or book a demo and we'll walk through a failover drill on your stack.

Run Unbreakable
Apps and Agents

Sign up free. No cloud accounts required.