Spotify’s Commercial Plugins for Backstage Put Its DX Principles on the Shelf

Spotify has launched Spotify Plugins for Backstage, a commercial bundle of five plugins available via subscription. Some of these plugins started life as internal tools used by Spotify’s own engineers; others are new to the Backstage ecosystem. What ties them together is that they were all built according to the same principles Spotify uses for its internal software development — principles the company believes will translate to any engineering organization dealing with scale.

The plugins run on Backstage, the open source developer portal platform Spotify donated to the Cloud Native Computing Foundation. Backstage’s plugin architecture is what allows teams to add functionality — from security alerts to CI/CD integration — and it’s also what makes the platform a two-sided marketplace: anyone can build a plugin, and teams can contribute fixes or improvements back via pull requests.

From internal tools to commercial software

Spotify runs over 200 internal Backstage plugins today. The selection process was straightforward: teams built plugins when they hit a problem, and the most useful ones improved through a cycle of user feedback and iteration. The more a plugin was used, the more feedback it received, and the better it got. The commercial bundle represents a mix of Spotify’s most-used internal plugins and new ones built specifically for external Backstage adopters.

Four principles behind the plugins

Spotify summarizes its software philosophy as “Think it, build it, ship it, tweak it.” Maintaining that approach at scale requires more than good intentions. The company points to four organizational principles that guide its engineering culture:

  • Keep squads small, capable, and aligned. Spotify’s 450+ squads are cross-functional units that balance autonomy with collaboration, with an emphasis on individual growth and mobility.
  • Make engineering excellence an everyday practice. Strong fundamentals enable speed, and focusing on fewer technologies means the organization can be world-class at them.
  • Empower bottom-up solutions. Teams choose their own tools, and the organization avoids top-down mandates in favor of incentives that reduce fragmentation.
  • Treat developers as customers. Internal tools should deliver the same quality of experience as Spotify’s consumer products — and the company listens and adapts when they don’t.

These principles aren’t exclusive to Spotify, the company argues. Whatever the industry — car manufacturing, banking, telecoms — software teams face common problems: complexity, context switching, cognitive load, fragmentation, silos, and toil. The plugins are designed to address those shared challenges rather than industry-specific ones.

The five plugins at a glance

Each plugin in the bundle addresses a different pain point, but they all reflect the same Spotify approach to developer experience.

Soundcheck runs checks on software components and displays how well they align with an organization’s engineering standards. The idea is that visual context drives action: showing a team it scores 2 out of 5 on standards is more effective than chasing them down with reminders. The plugin codifies best practices around quality, reliability, security, and consistency.

Role-Based Access Control (RBAC) simplifies managing who has access to what within a Backstage instance. Spotify’s approach is to make the right thing the easy thing: if access control is transparent and painless, teams are more likely to keep up with security and compliance requirements rather than fall behind.

Skill Exchange is an internal marketplace for learning and collaboration. It connects mentors with mentees, lets teams find temporary help for specific projects, pairs up programming partners, and helps assemble ad hoc teams for hack projects. The goal is to make it easy for developers to discover and borrow each other’s skills, regardless of where they sit in the org chart.

Pulse is an R&D survey framework that tracks productivity and satisfaction metrics and provides analysis of anonymized response data. Known internally at Spotify as the EngSat Survey, it’s designed to measure how developers feel about tooling, processes, and culture — on the theory that you can’t improve productivity without knowing what’s blocking your teams.

Insights tracks Backstage usage across an organization, capturing data points like daily active users and the most commonly used plugins. This helps organizations understand actual behavior within their developer portal, informing decisions about which features to invest in and which to deprecate.

Built for the engineer’s everyday reality

The plugins are a commercial product aimed at medium to large engineering organizations, but they’re not built around industry-specific verticals. They’re built around the realities of day-to-day engineering work — the waiting on builds, the context switching, the gaps between tools. Spotify’s position is that improving developer experience means addressing those universal frictions, and that measuring both productivity and happiness is part of the equation. The company’s internal experience, it says, is that both improve when teams have the right tools — and that the plugins now available are a way for other organizations to make the same bet.