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

A YAML field named allowed tools is a list in a document. Since v1.54 the catalog has an AiResource kind with fields for plugins, allowed tools, licenses and compatibility information ^[9], and every catalog entity is modeled in YAML ^[6]. Spotify's document does not say what reads that list when an agent calls a tool, or whether the Model Context Protocol surface exposes template execution as well as template contents. Those two answers decide whether the field is an authorization boundary or a comment.

Behind the same endpoint sit the Software Templates, the golden paths that create a new service with its repository, CI/CD and monitoring already wired ^[7]. Assistants reach the catalog, the templates and TechDocs through one protocol ^[8].

CNCF CTO Chris Aniszczyk said "IDPs and Backstage are becoming increasingly important in the age of agentic systems because agents rely on structured information" ^[13]. Spotify's in-house AI Knowledge Assistant, connected through an MCP service, cut developers' goalie workload by 47 percent ^[10], where goalie workload is the time developers spend answering requests that could be automated ^[11]. The catalog it queried has been accumulating since 2016, when Spotify built the portal for hundreds of microservices with no standard ^[5]. For that 47 percent to transfer, you would need ownership recorded for the services people actually interrupt each other about, and a measured baseline of those interrupts before the assistant existed. Spotify manager Tyson Singer put the condition plainly at KubeCon, saying AI agents amplify what is going well in an ecosystem and what is going poorly ^[12].

Toyota North America's Backstage-based platform Chofer saved ten million dollars over two years, five million a year of it in infrastructure costs alone ^[20]. Five million a year for two years is ten million ^[22], so the infrastructure line accounts for the whole published total. It is not clear whether the six weeks of development time per project that individual teams reported ^[21] is counted inside that number.

The category forecast runs from $5.76 billion in 2025 to $47.32 billion by 2035 ^[18]. That is 8.2 times in ten years, about 23 percent a year compounded ^[23].

The adoption cost is the upgrade cadence. Backstage ships monthly, always on the Tuesday before the third Wednesday of the month ^[17]. The New Backend System became stable in September 2024 and the legacy backend was removed that December ^[16], about three months later ^[24]. The plumbing in recent releases points the same way: the catalog syncs entity relationships by diff instead of deleting and rewriting them, and PostgreSQL deadlocks are retried automatically ^[14].