Skip to content

Keep what already works

Your build system, IaC, and cloud keep doing their jobs. Massdriver moves the knowledge of the environment out of the deployment glue and gives those tools one shared model of what they are acting on.

Your existing tools keep doing their jobs. They no longer have to be the model of the environment.

CI builds and tests. Terraform, OpenTofu, and Helm make infrastructure changes. Massdriver manages the environment those changes happen in.

CloudToday
AWS
GCP
Azure
Kubernetes
IaCToday
Terraform
OpenTofu
Helm
SecurityThin UX
Checkov
Trivy
Snyk
SonarQube
any scanner
CIToday
GitHub Actions
GitLab CI
Jenkins
any shell
AutomationToday
CLI
GraphQL API
Terraform provider
MCP

What stays, what Massdriver adds

AreaStays as isMassdriver
CITodayGitHub Actions, GitLab CI, Jenkins build, test, and package your code.The last CI step calls the CLI or API to deploy the artifact.
IaCTodayTerraform, OpenTofu, and Helm remain the execution technology.Packages modules as versioned bundles with typed inputs and outputs, and runs them.
CloudTodayInfrastructure runs in your AWS, GCP, or Azure accounts and your clusters.Holds the cloud credential and uses it only inside deployments.
Existing infrastructureTodayDatabases, networks, and clusters you already run stay where they are.Imports them as resources so new apps can depend on them, where the resource type is supported.
AutomationTodayScripts, internal tools, and Terraform configs you already have.Exposes the same model through the CLI, GraphQL API, Terraform provider, and MCP server.
Security toolingThin UXScanners and policy tools you run today keep running.Bundles can run checks such as Checkov at publish and deploy time.

One line in the pipeline you have

Your workflow keeps building and pushing the image. Instead of a deploy job full of Terraform and credentials, it hands the artifact to the environment.

.github/workflows/ship.ymlConcept syntax
A CI workflow that builds and tests, then hands the deploy to Massdriver
- run: npm test
- run: docker build -t $IMAGE . && docker push $IMAGE
- run: mass deploy billing-api --env dev --image $IMAGE

Plug it into your stack