What Spotify has learned from running Backstage-as-a-Service — and how those learnings shape the future of Spotify Portal.

Backstage adoption is accelerating across engineering organizations of every size. As internal developer portals (IDPs) become a core part of developer experience, expectations around reliability, consistency, and scale grow with them. Teams want the power and flexibility of Backstage — without the operational burden of running, securing, upgrading, and maintaining it themselves.

That’s where Spotify Portal, our SaaS offering for Backstage, comes in. Behind the infrastructure that powers Spotify Portal is the Chipmunks squad, Spotify’s team responsible for running Backstage-as-a-Service at scale.

Spotify Portal, which is now GA, turns Backstage into a fully managed, enterprise-ready platform — so your teams can focus on developer experience instead of operating infrastructure.

Meet the Chipmunks: The team behind Spotify Portal

At Spotify, the Chipmunks squad operates the infrastructure layer that hosts, secures, monitors, and scales every customer’s Spotify Portal instance. The Chipmunks are a dedicated platform engineering team focused exclusively on operating and evolving Spotify Portal as a reliable, multi-tenant SaaS offering.

Our mission is simple:

Deliver a reliable, scalable Backstage-as-a-Service platform while reducing operational overhead for engineering organizations.

We manage:

• Instance provisioning and lifecycle workflows
• Upgrades, configuration changes, and decommissions
• Observability and SLOs across all instances
• Reliability and workflow health checks
• On-call operations support
• Platform controls and security guardrails

Spotify Portal is not just software — it’s a fully managed platform operated with the same rigor we apply to Spotify’s internal systems.

We use Spotify Portal internally, too

Before any capability reaches customers, we use it ourselves.

Spotify runs an internal Spotify Portal instance that supports day-to-day operational work, including provisioning new customer environments, applying configuration changes at scale, and managing decommissions.

Our on-call engineers rely on this internal instance as well. It provides a unified operational view across the fleet, surfacing dashboards, logs, alerts, and other context needed during incidents. This consistency strengthens operational insight and enables fast, predictable responses.

We also use our custom Cost plugin in our internal Spotify Portal to make cloud spend observable and actionable. It helps us track cost trends over time, quickly spot anomalies or outliers, and clearly understand how infrastructure or configuration changes impact spend. This shortens the feedback loop between engineering decisions and real cost outcomes.

We use our internal Spotify Portal instance as one of several ways we inform and refine our SaaS product. It gives us practical insight into how the platform supports real operational workflows.

Internally, we use Backstage’s Scaffolder to automate provisioning workflows behind the scenes — one example of how Spotify Portal builds on Backstage’s extensibility.

Making Backstage provisioning effortless and consistent

Standing up Backstage inside an enterprise environment is rarely straightforward. Provisioning typically involves coordinating infrastructure, certificates, DNS, CI/CD, secrets, and compliance layers — all of which can vary widely across teams and cloud environments.

Spotify Portal removes that complexity entirely.

We combine a Terraform-based infrastructure foundation with a Scaffolder-powered automation layer to standardize the full provisioning lifecycle. When a team needs a new Portal instance, they simply initiate the process. From there, the platform’s automation layer takes over, handling the full workflow behind the scenes:

• Sets up all required infrastructure
• Applies Spotify’s recommended Backstage configurations
• Handles routing and certificate provisioning
• Defines upgrade and lifecycle workflows
• Ensures consistency across environments

The user action takes minutes; the full workflow is orchestrated automatically — without customers managing Terraform, DNS updates, CI pipelines, or long operational playbooks.

🧠 Why this scales:
Because instance creation is defined as code, each Spotify Portal instance follows the exact same provisioning path. Whether an organization spins up one instance or many, the operational effort remains consistent and predictable.

Continuous validation of Backstage workflows

An internal developer portal must be more than “up” — it must reliably support the workflows teams depend on. Spotify Portal continuously validates key Backstage flows such as login, catalog access, and configuration updates.

These automated checks run regularly across every customer instance and act as early signals for regressions or configuration issues. This helps ensure smooth operation even as teams customize Backstage with plugins, extensions, and integrations.

🧠 Why this scales:
Checks are defined once and applied across the fleet — ensuring consistent reliability without manual effort.

Enterprise-ready observability

Running an IDP in production requires clear visibility into performance and reliability. Spotify Portal provides enterprise-grade observability out of the box.

Every instance emits standardized, real-time metrics that power dashboards tracking:

• Availability
• Latency
• Health of key Backstage workflows
• Plugin behavior
• Configuration issues

These metrics are continuously aggregated across the fleet and form the basis for how we measure and uphold reliability targets. This observability foundation enables us to monitor service health 24/7 and confidently support Spotify Portal’s 99.5% SLA.

Alerts integrate directly with customer support channels, giving teams actionable insight without building or maintaining a monitoring stack.

🧠 Why this scales:
Every instance inherits the same telemetry pipeline and SLO instrumentation — no custom setup, no drift, no missing signals.

Focus on developer experience, not infrastructure

Running Backstage successfully requires real platform and SRE investment — from provisioning and upgrades to security, monitoring, and workflow reliability. Spotify Portal handles all of that for you.

For teams weighing whether to run Backstage themselves or adopt a managed solution, Spotify Portal removes the operational burden without compromising on control or extensibility.

Everything we’ve built into Spotify Portal comes from operating Backstage internally at Spotify scale: automated lifecycle workflows, built-in observability, reliability checks, and a consistent, hardened infrastructure foundation.

For organizations evaluating Backstage, this means:

• A fully managed IDP without maintaining infrastructure
• A reliable, consistent Backstage experience out of the box
• Safe, automated upgrades and configuration changes
• Enterprise-grade monitoring and security controls
• A platform that improves continuously as we evolve it

Spotify Portal is designed to remove the operational challenges teams often associate with running Backstage — without giving up the flexibility and extensibility that made Backstage successful in the first place.

In short: Spotify Portal takes care of running Backstage, so your teams can focus on building great developer experiences — not managing infrastructure.

Ready to leverage Spotify’s deep experience running Backstage at scale?

Talk with our Spotify Portal experts for a personalized consultation →