PowerPlan CD Platform

PowerPlan Continuous Delivery Platform

How a code change reaches production, tested and on record

Each team builds its service; the platform combines every part of a product into one tested version, and that version moves to an environment only through a recorded, reviewable change.

State as of 28 October 2026First product in the development landscape

Overview diagram: a team's change is packaged, combined into a product version, tried in a test environment, approved, then promoted to production on purpose
The journey of a change. Open the interactive diagram

Start where you are

Service developers

Build a service

The one file you own, how your build becomes a service chart, and what can stop it.

Build a service Product teams

Own a product

The product repository and the five CD workflows that make, approve and promote a version.

Own a product CloudOps, environment owners

Run environments

cloud-config, the environment pipeline, Flux and the runbook.

Run environments Leads, new joiners, everyone

See the big picture

A 10-minute story that follows one line of code to production, in plain words.

Read the story

Where things stand

Environment pipeline failing since 26 October 2026 broken

No environment apply, and so no promotion, can complete. The fix has two steps: cloud-config moves to the current shared workflow (done on 26 October), and environment chart 0.5.0 is published (pending). Test environments still receive new candidates through Flux. Details

No qa or prod environments yet planned

Only dev/app01 exists today. Promotion to qa and prod is not possible until greenfield IaC creates those environments: CD · Promote and CD · Release stop at their first step. Details

built Working today

  • Service, data-pipeline and analytics packaging
  • Product versions (compositions), candidate and approved
  • Automatic approval after a healthy run in dev
  • dev environments follow every new candidate
  • Settings-only changes make a new version

built, not live Waiting to be switched on

  • Promotion to qa and prod: built, but there are no qa or prod environments to promote to yet
  • Release numbers (1.4.0): built, not yet run; waits for qa too
  • Clean-up of old versions: report only
  • One identity per environment: chart release pending

planned Next

  • Deploying data pipelines and analytics bundles (placeholders today)
  • Deploying a release number to qa
  • qa, nonprod, preview and prod environments, created by greenfield IaC
  • Hotfix branches

Go deeper

Reference

The building blocks, the files each repository owns, and the two pipelines, one short section each.

How the platform works

Deep dive

The first product end to end: stages, values tracer, Flux, runbook, decisions and gotchas.

Technical deep dive

Diagrams and slides

Every interactive diagram and slide deck in one place, with who each one is for.

All diagrams