Private beta Runs in your clusters

The Internal Developer Platform you sell as your own.

A complete IDP, carrying your name, your colours and your engineering standards: developer portal, GitOps delivery, a Kubernetes control plane, identity, guardrails and observability. One container image serves every brand you run, so the tenth costs what the second did.

Access is granted team by team: no download, no public repository. In private beta.

1 imageserves every brand you sell
~10 minmake up to a running platform, on a laptop with Docker (8 GiB), kind and Node already on it
1 objectonboards or offboards a team
portal.keystone.example/scorecards
The platform's scorecards page: an estate score of 74, the standards that are failing most often, and the owners furthest behind.

Screenshots on this page are the real product, captured from a running instance. Nothing here is a mockup.

What your customers get

A platform, not a portal with a logo on it.

Most "IDP" products stop at a catalogue. This one ships the machinery underneath: what actually deploys, what actually provisions, what stops a team doing something they should not, and what proves any of it happened.

Developer portal

A service catalogue, TechDocs, API docs, search and live Kubernetes state, with your brand's plugin set, decided in config rather than in a build.

GitOps delivery

Argo CD, app-of-apps, sync waves. Git is the only way into the cluster, including the control plane's own configuration, so drift is a diff, not an incident.

A real control plane

Crossplane, with your own API on top of it. Onboarding a team is one object; offboarding is deleting it. Cloud resources are the same claim pointed at a different provider.

Guardrails that hold

Kyverno at admission and Pod Security enforced by the API server itself. Ownership labels, pinned images, resource limits, a registry allowlist, and tests proving each rule does what it says.

One set of identities

Keycloak groups authorise the namespace, the delivery project and the portal. Add a team in one place; there is no second list to drift out of step.

Standards you can score

Every service graded against your engineering standards, with the remedy for each failure on the page the owner is already looking at. Each brand decides what "good" means.

The white label

Same build. Different product.

Two brands below. Different name, palette, typography, hostnames, identity realm, logo, plugin set and engineering standards, running the same container image, from one configuration file. Switch this page and the screenshots at the same time:

This page re-skins itself too; that is the same mechanism the portal uses.
portal.keystone.example
The service catalogue in the current brand's colours.

The catalogue: brand name, palette and rail all follow the config.

portal.keystone.example/scorecards
Scorecards in the current brand's colours, with that brand's own standards.

Look at the standards, not just the colours: Acme weights documentation and GitOps higher, drops criticality, and uses its own annotation namespace, so the same estate scores differently.

What a rebrand actually costs

One file per brand, and a pod restart. No rebuild, no release, no second image to scan and ship. The portal reads its brand as it renders, so the tenth brand costs what the second did.

The renderer refuses a brand that would break: a colour that is not a colour, a plugin the build does not ship, a standard that does not exist. You find out at render time, not from a customer.

brands/acme/brand.yaml
product:
  name: Acme Cloud
  tagline: Your service, in production, before lunch.
domain:
  hosts: {portal: acme, argocd: acme-argocd, ...}
theme:
  headerShape: none
  light: {primary: '#b8232f', navigationBackground: '#241f1c'}
plugins:            # a real allowlist, not hidden nav
  - '@backstage/plugin-catalog'
  - '@backstage/plugin-scaffolder'
  - ...
standards:          # what "good" means here
  annotationPrefix: acme.example
  checks:
    techdocs: {weight: 4}
    gitops-managed: {weight: 5}
    criticality: {enabled: false}

Inside the product

Real screens, from a running instance.

The live demo is the portal itself, the same build these screenshots came from, over a catalogue that is not yours. Sign in as a guest and walk a golden path; it is wired to nothing, so it creates nothing.

Open the live demo

Scorecards: estate average, grade distribution, weakest standards and lowest-scoring owners.

The estate at a glance. Everything sorts worst-first, because the page is a work queue.

A service page showing ownership, APIs, and a platform standards card scoring A.

A service page: ownership, APIs, runtime, and its standards score with the remedy for anything failing.

The service catalogue, filtered by kind, owner and lifecycle.

Everything the platform knows about, filtered by kind, owner, lifecycle and tag.

The same scorecards page in the dark theme.

Both themes are designed, not inverted, and both come from the brand's own palette.

A service failing most of the platform standards, with the remedy listed for each.

A service nobody has looked after, and exactly what to do about it.

Who it is for

Four ways it earns its place.

Platform team

You have been building this for eighteen months

