If you thought Backstage was just a nicer service catalog, v1.55.0 makes that argument obsolete. The release includes an AI chat plugin designed for multi‑agent interactions; paired with Scaffolder improvements, catalog deduplication, and the removal of legacy relations mode, developer portals can act as a control plane for autonomous and semi‑autonomous agents.
That's not a curiosity. The Backstage plugin ecosystem now includes a first‑class AI chat integration aimed at orchestrating agents for platform engineering tasks. Paired with opinionated Scaffolder templates and catalog hygiene, platforms can expose a single, supported route from idea to production that runs for both humans and machines.
Why this matters to platform teams
Platform teams have been building golden paths to reduce cognitive load and surface consistent policies. The new twist is who (or what) consumes those paths. If your portal can scaffold a new service, wire CI/CD, and configure observability for a human clicking buttons, you can also let an agent do the same — and faster. That enables automated remediation, incident runbooks invoked by agents, and cross‑service refactors started from a single chat prompt.
But it’s also a new trust boundary. Agents will need credentials, access to Scaffolder templates, permission to kick off pipelines, and visibility into service metadata. Most IAM models and audit pipelines were designed for human identities; they were not built for multi‑agent orchestration originating from your portal.
Security and policy are the engineering problem here
Treat this as the IAM problem nobody planned for: if you hand an agent the same permissions a dev has, you’ll get credential sprawl and unanswered audit questions. Conversely, if you lock agents down so tightly they can’t invoke Scaffolder or trigger pipelines, you’ve built a useless feature.
Practical starts: provision service accounts for agents, scope tokens to specific Scaffolder templates and the exact pipeline paths the agent needs, force ephemeral credentials, and ensure every agent action is auditable and visible in your catalog and observability tooling. Implement agent scorecards the way you track services on the golden path — adoption, time‑to‑first‑deployment, and Platform NPS all matter now.
Measurement that actually matters
Platform ROI is no longer a single dashboard. Teams are synthesizing DORA metrics (deployment frequency, lead time, change failure rate, MTTR) with platform‑specific signals: Platform NPS, time‑to‑first‑deployment, adoption rates, and friction logs. If agents are consumers of the platform, add agent‑initiated deployment frequency and agent‑error rates to that list.
Opinion: This is overdue and inevitable
Backstage going agent‑friendly is the right call. The alternative — letting teams build ad‑hoc agent integrations and credential injection — would have produced sprawl and zero auditability. That said, platform teams that treat Backstage as a UI only and don't rework IAM, audit, and golden‑path scorecards will be the ones who get bitten by a new attack surface.
What to do now
- Inventory where your Scaffolder templates, CI triggers, and service metadata are exposed in Backstage. Start by deciding which golden paths are agent‑safe.
- Add agent personas to your platform architecture: service accounts, scoped tokens, ephemeral creds, and targeted audit logs.
- Extend your platform scorecards: measure agent adoption, agent‑initiated deployments, and agent error/change failure rates alongside DORA metrics.
Backstage’s v1.55 signals the direction — portals as AI gateways, not just catalogs. Platform teams who accept agents as first‑class consumers will win consistency and velocity; those who treat agents like an afterthought will inherit complexity and risk. In twelve months, the question won’t be whether you used Backstage to scaffold services, but whether your portal was the place your agents learned to operate safely. Are you ready to build agent scorecards into your golden paths?
Related reading: see our earlier coverage of Backstage v1.55 for the catalog and relations changes: Backstage v1.55: legacy relations mode removed and catalog deduplication.
Sources
- Releases · backstage/backstage (v1.55.0, v1.54.8)
- Backstage GitHub repository (latest release metadata and activity)
- Backstage Plugins catalog (AI chat plugin for platform engineering tasks)
- Platform Engineering Latest — multi-persona platforms and AI gateway framing
- Platform Engineering Blog — metrics and practices for platform teams
- Platform Engineering Golden Paths: Internal Developer Portals
- Golden Paths: We Built 30+ for Platform Teams (Guide)
- DevOps & SRE | Google Cloud Blog
- Google Cloud release notes (App Topology API usage-based billing and operations updates)