Migrate to Spotify Portal without pausing your roadmap
You adopted Backstage to accelerate developers, not to become a full-time infrastructure maintainer.
Placeholder title
Spotify Portal is the SaaS, Spotify-managed edition of Backstage, built and operated by the same engineers who created and open sourced Backstage. We handle the migration and the unglamorous operational work, so your platform team can stay focused on building new developer experiences and adopting the capabilities Spotify uses internally.
.avif)
Backstage without the maintenance
Running Backstage at scale is real work: upgrades break, plugins drift, infra ages, and security patches never stop. Spotify Portal takes that off your plate.
While we keep the platform running, your team stays focused on higher-leverage work, not keeping the lights on.
While we keep the platform running, your team stays focused on higher-leverage work, not keeping the lights on.
🚀 Upgrades on autopilot
Always aligned with upstream open source Backstage
🛠️ No infrastructure to run or scale
We handle reliability, security, and availability
👷 Fewer breaking changes
We absorb ecosystem churn so you don’t have to
Your platform, professionally operated
Spotify Portal is run in a dedicated, single-tenant environment, so your plugins and integrations continue to work the way you expect.
We don’t ask you to rewrite your platform or give up flexibility. Our engineers work with you to move what you already have into a supported, production-grade environment.
Custom plugins stay first-class
Your plugins remain real, versioned code that you own, not extensions trapped behind a UI.
Portal Studio as your foundation
We migrate your existing custom plugins into your private Portal Studio mono-repo, giving you a clean, supported home going forward.
Same flexibility, fewer pitfalls
You keep control over how your platform evolves, without carrying infra, upgrade, or compatibility risk.
You still have a platform team. You just don’t have to run the platform.
We don’t ask you to rewrite your platform or give up flexibility. Our engineers work with you to move what you already have into a supported, production-grade environment.
Custom plugins stay first-class
Your plugins remain real, versioned code that you own, not extensions trapped behind a UI.
Portal Studio as your foundation
We migrate your existing custom plugins into your private Portal Studio mono-repo, giving you a clean, supported home going forward.
Same flexibility, fewer pitfalls
You keep control over how your platform evolves, without carrying infra, upgrade, or compatibility risk.
You still have a platform team. You just don’t have to run the platform.
.avif)
What the migration actually looks like
Our engineers do the heavy lifting across each step. Your team stays productive and can start focusing on what’s next, not the migration itself.
1. Identity & access (foundation)
We set up SSO, teams, and users so Portal reflects your org from day one.
- IDP integration
- Team and ownership mapping
- Access validated early to avoid surprises
2. Catalog import & alignment
We migrate your Backstage catalog and connect it to your identity model.
- Services, APIs, components, data, and metadata preserved
- Ownership and relationships maintained
- Familiar experience the first time engineers log in
3. Open-source plugin configuration
We port and validate the open-source plugins you already rely on.
- Plugin configs migrated from your OSS Backstage
- Integrations tested (CI/CD, SCM, cloud, observability, etc.)
- Gaps flagged early with clear remediation paths
4. Secure connectivity (Private Connect)
Need access to tools behind your firewall? We set up Portal Private Connect.
- Deploy a secure, scoped agent
- Whitelist only the network access you explicitly approve
- Validate connectivity end-to-end
Portal gets the access it needs, your network stays protected.
5. Custom plugin migration
We migrate your custom plugins into Portal Studio.
- Plugins extracted from your existing Backstage repo
- Moved into your private Studio mono-repo
- Built, deployed, and validated in Portal
Your plugins remain real, versioned code, running on a platform we operate for you.
Most teams use this phase to start adopting new Portal capabilities, rather than spending cycles maintaining migration code.
Clear ownership, no lock-in
Spotify Portal stays aligned with open source Backstage, so you always retain an exit path
You own
- Plugins and source code
- Catalog and data
- Integrations and identity model
- Catalog and data
- Integrations and identity model
We own
- Infrastructure and scaling
- Upgrades and compatibility
- Security, reliability, and availability
- Upgrades and compatibility
- Security, reliability, and availability
Ready to hand over the grunt work?
Get a free migration assessment with our engineering team.
We migrate your platform. You build what’s next.
We migrate your platform. You build what’s next.
What your team can focus on instead: “The Spotify Way”
While we handle migration and operations, your team can start adopting the same tools we use internally at Spotify without waiting for the move to finish.
Adopt what you want. Ignore what you don’t.
Adopt what you want. Ignore what you don’t.
AIKA: AI tool and MCP server already connected to the rich data in your Portal instance.
Soundcheck: Scorecards to enforce best practices and track tech health
Confidence Feature Flags: Cost-effective flagging built on OpenFeature
Insights: Executive-level DevEx metrics, DORA, usage, and surveys
Skill Exchange: Discover expertise and organize hackathons