A scale-up with forty engineers, a half-finished Backstage, Argo CD somebody set up, and no consistent way to give a team a namespace.

  • Onboards a team as one object, with quota, RBAC and secrets included
  • Standards enforced at admission and scored in the portal
  • Your platform team stops maintaining glue and starts shipping golden paths

Consultancy · MSP

You want a platform to sell, not to build

You deliver Kubernetes work for several clients and rebuild the same scaffolding each time, unbilled.

  • Every client gets a portal in their colours, from one image you maintain
  • Per-client plugin sets and standards, so engagements differ without forks
  • Run it for every client under your own name

Regulated enterprise

You need to prove it, not just do it

Bank, insurer, health: every control needs evidence and every change needs a reviewer.

  • Git is the only path into the cluster, so every change has an author and a diff
  • Admission policies with tests that assert what each rule allows and refuses
  • No secrets in the repository, generated at bootstrap, held in OpenBao
  • Runs air-gapped; nothing phones home

Group IT

Five business units, five opinions

A group with autonomous divisions that will not accept a shared tool wearing another division's name.

  • One platform, one operations team, a distinct product per division
  • Each division sets its own standards and its own plugin set
  • Tenancy boundaries that hold: a division cannot deploy into another's namespace

How it lands

Running in a day. Yours by the end of the week.

The platform stands itself up on a laptop first, so your team can see all of it working before any decision about clusters is made.

  1. Try it locally

    One command builds a full cluster on a laptop: portal, delivery, control plane, identity, guardrails, observability. No cluster of your own needed to see all of it.

  2. Put your name on it

    Copy a brand file, set your colours, hostnames, plugin set and standards. Render, review the diff, and the portal is yours.

  3. Point it at real clusters

    The same manifests target your environments. Identity moves to your IdP; secrets move to your vault.

  4. Onboard teams

    One object per team. Quota, network policy, RBAC, delivery project and secret store, created and kept in step by the control plane.

Private beta

In private beta.

Paved is in private beta. Request access and you will hear when there is a seat.

What the beta includes

  • The full platform: portal, delivery, control plane, identity, guardrails, observability
  • Your brand applied: colours, logo, hostnames, plugin set, standards
  • A working session to stand it up against your clusters
  • A named contact, not a ticket queue

What we ask in return

  • Run it somewhere real, even if that is one non-production cluster
  • An honest half-hour every few weeks about what is missing
  • Permission to name you as a design partner, if you are comfortable

Questions we are asked

Before you get in touch.

Is this open source? Can I just download it?

No. There is no public repository and no download. During the private beta, access to the platform and the brand pipeline is given team by team, so each one gets a working session and a named contact.

What does joining the beta involve?

Paved is in private beta. There is nothing to sign up to beyond the form at the bottom of this page.

It is built on open-source projects. What does it add?

Backstage, Argo CD, Crossplane, Kyverno, Keycloak, OpenBao and Prometheus are all excellent. What Paved adds is the part nobody hands you: the white-label engine, the platform API that makes a tenant one object, the standards engine, the guardrails with their tests, the identity model that ties all three together, and the upgrade path that keeps that assembly working as each project moves.

What happens when the beta ends?

Nothing switches off by itself. There is no licence server, no phone-home and no kill switch, so the clusters keep running exactly as they are. Before anything about the beta changes, every team in it hears about it first, in writing.

Can it run air-gapped?

Yes. Every upstream version is pinned in one file, the images are mirrorable into your registry, and the platform makes no outbound calls of its own. The portal loads no third-party fonts, scripts or analytics.

Where does our data live?

Entirely in your clusters. We never receive your catalogue, your source, your users or your metrics.

How much of it can we change?

Beta teams get the source. Brands, plugin sets and standards are configuration; golden paths and compositions are yours to write. Changes you make to shared code are supported on a best-effort basis, and we will tell you honestly which ones will make upgrades harder.

Which Kubernetes will it run on?

Any conformant cluster from 1.28: EKS, GKE, AKS, OpenShift, Rancher, or bare metal. The default control plane provisions in-cluster resources only, so it needs no cloud credentials; cloud provisioning is an additional provider behind the same API your developers already use.

How does joining the beta work?

Tell us a little about your estate and we will write back, usually within a few days, when there is a seat. It stands itself up on a laptop, so trying it costs your team an afternoon rather than a project.

Join the private beta

Put it in front of your developers.

Built, running, and opened to a handful of teams at a time so each one gets a working session and a named contact.

Every answer below tells us something we cannot find out any other way.

In private beta, and we will tell you plainly if you are not a good fit for it.