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.
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
- AWSGCPAzureKubernetes
- IaCToday
- TerraformOpenTofuHelm
- SecurityThin UX
- CheckovTrivySnykSonarQubeany scanner
- CIToday
- GitHub ActionsGitLab CIJenkinsany shell
- AutomationToday
- CLIGraphQL APITerraform providerMCP
What stays, what Massdriver adds
| Area | Stays as is | Massdriver |
|---|---|---|
| CIToday | GitHub Actions, GitLab CI, Jenkins build, test, and package your code. | The last CI step calls the CLI or API to deploy the artifact. |
| IaCToday | Terraform, OpenTofu, and Helm remain the execution technology. | Packages modules as versioned bundles with typed inputs and outputs, and runs them. |
| CloudToday | Infrastructure runs in your AWS, GCP, or Azure accounts and your clusters. | Holds the cloud credential and uses it only inside deployments. |
| Existing infrastructureToday | Databases, 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. |
| AutomationToday | Scripts, internal tools, and Terraform configs you already have. | Exposes the same model through the CLI, GraphQL API, Terraform provider, and MCP server. |
| Security toolingThin UX | Scanners 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
.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