Paved is a complete internal developer platform that carries your name,
your colours and your engineering standards. One product, any number of brands.
Service catalogue. Who owns what, what it depends on, and where it runs.
Golden paths. A new service created from a template rather than copied
from the last one.
Scorecards. How each service measures against your engineering standards.
Docs beside code. Technical documentation in the same portal as the
service it describes.
Single sign-on. One account for the portal and the delivery tool.
Safe self-service. Ship without filing tickets, inside the quotas and
policies the platform sets.
Delivery
Getting changes into production
GitOps. What is deployed is a file in your repository.
Reviewable changes. The final manifests are committed, so a change is
readable before it lands rather than generated at deploy time.
Ordered rollouts. Components come up in the order they depend on each
other.
Rollback is a revert.
One view. What is deployed where, and what has drifted.
Governance
Teams, boundaries and standards
Onboarding in one object. A team gets a namespace, a quota, network
isolation, permissions, its own delivery project and its own secret store.
Isolated by default. Teams cannot reach each other's workloads.
Quotas per team. One team cannot consume the cluster.
One set of groups. The same membership grants the namespace, the delivery
tool and the portal.
Standards at admission. Enforced when a workload arrives, not discovered
later in a review.
Tested policies. See exactly what each one allows, refuses and exempts
before you turn it on.
Security
Secrets and guardrails
Secret store per team. Delivered to workloads rather than pasted into them.
No committed credentials. Every one is generated when the platform is
installed.
One-command rotation. Every credential, at once.
Unsafe workloads refused. With the reason returned to the developer who
pushed them.
Explicit exemptions. Written down and tested, rather than a policy
somebody quietly turned off.
White label
Sell it as your own
Your identity. Name, colours, typography, logo and favicon throughout the portal.
Your hostnames. The portal, delivery tool, dashboards and sign-in page on
your own domain.
Your standards. The scorecards measure what your company cares about.
One image, every brand. Every brand runs the same portal image; nothing is
forked per customer.
Rebrand in a restart. A configuration change, not a build and a release.
Components per brand. Chosen with a short wizard from three starting
points: the platform alone, with observability, cost reporting and managed Postgres, or with
TLS for regulated environments.
Preview as a diff. See what a rebrand changes before you apply it.
Operations
Running it
Observability. Metrics, dashboards and logs as optional components, with a
platform view that picks up new teams by itself.
Any Kubernetes. Your cloud or your data centre.
Laptop first. It stands itself up locally, so trying it does not need a
cluster, or anyone's sign-off, first.
Pinned versions. Every upstream version in one place, so an upgrade is a
decision rather than a surprise.