Konduit & Platform Themes

Konduit is Konstruct's always-available PaaS experience, and the flagship platform theme. Point it at a Git repository, click once, and Konduit builds the code with Cloud Native Buildpacks, ships it to a zone through GitOps, and hands back a live URL. No Dockerfile, no cluster, no YAML.

Platform Themes is the contract and plugin model underneath that experience. It's the small, versioned API that lets any frontend — Konduit, a game, your own team's internally-branded tool — drive the same platform. Konduit is one theme running on the theme contract; it's just the one every organization gets for free, pinned in the navigation, with no install step.

Beta

Konduit and Platform Themes are both in beta. Interfaces are settling fast — expect additions, not breaking removals, but treat both as evolving.

One platform, two doors

Everything here — the app you shipped with Konduit, the planet you claimed in Ship It!, the environment you created from a dropdown — is the same real infrastructure underneath: the Konstruct control plane. The same operators, the same GitOps repositories, the same Argo CD, the same cluster fleet that runs the full Konstruct IDP also runs every platform theme and every Konduit app. Themes are windows onto that control plane, not a separate stack bolted on beside it.

That means the guardrails are a choice, not a ceiling:

Eject when you outgrow it

Konduit and Platform Themes are deliberately simple — that's the point of a PaaS. When a team outgrows the guardrails, ejecting to the full Konstruct IDP (clusters, catalogs, pipelines, environments) won't be a migration. The resources were always Konstruct resources; ejecting just hands you the wheel you didn't need before. This is on the roadmap, not shipped yet.

Try it in 30 seconds

1. Open Konduit in the sidebar and pick your organization
2. Click Register app, choose a repository, and deploy
3. Watch the phases: Building → Pushing → Deploying → Live
4. Get a public URL the moment your app is Live

Every push to the tracked branch after that rebuilds and redeploys automatically.

Or drive it with your own theme

Platform themes run in a sandboxed iframe with no credential — they talk to the platform over postMessage, the same way Konduit does internally. Anything a theme can do, the signed-in user could already do. That's what makes it safe to install a retro arcade game, a generated one-off, or your own team's internal tool right alongside Konduit.

• Ship It! is a great example: a retro space game where planets are zones and rockets are apps
• Theme Starter is the minimal template to copy when building your own
• The Forge (in Themes) generates a working theme from a short description — minutes from idea to Live

Every example theme doubles as living documentation: read its source to see how the theme contract gets used in practice, not just described.

Find your page

Using Konduit day to day

• Using Konduit — environments, registering apps, redeploys, metrics
• Platform requirements — what an administrator enables on a self-hosted control plane

Understanding the platform

• The theme contract — the full reference: trust model, the client API, zones, apps, the shop, characters
• Glossary — the source of truth for theme contract terms

Building your own theme

• Themes — the model, distribution, and the Forge
• Creating a theme — the authoring guide, precise enough to hand to an AI assistant
• Theme specification — the manifest schema and the checklist
• The game formula — what makes a game theme fun, and how to avoid the anti-patterns