Softwr

Developer Tools · head to head

Backstage vs Formance

Backstage logo

Backstage

Developer Tools

Open source internal developer portal framework created and open sourced by Spotify

From
Free
Rated
-
Full reviewWebsite
Formance logo

Formance

APIs

Open source double-entry ledger and payment orchestration for money-moving software

From
Free
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Backstage backstage is a framework rather than a product: there is no supported turnkey install, so getting to a usable portal means a TypeScript and React project your team owns, hosts and upgrades forever.; Formance formance holds no money and provides no regulatory cover, so it must be paired with a payments provider or bank, and buyers occasionally mistake a ledger for a treasury system and discover the gap late.
  • They diverge on capability: Backstage covers Software catalogue, Formance covers Double-entry ledger.
  • Prices and features above were last checked on 31 August 2026.

Where they differ

Only the attributes on which Backstage and Formance actually diverge.

Attributes where Backstage and Formance differ
AttributeBackstageFormance
PlatformsWeb, Self-hosted, Linux, Docker, KubernetesLinux, Docker, Kubernetes, Web, API
CategoryDeveloper ToolsAPIs

Identical on both: starting price (Free), pricing model (Open source, no licence fee), free tier (Yes), user rating (Not yet rated).

What each one covers

Drawn from each product's published feature list. An absence here means we hold no record of it - not that the product lacks it.

Only in Backstage

  • Software catalogue
  • Software templates
  • TechDocs
  • Plugin architecture
  • Kubernetes plugin
  • Search
  • Entity ownership model
  • Auth provider integrations

Only in Formance

  • Double-entry ledger
  • Numscript transaction DSL
  • Multi-currency
  • Payments connectivity
  • Reconciliation
  • Self-hosted deployment
  • Cloud offering
  • API and SDKs

What people use each for

The jobs each tool is most often brought in to do.

Backstage

  • An engineering organisation past roughly a hundred services where nobody can reliably answer who owns a given service at two in the morningnot Formance
  • A platform team enforcing golden paths, so a new service is scaffolded with logging, CI and security defaults already wired innot Formance
  • A company consolidating scattered READMEs and Confluence pages into docs that live beside the code and cannot silently rot unnoticednot Formance
  • A regulated business that needs an auditable register of every running service, its owner and its data classificationnot Formance

Formance

  • A marketplace splitting a single customer payment between seller, platform fee and tax that needs the split to be atomic and auditablenot Backstage
  • A fintech whose homegrown balances table produced numbers finance could not reconcile and now needs proper double-entry before an auditnot Backstage
  • A payments team that wants one normalised model across several PSPs so reconciliation is not written separately for eachnot Backstage
  • A company that wants its ledger under a licence it can keep running even if the vendor disappearsnot Backstage

Where each one falls short

Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Backstage

  • Backstage is a framework rather than a product: there is no supported turnkey install, so getting to a usable portal means a TypeScript and React project your team owns, hosts and upgrades forever.
  • Upstream releases move quickly and plugin APIs have broken across major versions, so a customised deployment accumulates upgrade debt and teams routinely fall months behind on versions they cannot cheaply catch up on.
  • The catalogue is only as good as the YAML descriptors engineers remember to write; without enforcement the register drifts out of date, and a developer portal nobody trusts is abandoned faster than one that never existed.
  • Community plugin quality varies sharply, with many unmaintained or pinned to old core versions, so the plugin that made the business case may be the one blocking your next upgrade.
  • Spotify Portal, the packaged commercial route, publishes no price at all and is quoted as a custom annual subscription, so the only cost you can actually forecast up front is the self-hosted one, which is the option with the largest hidden staffing bill.

