![\"\"\/](\"https:\/\/engineering.atspotify.com\/wp-content\/themes\/theme-spotify\/images\/icon.png\"){kind=icon}
<\/p>\n
<\/p>\n
<\/p>\n Did that we promote Spotify\u2019s developer productiveness instruments and help to different firms, from on-line retailers and vogue manufacturers to banks and vehicle producers? How did Spotify get into the enterprise of promoting enterprise developer software program? And how does serving the open supply group \u2014 to not point out paying company prospects \u2014 enhance our personal inner software program practices? Tyson Singer, Spotify\u2019s head of expertise and platforms, shares how our homegrown developer portal advanced from an open supply challenge to our latest enterprise software program product: <\/em>Spotify Portal for Backstage<\/em><\/a>.<\/em><\/em><\/p>\n Five years in the past on March 16, 2020, we open sourced Backstage, a framework for constructing inner developer portals<\/a> (IDPs) just like the one we have been utilizing at Spotify. Despite being a really new thought \u2014 the time period \u201cIDP\u201d didn\u2019t even exist again then \u2014\u00a0the challenge took off on day one, and accelerated from there.\u00a0<\/p>\n Today, Backstage is the IDP platform of selection<\/a> \u2014 with over 3,000 firms<\/a> having adopted it to construct IDPs of their very own. Within Spotify, it\u2019s nonetheless what our 700 R&D squads depend on to assist them ship daily. And, oh yeah, we\u2019re additionally constructing an enterprise software program enterprise<\/a> on prime of it. So how did Spotify get right here? And the place will Backstage take us subsequent?<\/p>\n Before open sourcing Backstage, we\u2019d already been utilizing it internally for years to assist us remedy an entire vary of developer expertise issues: context switching, fragmentation, cognitive load, silos, duplication, congestion, dependency administration, tech well being, compliance \u2014 you identify it, Backstage might develop to assist us handle it. As a centralized platform, it contained the chaos of recent software program improvement whereas making our entire engineering org extra productive and extra environment friendly<\/a>. It turned invaluable to how we work \u2014 and we didn\u2019t need to lose it.<\/p>\n How would we lose it? We\u2019d just lately gone via a painful migration earlier than with one other expertise, the place we needed to transfer from our custom-built resolution to a third-party one which had turn into the usual. We didn\u2019t need to undergo that once more with Backstage. So we open sourced it.\u00a0<\/p>\n Backstage had turn into so invaluable to us, we thought different firms would discover it invaluable, too. But we additionally had one other motive for open sourcing it. It wasn\u2019t nearly sharing: Our ambition from the very begin was for Backstage to turn into the usual for IDPs. Because if everybody else was utilizing it, we wouldn\u2019t need to migrate off it.\u00a0<\/p>\n But you\u2019re not going to turn into the usual simply by being free. The product additionally needs to be good. Even greater than that, for us, Backstage needed to be nice. Because we\u2019re an finish person, too \u2014 in all probability probably the most demanding one. We depend upon Backstage to enhance the developer expertise and productiveness of our personal groups, which has a direct influence on our enterprise. As an open supply challenge, we\u2019d additionally get the advantage of exterior contributions, addressing use circumstances we hadn\u2019t even considered but. Sounds nice, proper?\u00a0<\/p>\n But after all, watch out what you would like for. Now we have been not constructing only for ourselves, now we have been constructing for everybody. And typically it seems like these two issues is likely to be competing with one another. Could we meet the calls for of the skin group whereas nonetheless serving the wants of our personal builders?<\/p>\n Here\u2019s an instance of what it\u2019s been like being each maintainer and finish person of the Backstage challenge: We just lately launched a whole rewrite of the complete backend system<\/a>. This has been a extremely huge endeavor for us. But we noticed that adopters actually wanted a better method to construct and combine plugins. So we did the work \u2014 constructing with the group and rewriting the entire backend over the course of a 12 months.<\/p>\n And when the 1.0 of the brand new backend launched, it was nice. Here are just some of the issues we\u2019ve heard from the group and our enterprise prospects alike: \u201cMakes things a lot easier to maintain.\u201d \u201cYou used to have to wire things together across multiple files. Now adding a new plugin is a one-liner<\/a>.\u201d The new backend \u201cwas the game changer<\/a> \ud83d\ude80\ud83e\uddd1\u200d\ud83d\udcbb.\u201d\u00a0<\/p>\n Everything concerning the new backend is less complicated to work with \u2014 for the group and for us. So, after all, now we\u2019re in the course of fully rewriting the frontend, too. And guess what? That shall be nice for Spotify as finish customers, as nicely.<\/p>\n If we hadn\u2019t open sourced Backstage, I don\u2019t know the way lengthy we’d have stored dwelling with our earlier, extra difficult backend system. Because of the group \u2014 each its wants and the best way it permits us to construct higher options \u2014 we have been pushed to construct a significantly better model of Backstage for ourselves. And we might additionally rapidly convey these enhancements to our enterprise prospects \u2014 via a no-code UI for putting in and managing plugins \u2014 in Spotify Portal<\/a>, our SaaS resolution for Backstage adopters.<\/p>\n Spotify Portal is a SaaS resolution for Backstage that brings collectively one of the best of all the pieces we learn about constructing IDPs, each inside and out of doors Spotify. <\/em>Apply to get the Portal beta<\/em><\/a>.<\/em><\/p>\n It\u2019s been lots of push and pull in how we stability inner priorities with exterior ones. But in the end, this can be a virtuous cycle. The ever-popular Notifications characteristic<\/a>, the Events administration plugin<\/a>, and the API Docs plugin<\/a>, which mainly powers our entity pages for API entities \u2014 all of those are utilized in Spotify\u2019s inner Backstage occasion, and all have been contributions from the group.<\/p>\n Being a part of a developer group past Spotify has put us in such an awesome place for persevering with to spend money on and develop the Backstage platform. The challenge has improved our personal inner software program practices. We\u2019ve benefited from the innovation of the group at giant. And we\u2019ve been capable of preserve investing within the ecosystem in a approach that improves our industrial Backstage merchandise and brings extra worth to our enterprise prospects.<\/p>\n In 5 years, we\u2019ve gone from mainly only a skinny framework for constructing an IDP, to a greater IDP than we might have constructed by ourselves, and now to a SaaS product that we predict is one of the best IDP for the longer term. This journey will be bumpy. But making that repo public again in 2020 has positively introduced us to a spot we by no means might have imagined at this time<\/a>. All of which proves out our unique thought: Investing in the neighborhood has been an funding in ourselves, as nicely.\u00a0<\/p>\n
\n April 23, 2025<\/span>
\n
\n Published by Tyson Singer, Head of Technology and Platforms <\/span>
\n <\/p>\n<\/p><\/div>\n
\n ![\"\"](\"https:\/\/storage.googleapis.com\/production-eng\/1\/2025\/04\/backstage-5th-birthday-1.png\")
<\/a>
\n \n <\/div>\nA platform for developer expertise\u00a0<\/h2>\n
Becoming the trade customary<\/h2>\n
How constructing for others has benefited us<\/h2>\n
Internal \u2192 open supply \u2192 industrial: The better of all worlds<\/h2>\n
![\"\"](\"https:\/\/storage.googleapis.com\/production-eng\/1\/2025\/04\/spotify-backstage-venn-700x394.png\")
<\/figure>\n