AWS and Google CloudAzure next

24 customer clouds.
1 desired state.

Describe your product once. Converge plans every rollout, waits for your approval and builds it inside each customer's own AWS account or Google Cloud project, then pulls drift back in line.

Fleetconverge-demo 1.2.0 → 1.3.0

0 / 24 in sync0 applying0 drifted

acmeAWS us-east-1, 1.2.0Behind
globexGCP us-central1, 1.2.0Behind
initechAWS us-east-1, 1.2.0Behind
umbrellaAWS eu-west-1, 1.2.0Behind
hooliGCP europe-west1, 1.2.0Behind
starkAWS eu-west-1, 1.2.0Behind
wayneAWS ap-south-1, 1.2.0Behind
soylentGCP asia-south1, 1.2.0Behind
wonkaAWS ap-south-1, 1.2.0Behind
tyrellAWS us-west-2, 1.2.0Behind
cyberdyneGCP us-east4, 1.2.0Behind
apertureAWS us-west-2, 1.2.0Behind
oscorpAWS eu-central-1, 1.2.0Behind
vandelayGCP us-central1, 1.2.0Behind
nakatomiAWS eu-central-1, 1.2.0Behind
monarchAWS ap-southeast-2, 1.2.0Behind
oceanicGCP europe-west1, 1.2.0Behind
sterlingAWS ap-southeast-2, 1.2.0Behind
bluthAWS us-east-1, 1.2.0Behind
dunderGCP asia-south1, 1.2.0Behind
prestigeAWS us-east-1, 1.2.0Behind
massiveAWS eu-west-1, 1.2.0Behind
gringottsGCP us-east4, 1.2.0Behind
piedpiperAWS eu-west-1, 1.2.0Behind

In sync
Applying
Drifted
Behind

one customer per bar · hover for details

[ Watch one converge ]

01
Describe
One versioned spec names everything the product needs. The same file deploys to AWS or Google Cloud, and values that differ per customer become parameters.
02
Plan
Converge reads what already runs in acme's account and shows the exact diff. Nothing moves until someone approves it.
03
Apply
Resources are built in dependency order inside their own account, each one checked healthy before the next.

01Describe

One versioned spec names everything the product needs. The same file deploys to AWS or Google Cloud, and values that differ per customer become parameters.

acme

AWS 4021 7783 1190 · us-east-1

role/convergeSpec 1.2.0

product: converge-demo
version: 1.2.0
params: [domain]
resources:
  net:     { type: network, cidr: 10.40.0.0/16 }
  app_key: { type: secret }
  uploads: { type: bucket }
  jobs:    { type: queue, max_receive_count: 5 }
  db:      { type: database, engine: postgres }
  cache:   { type: cache, network: ref(net) }
  api:     { type: service, image: api:1.2.0 }
  public:  { type: ingress, domain: param(domain) }

Same spec, on

[ Day two ]

The first deploy is the easy part.

Upgrades, drift, failures and audits are where a fleet of customer clouds gets hard. Converge handles each of them the same way, for every customer.

Canary first, then batches with a soak in between. A failure pauses the rollout before it spreads.

Rollouts · converge-demo 1.3.0

RunningApplying the canary

0 / 7 customers

Wave	Customer	Cloud	Status
Canary	acme	AWS us-east-1	Applying
Batch 1	globex	GCP us-central1	Pending
	initech	AWS eu-west-1	Pending
	hooli	GCP europe-west1	Pending
Batch 2	stark	AWS eu-west-1	Pending
	wayne	AWS ap-south-1	Pending
	wonka	GCP asia-south1	Pending

Private registries

Pull credentials are sealed once and handed to each customer's runtime.

Fleet search

Filter customers by cloud, version, drift or label, in a link you can share.

A CLI for all of it

Plan, apply, retry, tail logs and destroy from CI with the same guardrails.

[ Guardrails ]

Built for production accounts you don't own.

Deploying into someone else's cloud means safety by default, not by habit.

01
Plan before apply
Every change starts as a diff a teammate approves. Apply does exactly what the plan showed, nothing more.
plan 3f9a2c71 · awaiting approval
02
Data is never replaced
Databases, caches and buckets refuse replacement unless you allow it for that one customer.
db · replace refused
03
They hold the keys
On AWS, one IAM role locked to an external ID. On Google Cloud, a service account Converge may only impersonate. Either is revocable any time.
sts:ExternalId = cvg-acme-prod
04
Healthy, or not done
A run only finishes once every service answers its health check. Otherwise the environment is marked degraded.
GET /healthz 200 · 3/3 tasks
05
Teardown takes their name
Destroying a customer lists everything that will be deleted, and an admin has to type the environment ID to go ahead.
type acme-prod to confirm
06
Roles for the team
Viewers watch. Operators plan, apply and retry. Admins onboard customers, publish versions and approve teardowns.
viewer · operator · admin

[ Your turn ]

Every customer on the version you approved.

Onboard a customer on AWS or Google Cloud, review their first plan and roll the next version out to the whole fleet, all from one console.

clouds, one spec: 2
manual steps per customer: 0
approval per rollout: 1

Rollout

converge-demo 1.2.0 → 1.3.0

0 / 8 in sync

Customer	Cloud	Version	Status
acme	AWSus-east-1	1.2.0	Applying
globex	GCPus-central1	1.2.0	Pending
initech	AWSus-east-1	1.2.0	Pending
umbrella	AWSeu-west-1	1.2.0	Pending
hooli	GCPeurope-west1	1.2.0	Pending
stark	AWSeu-west-1	1.2.0	Pending
wayne	AWSap-south-1	1.2.0	Pending
soylent	GCPasia-south1	1.2.0	Pending

24 customer clouds.1 desired state.

Describe

Plan

Apply

01Describe

The first deploy is the easy part.

Private registries

Fleet search

A CLI for all of it

Built for production accounts you don't own.

Plan before apply

Data is never replaced

They hold the keys

Healthy, or not done

Teardown takes their name

Roles for the team

Every customer on the version you approved.

24 customer clouds.
1 desired state.