Is Nool a Backstage alternative?

No. Backstage is a portal and catalogue; Nool is change control for agent-authored changes. If you need discoverability and ownership across teams, Backstage is the answer. If you need to govern what coding agents land in specific repositories, Nool is.

Can Nool feed data into Backstage?

Nool's ledger and architecture model are queryable and exportable from the CLI, and its attestations are Git refs, so a Backstage plugin could surface per-change evidence, blast radius and findings for a catalogued component. There is no official plugin today.

Backstage exposes MCP tools to agents. Does that overlap with Nool?

They compose. Portal's MCP tools give an agent organisational context: services, owners, docs. Nool's MCP server gives it repository context and the propose and announce calls that put its change through the gates.

Does Soundcheck do what Nool's gates do?

Soundcheck scores services against standards on a schedule. Nool's gates run on each proposed change before it lands and can refuse it. One is a scorecard; the other is enforcement at the point of change.

Nool vs Spotify Backstage | Developer Portal vs Change Control

Backstage tells an organisation what it has and who owns it. Nool tells it what agents changed, whether the change stayed in scope, and which gates it passed. A portal and a control plane, not two of the same thing.

Govern the repositories behind the catalogue

# On each repository the portal catalogues
nool init --from-git main
nool discover features
nool config init-governance

# Export the architecture model for a portal or a dashboard to read
nool export --help

# Coordinate many repositories as one workspace: topology, rollups, cross-project tasks
nool workspace --help

# Per-change evidence a scheduled check cannot produce
nool attest record --from-head --checker github-actions --assertion unit-tests --verdict pass --push origin
nool audit report

nool export and nool workspace list their subcommands with --help; the shapes they emit are what a portal integration would consume.

What Spotify Backstage is

Backstage is the open-source framework for building internal developer portals that Spotify created and donated to the CNCF, adopted by thousands of organisations. Its core is a software catalogue and software templates: every service, library, dataset and team as an entity with an owner, plus scaffolding for new components. Spotify Portal for Backstage is the ready-to-use version, pitched as a full-featured developer portal with no coding required, and it ships premium plugins: AiKA, the AI knowledge assistant that knows what your organisation knows; Soundcheck for quality and reliability checks; Insights for adoption analytics; Skill Exchange; Data Experience; Confidence for experimentation; and role-based access control. Portal now exposes plugin capabilities as MCP tools that agents such as Claude Code, Cursor and Copilot can discover and use.

What Nool is

Nool works at a different altitude. It is installed on a repository, not across an organisation's catalogue, and it governs the changes that land there: an agent announces intent and leases scope, its proposal is checked for semantic blast radius and against policy gates, reviewers attach signed verdicts, and the change seals into a ledger with its reasoning attached. nool workspace extends this across nested repositories, reconciling topology and rolling up release health, and nool export serialises the architecture model into views other systems can read. Nool has no catalogue UI and does not try to be a portal; it is the layer a portal would query to answer what agents did and whether it was allowed.

Where they differ

Inventory versus enforcement. Backstage answers who owns this service, what does it depend on, is it meeting our standards, and where do I go to learn about it. Soundcheck evaluates services against standards on a schedule; AiKA answers questions from organisational knowledge. Nool answers whether this specific change, proposed by this agent under this intent, may land, and what evidence says so. Backstage's MCP tools give agents information about the organisation; Nool's gates constrain what agents do with it. A catalogue does not stop an agent from reaching past its scope, and a change-control ledger does not tell a new engineer which team owns the payments service.

Using them together

The natural shape is Backstage above, Nool below. Agents discover services, owners and standards through Portal's MCP tools, then make changes to those services' repositories through Nool, where the envelope check, policy gates and reviewer quorum apply. Nool's ledger becomes a source Backstage could surface: which agents changed a component, how far each change reached, which gates it passed, and the findings recorded against it. Teams that already run Soundcheck can treat Nool's attestations, signed verdicts from tests, scans and reviews, as the per-change evidence that a scheduled check cannot produce. Neither product needs the other to work, and neither replaces the other's job.

When to choose which

Choose Backstage or Spotify Portal when the problem is discoverability and standards across many teams: nobody knows what exists, who owns it, or whether it meets the bar. That is a portal problem, and Backstage is the most widely adopted answer to it. Choose Nool when the problem is that AI coding agents are producing changes faster than review can govern them, and you need scope enforcement, semantic conflict detection, policy gates and an audit trail at the moment a change is proposed. Choose both when agents are working across a catalogued estate; the portal tells them where to go and Nool decides what they may do when they get there.

Spotify Backstage vs Nool, side by side

Criterion	Spotify Backstage	Nool
What it is	Open-source developer portal framework (CNCF); Spotify Portal is the ready-to-run version	Change control for AI coding agents, installed per repository
Primary unit	Catalogue entities: services, libraries, datasets, teams	Knots: signed changes with intent, blast radius and evidence
Standards	Soundcheck evaluates services against standards on a schedule	Deterministic gates evaluate each change at proposal time
AI features	AiKA knowledge assistant; plugins exposed as MCP tools to agents	Governs what agents land; MCP server exposes context, findings and proposals
Agent coordination	Not a goal of the product	Leases, isolated worktrees, semantic conflict detection, reviewer quorum
Multi-repository	Catalogue spans the organisation	nool workspace coordinates nested projects; packs apply governance across repositories
Who operates it	Platform teams running a portal	Engineers and agents, from the CLI, MCP server and CI

Frequently asked questions

Is Nool a Backstage alternative?: No. Backstage is a portal and catalogue; Nool is change control for agent-authored changes. If you need discoverability and ownership across teams, Backstage is the answer. If you need to govern what coding agents land in specific repositories, Nool is.
Can Nool feed data into Backstage?: Nool's ledger and architecture model are queryable and exportable from the CLI, and its attestations are Git refs, so a Backstage plugin could surface per-change evidence, blast radius and findings for a catalogued component. There is no official plugin today.
Backstage exposes MCP tools to agents. Does that overlap with Nool?: They compose. Portal's MCP tools give an agent organisational context: services, owners, docs. Nool's MCP server gives it repository context and the propose and announce calls that put its change through the gates.
Does Soundcheck do what Nool's gates do?: Soundcheck scores services against standards on a schedule. Nool's gates run on each proposed change before it lands and can refuse it. One is a scorecard; the other is enforcement at the point of change.