Keep the pipeline for what it is good at: compiling, testing, and pushing an image or zip. Its last step hands the artifact to Massdriver.
From pipeline-driven delivery to environment-modeled delivery.
CI builds, tests, and packages
You, or an agent, state the deploy
The request names the app, the artifact, and the target environment. It does not describe how to reach the cloud.
Massdriver resolves it against the environment
Cloud credentials, networks, and connections are registered once, along with what is using each of them. The deploy picks up the right ones for that environment, so nobody copies keys, VPC IDs, or connection strings between pipelines. The delivery workflow does not have to reconstruct the environment from variables, outputs, and disconnected configuration.
Typed dependencies decide the wiring
Resources emit typed outputs and apps declare typed inputs. A postgresql output satisfies a postgresql input, so connection details, IAM, and network rules flow in without copy and paste.
Approved infrastructure runs underneath
Each change is planned, checked against policy, approved if the environment requires it, and executed with Terraform, OpenTofu, or Helm in a short-lived worker that holds the credentials.
The environment stays understandable
The result of the deployment remains part of the same model: what was deployed, which infrastructure it uses, what it depends on, what depends on it, and what controls apply.
Humans, automation, and agents can start the next change with that context already available.
The next change starts from the same model
Upgrades, new dependencies, and promotions to prod all operate on the environment. Impact analysis comes from the graph, and policy applies the same way every time.