Runtimes are yours to customize
Lambda, ECS, and Kubernetes are where you start. Add the tooling your org requires, like your logging agent, secrets store, scanners, or service mesh, or package a runtime from the Terraform, OpenTofu, or Helm you already maintain. Runtimes are versioned, so changes roll out without touching an app.
lambda
FunctionsThin UX
APIs and event handlers that scale to zero. IAM role, VPC access, and log groups come with the runtime.
ecs-service
ContainersThin UX
Long-running services and workers on ECS with load balancing, autoscaling, and service discovery decided once.
kubernetes
KubernetesThin UX
Deployments, cron jobs, and workers on a cluster your platform team already runs, packaged as Helm.
your own
Whatever you runThin UX
Your own Terraform, OpenTofu, or Helm, with the agents, sidecars, and checks your org requires built in.
Fix it once and every app gets it
When the platform team patches a runtime, every app on it picks up the change on its next deploy. Nobody opens the same pull request against forty repos.
Developers only describe what their code talks to: Postgres, Redis, a queue, another service.
The deploy stays the same. The runtime underneath becomes yours.
Thin UX
$mass deploy billing-api --env prod
beforeseed
buildpack-web@1.0massdriver catalog
- buildpack
- postgres
- tls
- logs
afterseries a
acme/ecs-service@1.0your platform team
- +docker image
- +ecs service
- postgres
- tls
- logs
- +checkov gate