Formance

  • Formance holds no money and provides no regulatory cover, so it must be paired with a payments provider or bank, and buyers occasionally mistake a ledger for a treasury system and discover the gap late.
  • Numscript is a domain-specific language your team must learn, and while it makes complex splits expressible it also means transaction logic sits outside the languages your engineers already debug well.
  • Self-hosting a ledger that must never lose or duplicate a transaction is a serious operational commitment covering backups, upgrades and Postgres tuning, which is real cost the zero licence fee hides.
  • Enterprise pricing is not published, so the difference between the free path and the supported path cannot be evaluated without a sales conversation.
  • The company is much smaller than the incumbent alternatives, and while the MIT licence protects the code it does not protect the roadmap, so features on the hosted side may arrive slowly or change direction.

Pricing, plan by plan

Backstage

Free
  • Backstage (open source)Free
    • Apache 2.0 licence
    • Software catalogue, templates, TechDocs and search
    • Full plugin ecosystem
  • Spotify Portal for Backstage$undefined/year
    • Packaged commercial distribution from Spotify
    • Spotify premium plugins including Soundcheck and Insights
    • Simplified setup and managed upgrade path

Formance

Free
  • Open SourceFree
    • MIT licensed core ledger
    • Numscript transaction DSL
    • Multi-currency tracking
  • Enterprise$undefined/year
    • Managed or private deployment
    • Payments connectivity and reconciliation
    • Support with response commitments

Which should you pick?

Choose Backstage if

  • You need software catalogue.
  • You want to start without paying.
  • You work on Web, Self-hosted, Linux, Docker, Kubernetes.
  • You also want software templates.
Backstage review

Choose Formance if

  • You need double-entry ledger.
  • You want to start without paying.
  • You work on Linux, Docker, Kubernetes, Web, API.
  • You also want numscript transaction dsl.
Formance review

Questions people ask

Is Backstage or Formance better?
Neither clearly leads. Backstage starts at Free and Formance at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Backstage or Formance?
Backstage starts at Free and Formance at Free.
Does Backstage or Formance run on more platforms?
Backstage runs on Web, Self-hosted, Linux, Docker, Kubernetes. Formance runs on Linux, Docker, Kubernetes, Web, API.
Can I use Backstage for free?
Both have a free tier, so you can try either at no cost before committing.
What is Backstage best used for?
Backstage is most often used for an engineering organisation past roughly a hundred services where nobody can reliably answer who owns a given service at two in the morning, a platform team enforcing golden paths, so a new service is scaffolded with logging, ci and security defaults already wired in, a company consolidating scattered readmes and confluence pages into docs that live beside the code and cannot silently rot unnoticed, a regulated business that needs an auditable register of every running service, its owner and its data classification. Of those, an engineering organisation past roughly a hundred services where nobody can reliably answer who owns a given service at two in the morning and a platform team enforcing golden paths, so a new service is scaffolded with logging, ci and security defaults already wired in are not what Formance is typically brought in for.
What can Backstage do that Formance cannot?
Backstage covers Software catalogue, Software templates, TechDocs, Plugin architecture. Formance covers Double-entry ledger, Numscript transaction DSL, Multi-currency, Payments connectivity.

Answered from the vendors’ own pages

Backstage: Is Backstage free?

The project is Apache 2.0 with no licence fee. The real cost is engineering time; teams commonly dedicate one to two engineers permanently to running it.

Formance: Is Formance really open source?

Yes. The core ledger is MIT licensed with full source access and no deployment restrictions.

Backstage: Do I need to write code to use it?

Yes. Configuring and extending a Backstage application is a TypeScript and React project. This is the single most common misjudgement buyers make.

Formance: Does Formance move money?

No. It records and orchestrates movements; the actual payments happen at a PSP or bank you connect.

Backstage: What is Spotify Portal for Backstage?

A commercial distribution from Spotify with premium plugins and support, generally available since October 2025 and sold as a quoted annual subscription with no published price.

Formance: What does the enterprise version cost?

Not published. It is an annual subscription quoted per customer.

Backstage: Who owns the project?

Spotify created and open sourced it; it is now a CNCF project, so the upstream roadmap is not solely Spotify controlled.

Formance: Do I have to use Numscript?

Yes for anything beyond the simplest transfers. It is how multi-party transactions are expressed atomically.

Share

Related pages

More on Backstage

More on Formance

Keep looking

Other head to heads