Understanding Paved Road
The term paved road originated at Netflix to describe an approach to internal tooling: rather than mandating a single approved way of doing things, the platform team builds a road that is simply the easiest and best-supported option, so teams choose it voluntarily. It is closely related to, and often used alongside, the term golden path, but the emphasis is different. A golden path is often a specific, concrete instantiation — a particular software template or scaffolded workflow. A paved road is the broader philosophy: incentivize the standard route through quality and support rather than mandate, while still allowing teams to go off-road when they have a genuine reason to.
What Makes a Paved Road Different From a Mandate
A mandated standard is enforced through policy; a paved road is chosen because it is genuinely the path of least resistance. That distinction changes how a platform team invests. A paved road needs to be actively maintained, documented, secure by default, and backed by a real support commitment — because if it falls behind what a team could build themselves, teams will quietly abandon it, and no policy will bring them back without eroding trust.
A Concrete Example
A platform team builds a paved road for “new microservice” as a scaffolding template: it includes a working Dockerfile, a CI/CD pipeline already wired to the org’s standard deployment process, structured logging and tracing libraries pre-integrated, and Kubernetes manifests that already meet the security baseline (non-root containers, resource limits, network policies). A team that uses the template gets a deployable, observable, compliant service in under an hour. A team that opts to hand-roll their own setup instead can still do so, but they take on responsibility for keeping it secure and up to date themselves, and they typically fall outside the platform team’s standard support SLA.
Why Organizations Invest in Paved Roads
Paved roads are how a platform team scales support across dozens or hundreds of teams without needing a linear increase in headcount. If every team’s deployment pipeline, logging setup, and infrastructure pattern is different, the platform team cannot realistically support all of them, and the organization’s cognitive load stays high because knowledge doesn’t transfer between teams. A well-adopted paved road turns platform support into something that scales: fix a bug once in the shared template, and every team using it benefits immediately.
Trade-offs and Limitations
A paved road only works if it stays genuinely easier than the alternative. If it doesn’t cover common edge cases, or becomes outdated relative to what the underlying platform now supports, teams route around it — and every team that goes off-road represents lost leverage for the platform investment. Paved roads can also create a false sense of security if teams assume “on the paved road” automatically means “compliant” or “correct,” when in practice the road still needs periodic re-certification as security requirements evolve.
Best Practices
- Track adoption rate as a first-class platform metric — it is the clearest signal of whether the paved road is actually winning on merit.
- Treat every team that opts out as a source of feedback, not a compliance failure to punish; their reasons usually point to a real gap in the road.
- Keep paved roads thin and composable rather than a single monolithic template, so teams can adopt the parts relevant to them.
- Avoid making the paved road mandatory by policy alone — invest in making it obviously the best choice instead, and reserve mandates for genuine non-negotiables like security baselines.
Frequently Asked Questions
What is Paved Road?
A paved road is an opinionated, well-supported route for accomplishing a common engineering task, made deliberately easier and better maintained than any custom alternative, while still leaving teams free to build their own path if they accept the trade-offs.
How does Paved Road work?
Paved Road works by combining the components described in the sections above. The main page walks through the architecture, the typical use cases, and the trade-offs to weigh before adopting it.
Why does Paved Road matter?
Teams adopt Paved Road to ship faster, run more reliably, and reduce the cognitive load on engineers. The benefits, limits, and adjacent tools are covered in the body above.
When should you use Paved Road?
Use Paved Road when the problems it solves match what your team is hitting today. The page above outlines the signals that mean you should adopt it now, and the cases where a simpler approach is fine.
