Presenters

Source

Unlocking Developer Superpowers: Spotify’s Portal and the Agentic Future 🚀

Hey tech enthusiasts! Ever felt like you’re drowning in operational overhead, juggling countless tools, and wishing for a smoother development experience? Well, get ready, because Joe Combopiano from Spotify is here to pull back the curtain on Spotify for Portal, a game-changer that’s not just simplifying development but propelling it into an agentic future.

What is Spotify for Portal? 🤔

At its core, Spotify for Portal is an evolution of the popular open-source Backstage environment. It offers all the incredible flexibility developers love but without the headache of managing it all yourself. Think of it as a fully managed, single-tenant platform, powered by Spotify’s extensive experience and cutting-edge platform engineering tools.

Why Trust Spotify? The Agentic Revolution! 🤖

Spotify isn’t just talking about the future; they’re living it. Joe shared a fascinating insight: they are all in on agentic development. This means engineers, and even non-engineers, are empowered to push code to production, sometimes even while on the go! This might sound like pure chaos, but Spotify proves it’s not.

Key takeaway: Internal developer portals and other platforming tools are the fundamental enablers that keep this seemingly wild west of agentic development grounded. Guardrails, in this context, aren’t limitations; they’re accelerators, guiding innovation safely and efficiently.

Honk & Fleetshift: The Power Duo for Scalable Changes 🦢➡️🚢

Joe introduced us to Honk, Spotify’s internal tool that allows users to interact with code changes via Slack. Imagine asking a bot to push code directly to your repositories – that’s Honk! This magic is possible because Backstage provides the crucial context for all their projects.

But the real fireworks happen when Honk integrates with Fleetshift. This is Spotify’s tool for making changes at scale. By using Fleetshift as the orchestration layer, Honk can tackle complex software migrations across thousands of repositories simultaneously. The synergy is clear: Honk alone is powerful, but Honk amplified by Spotify’s internal platforms (like Backstage) is exponentially more potent.

A Live Demo: Claude, Soundcheck, and Fleetshift in Action! 💡

Joe then walked us through a captivating live demonstration showcasing the power of these tools:

  1. Asking Claude for Project Insights: Joe interacted with Claude, an AI assistant, asking which of his projects needed attention. Claude leveraged Portal’s MCP (likely a Metadata Control Plane or similar) to identify Joe’s owned entities and then utilized Soundcheck.
  2. Soundcheck: The Tech Health Guardian: Soundcheck is Spotify’s internal tool for observing and monitoring all projects, providing crucial tech health insights across the organization. It identified a failing check for Joe: the AI recommendation engine wasn’t enabled in one of his music player projects.
  3. Agentic Fix with Claude: Joe could have simply asked Claude to fix this. With the project context and source code location readily available, Claude could clone, make the necessary changes, and automate the fix – true agentic development in action!
  4. Platform Engineering at Scale with Fleetshift: For platform engineers, the need is to do this across many projects. Joe showed how Soundcheck’s “campaigns” feature allows for short-term, focused projects. He demonstrated initiating a campaign to migrate to the AI recommendation engine.
  5. Fleetshift Orchestrates Thousands: By launching Fleetshift, this migration could be executed across all thousand repos at once. Fleetshift handles both agentic (AI-driven) and deterministic (rule-based) shifts. Joe could select the entities, create the “shift” (a change initiative), and watch as it progressed, creating isolated changes before opening PRs.

Migrating to the Future: Plugins and Private Registries 📦

The demonstration concluded with the migration engine completing its task, highlighting the plugins that would be installed. Crucially, it also flagged which plugins required Portal’s private registry. This is essential for managing and securing internal plugins within their single-tenant environment, ensuring a robust and secure platform.

Joe’s presentation offered a compelling vision of how Spotify is building the future of software development, making complex tasks manageable and empowering developers with intelligent, scalable tools. The integration of agentic capabilities with robust platform engineering is clearly the path forward, and Spotify for Portal is leading the charge! ✨

Appendix