Multi-cloud — AWS, GCP, Kubernetes
Same service definition deploys to AWS Lambda, ECS Fargate, GCP Cloud Run, GKE Autopilot, or self-hosted Kubernetes. Switch templates; the service stays the same.
Why this matters
The point of a multi-cloud abstraction isn’t to deploy to all clouds at once — it’s that you pick the right one for the workload and switch when you need to. SC services declare what they need (a container, a connection string, an outbound CNAME); the template you pick decides which cloud handles it.
For our flagship product Forge, this concretely means:
- Reasoning agents run on AWS Lambda — cheap, time-boxed, perfect for ~5-minute prompt sessions.
- Long-running runtime workers run on Fargate — no 15-minute Lambda cap.
- Marketing sites run on AWS S3 + CloudFront via
aws-static-website.
Same parent: forge/infra. Three templates: aws-lambda, ecs-fargate, aws-static-website. Three deployments. One mental model.
What’s actually shipped
The templates and resources below are what the current SC CLI provisions out of the box:
Compute templates
| Template | Cloud | Use case |
|---|---|---|
aws-lambda | AWS | Time-boxed serverless |
ecs-fargate | AWS | Long-running containers |
aws-static-website | AWS (S3 + CloudFront) | Static sites / SPAs |
cloudrun | GCP | Managed containers |
gcp-gke-autopilot | GCP | Managed Kubernetes |
gcp-static-website | GCP (GCS + Cloud CDN) | Static sites |
kubernetes-cloudrun | any k8s | Self-hosted or managed |
Data + integration resources
| Resource | Behind the scenes |
|---|---|
mongodb-atlas | MongoDB Atlas managed cluster |
aws-rds-postgres | AWS RDS for Postgres |
gcp-cloudsql-postgres | GCP Cloud SQL for Postgres |
kubernetes-helm-postgres-operator | Postgres on your k8s cluster |
kubernetes-helm-mongodb-operator | MongoDB on your k8s cluster |
kubernetes-helm-redis-operator | Redis on your k8s cluster |
kubernetes-helm-rabbitmq-operator | RabbitMQ on your k8s cluster |
gcp-redis | GCP Cloud Memorystore |
s3-bucket, ecr-repository | AWS storage + container registry |
cloudflare | DNS zones + registrar |
Buyer-friendly + acquirer-friendly
A subtle but important property: because SC abstracts the compute layer, customers aren’t locked into one cloud. Equally, a potential acquirer can absorb an SC-based platform without rewiring everything — the abstraction makes the underlying cloud swappable.
Ship your infrastructure on autopilot.
Try the SC parent stack in your own repo, or see what we built on top of it — Forge, our flagship AI workflow engine for teams.