Skip to content
Plinth

Plinth

The load-bearing base for enterprise internal tooling.
Try it in 60 minutes Read the manifesto Browse the architecture

What Plinth gives a team

Section titled “What Plinth gives a team”

A fleet of internal applications — project management, change requests, audit dashboards, HR tooling, internal admin — sharing one substrate, one SDK, one scaffolder. Modules import the platform; they don’t re-implement it.

  • Substrate. A Helm umbrella chart that brings up the entire reference architecture on a fresh Kubernetes cluster. Identity, authorization, secrets, data, observability, security, GitOps, dev portal — one helm install.
  • SDK. Versioned Go and TypeScript packages encoding the platform contracts: fail-closed Cerbos client, audit publisher, OTel wiring, typed errors, healthcheck, server-action forms. Imported, not copy-pasted.
  • Scaffolder. A CLI (plinth new <module>) and a Backstage software template. Five minutes from idea to deployed-in-dev.
  • Manifesto. Six commitments — zero standing trust, GitOps everything, immutable infrastructure, durable workflows, evidence by default, open source first. The opinions that shape every default.

Who it’s for

Section titled “Who it’s for”

Organisations that run multiple internal-facing modules, operate in a regulated context (banking, finance, insurance, healthcare, government), prefer on-premise or private-cloud deployment, and have a small platform team supporting a much larger app-developer audience.

Not for single-product startups, cloud-native teams already happy with managed services, or teams uncomfortable operating Kubernetes.

Where to go next

Section titled “Where to go next”