Technology1 min read

Introducing Pulumi Delivery: your release pipeline as code

By · Published by Everything Blog

In short

The new public preview tool lets organizations write release pipelines using established programming languages like TypeScript, Python, Go, HCL, and YAML. Teams define target repositories, stages, stack updates, and promotion gates directly inside their deployment programs. Pulumi Cloud then manages execution across these environments, automatically pausing changes for necessary approvals before production rollouts. This code-first approach enables automated coding agents to navigate releases without requiring separate console access.

Key points

  • Consolidating deployment logic into code allows infrastructure policies and review workfl…: Consolidating deployment logic into code allows infrastructure policies and review workflows to govern application delivery.
  • Unifying release pipelines helps automated coding agents deploy software without relying…: Unifying release pipelines helps automated coding agents deploy software without relying on disconnected consoles or external files.
  • Eliminating standalone configuration scripts reduces the operational friction commonly se…: Eliminating standalone configuration scripts reduces the operational friction commonly seen in multi-stack application deployments.

Sources checked by our analysis pipeline: 1

Coding agents have made writing software faster than shipping it. The bottleneck is now everything after the code: release pipelines full of bespoke scripts, console steps, and hand-run promotions that slow teams down and don’t scale.

Today, we’re introducing Pulumi Delivery, available in public preview. With Delivery, you define how a change moves from development through staging to production in the same languages you already use for infrastructure: TypeScript, Python, Go, HCL, YAML, and more. Your pipeline becomes a Pulumi program, so it gets the same policies and review process as the rest of your infrastructure, whether a person or an agent wrote the change.

The new bottleneck

Most applications span many infrastructure stacks. For example, your service may have separate stacks per environment for its networking layer, database, and application code, and they need to be deployed in the correct order. Today, that ordering and the rest of your delivery logic live in standalone pipeline files and manual console steps. Those tools run separately from your infrastructure, your secrets, and your policies, so the rules you enforce on a…

Technology