Skip to content

Project

Backstage

Backstage is an open-source developer portal framework, originally built by Spotify, for creating software catalogs, documentation, and self-service tooling.

Known aliases

  • Spotify Backstage
  • Spotify for Backstage

Current stories

buildConfirmed2 publishers

Spotify gathers Backstage, Portal, Confidence and Xirp under a Spotify Technology brand

Spotify has put four tools it built for its own engineers, Backstage, Portal, Confidence and Xirp, under one brand called Spotify Technology. It calls the move doubling down, a public commitment that platform teams running these tools can now hold it to.

Publishers:engineering.atspotify.com mezha.net techcrunch.com

Perspective Coverage

3 publishers
Builder
Builder 39%
Operator
Operator 23%
Investor
Investor 38%

Reality

Evidence45
Adoption
Not scored
Hype gap+35
Incentives70
Confidence60
buildOne report1 publisher

Backstage v1.54 models AI agents as catalog entities with an allowed-tools list

Backstage's catalog is now something coding agents call at runtime, and the AiResource kind added in v1.54 records which tools a given agent may use. Platform teams still have to work out what checks that record.

Publishers:dev.to

Reality

Evidence34
Adoption45
Hype gap+42
Incentives72
Confidence40
buildOne report1 publisher

Swapping Backstage for an agent hands the platform team an index to keep current

At KubeCon Europe, Whitney Lee and Viktor Farcic argued the developer's front door is now an agent. What follows is continuous ingestion over Git and Slack, plus a per-tool policy on what the agent may run without asking.

Publishers:infoq.com

Reality

Evidence48
Adoption
Not scored
Hype gap+22
Incentives
Not scored
Confidence57
buildOne report1 publisher

A global pnpm setting in bol's container image sent the store outside the directory GitLab archived

bol has run its Backstage platform for more than five years and switched to pnpm so coding agents could work in parallel worktrees. Then came a store path two systems disagreed on and 1.42 GB of cached node_modules that saved nothing.

Publishers:dev.to

Reality

Evidence58
Adoption28
Hype gap−10
Incentives30
Confidence55
buildOne report1 publisher

Port writes its blast-radius prediction into a catalog field the next sync can overwrite

An essay from a one-person AI-native shop argues the catalog governs inventory and the gateway governs single tool calls, so nothing records which projects a pending change touches or who accepted it.

Publishers:dev.to

Reality

Evidence24
Adoption
Not scored
Hype gap+21
Incentives58
Confidence33
buildOne report1 publisher

Three tools, three spellings of the same glob: agent rules do not port

Claude Code scopes rules with paths, Cursor with globs, Copilot with a comma-delimited applyTo. Copilot reads Claude's rules directory, but not the file references inside it.

Publishers:dev.to

Reality

Evidence42
Adoption30
Hype gap+10
Incentives32
Confidence46