That's the moment worth writing down. Not because a PaaS deploy is novel in 2026, but because of everything underneath it that didn't exist nine months ago.

The arc​

0.1 (November 2025) was the skeleton of an internal developer platform: organizations, team management clusters, cluster provisioning, GitOps with Argo CD wired in from the first commit. Honest work, nothing flashy.

0.2 (December) made applications self-propelled. Environments and pipeline templates meant a registered repo built its own container, published its own auto-generated Helm chart, and rode multi-stage delivery to any environment — zero configuration, with an eject path to your own CI when you outgrow ours.

0.3 (January) was independence day: no more kubefirst dependency, one umbrella Helm chart, installable on any Kubernetes cluster with no pre-existing infrastructure. The operator bootstraps Argo CD, the GitOps repository, and the platform apps itself.

0.4 (March) launched the business model. The hosted control plane went live — sign up, create an org, provision a management cluster without installing anything — and workload clusters went multi-cloud: Civo, AWS, and GCP from a single management cluster.

0.5 (May) matured multi-tenancy with one mental model for global versus org-scoped resources across every shareable thing on the platform, and made AI a first-class operator: MCP-flavoured API keys so assistants like Claude Code can drive Konstruct directly.

0.6 (July) broadened and hardened: GitLab as a first-class git provider next to GitHub, a rank-based RBAC overhaul, platform-wide broadcasts, MCP diagnostics endpoints so an AI assistant can troubleshoot the platform itself, and a pile of GitOps reliability work.

0.7: the platform gets a personality​

0.7 is my favorite release so far, and not just because it's the newest.

Platform Themes are the headline. The theme-driven PaaS surface got a clean, no-aliases cutover, and the idea underneath deserves the spotlight: a small, versioned contract that lets any frontend drive the same platform. Konduit is the flagship — the clean business PaaS every organization gets pinned for free. But the same contract powers Ship It!, a retro arcade game where planets are zones and rockets are real deployments with real URLs, and Metropolis, which renders your organization as a living 3D city — builds raise construction cranes floor by floor, a failed app is a three-alarm fire, and rooftop gauges draw from real metrics. Themes are views, not silos: switch themes and your zones and apps are all still there, because they were always just platform resources.

The build plane got its shape. Themes and apps build on the control plane — shared kpack and Harbor for every organization — and serve on zone clusters, which are ordinary workload clusters. That's the machinery behind my eight-minute deploy: kpack noticed my commit within a minute, built with Cloud Native Buildpacks, pushed to Harbor, the operator committed the manifest to GitOps, and Argo CD rolled it onto the zone.

The platform team became a tenant of its own product. 0.7's organization model gives the platform team a visible platform organization that owns the control plane — it shows up in their clusters graph with every other org's management cluster ghosted alongside for the admins. The control plane is owned now, not ambient.

Civo Bare Metal (alpha) brings your own data center into the same pane of glass, powered by Colony: racked servers become discoverable hardware, hardware becomes Kubernetes, and those clusters are first-class Konstruct clusters with the same catalog, environments, and templates as your cloud fleet.

And the detail I love most: the docs now include a page on the game formula — why game themes work, with a ready-to-paste prompt for building your own theme with an AI assistant, starting from our theme-starter template. We designed part of the platform to be extended by people describing what they want in a sentence. That's where this industry is going, and I'm glad we're leaning in rather than pretending otherwise.

What nine months taught me​

The pattern in the release notes is the same one I've preached my whole career: build the engine before the paint. 0.1 through 0.3 built the engine. 0.4 and 0.5 made it a product you could host and share. 0.6 made it enterprise-shaped. Only then did 0.7 give it a personality — and because the engine was real, the personality is real too. The game isn't a demo; the city isn't a mockup. Every crane is a build and every fire is an incident.

Think big, build small, ship weekly. See you in 0.8.