Massdriver

Massdriver solves the problem of developers struggling to use infrastructure as code (IaC) written by platform teams. It allows ops teams to package their Terraform, Helm, and other modules into visual, self-service components so developers can deploy infrastructure without writing code, touching YAML, or waiting on tickets.

A bundle is your IaC (Terraform, Helm, etc.) wrapped with schemas, policies, and guardrails. It turns raw infrastructure code into a reusable component that validates inputs, enforces best practices, and connects to other infrastructure automatically.

Developers use Massdriver by dragging and dropping bundles onto a canvas to build their architecture visually, connecting them together, filling out forms for configuration, and hitting deploy. No Terraform, no pipelines, no YAML are required.

'Pipelineless' means you don't maintain CI/CD pipelines for infrastructure changes. When a developer makes a change, Massdriver spins up a temporary execution environment, runs your IaC, then tears down the environment. Only the deployment environment is ephemeral.

No, you write the IaC. Platform teams use the IaC tools they already know (Terraform, OpenTofu, Helm, CloudFormation) to define infrastructure, then wrap it in a bundle spec. Massdriver orchestrates and automates the IaC you've already written.

Massdriver ships with an HTTPS-based state backend that works out of the box with zero configuration. State is automatically scoped per project, per environment, per module. You can also configure your own backend if needed.

Massdriver prevents drift by design. Developers can only deploy through approved bundles with guardrails, eliminating 'shadow IT.' The visual canvas serves as the source of truth, and changes go through Massdriver's orchestration.

Massdriver works with Terraform, OpenTofu, Helm, CloudFormation, and Azure Bicep. You're not forced into a proprietary language and can use your preferred tool.