Prompt
Backstage vs building an internal developer portal from scratch
Latest observation
Oct 29, 2026
OpenAI APIWeb search: off
If you’re deciding between Backstage and building an internal developer portal (IDP) from scratch, the short version is:
- Choose Backstage if you want to move fast, leverage a proven open-source platform, and focus on customizing rather than inventing the foundation.
- Build from scratch only if you have highly specialized requirements, strong platform engineering capacity, or constraints that Backstage can’t reasonably fit.
Backstage: what you get
Backstage is an open-source developer portal framework originally created by Spotify and now widely adopted.
Pros
- Faster time to value: You get a service catalog, docs, templates, ownership metadata, and plugin ecosystem out of the box.
- Standardized platform: Helps centralize service discovery, golden paths, and developer workflows.
- Extensible: You can add plugins for CI/CD, observability, incident management, cloud, scorecards, etc.
- Community and ecosystem: Lots of integrations and shared patterns already exist.
- Avoids reinventing common portal features: auth, catalog, docs, scaffolding, search, etc.
Cons
- Requires customization and maintenance: It’s a framework, not a finished product.
- Operational overhead: You still need to run, upgrade, secure, and integrate it.
- UX may not be perfect out of the box: You may need work to make it feel tailored to your org.
- Plugin fragmentation: Some integrations are mature; others may need internal engineering.
Building from scratch: what you get
Building your own portal means designing the exact experience, data model, and workflows your org wants.
Pros
- Maximum flexibility: You can model your org, services, and workflows exactly as needed.
- Custom UX/workflows: Great if portal needs are tightly tied to proprietary processes.
- Full control: Architecture, data ownership, deployment model, and roadmap are yours.
- Potentially simpler in one narrow use case: If you only need a few highly specific portal functions.
Cons
- Slow and expensive: You’ll spend a lot of time on basics before delivering value.
- Ongoing burden: Auth, search, cataloging, docs, templates, RBAC, auditability, and integrations all become your problem.
- Hidden scope creep: Internal portals often expand quickly once teams rely on them.
- Hard to match ecosystem breadth: You’ll likely need to build many commodity capabilities yourself.
A practical decision framework
Backstage is usually the better choice if:
- You need an IDP in weeks/months, not quarters/years
- You want service catalog + docs + templates + integrations
- Your org has many services and teams
- You want a platform engineering foundation
- You can tolerate configuring and extending rather than fully custom-building
Build from scratch if:
- Your portal is a core competitive differentiator
- You need a very specialized workflow Backstage doesn’t support well
- You have strong reasons to avoid the platform assumptions Backstage imposes
- You already have the engineering bandwidth to maintain a long-lived internal product
Common middle ground
A lot of companies do this:
- Adopt Backstage as the base
- Customize the UI and data model only where needed
- Build internal plugins or integrations for proprietary workflows
- Avoid replacing Backstage unless absolutely necessary
That approach gives you most of the speed benefits while still allowing differentiation.
Rule of thumb
If your goal is “deliver a usable IDP quickly and iterate”, use Backstage.
If your goal is “design a deeply bespoke internal platform and we’re willing to invest heavily”, consider building from scratch.
If you want, I can also provide:
- a feature-by-feature comparison table
- a TCO/ROI comparison
- a recommendation based on your org size and stack