Softwr

Developer Tools · head to head

Cortex vs Thredd

Cortex logo

Cortex

Developer Tools

Internal developer portal that scores service ownership and maturity rather than just cataloguing services

From
On request
Free plan
No
Thredd logo

Thredd

APIs

Issuer processing platform for fintechs and digital banks, formerly Global Processing Services

From
On request
Free plan
No

The short version

  • Only Cortex lists service catalogue; only Thredd lists issuer processing.
  • Where Thredd falls short: pricing is entirely unpublished, so cost comparison against competing processors requires a sales process.
  • Prices and features on this page were last checked on 20 November 2026.

How do Cortex and Thredd differ?

Cortex and Thredd differ on category (Developer Tools against APIs). Only the attributes on which Cortex and Thredd actually diverge.

Attributes where Cortex and Thredd differ
AttributeCortexThredd
CategoryDeveloper ToolsAPIs

Identical on both: starting price (On request), pricing model (Quote), free tier (No), platforms (Web, API).

Which features does each one have?

They share no listed features; 8 appear only for Cortex and 6 only for Thredd. 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 Cortex

  • Service catalogue
  • Scorecards
  • Initiatives
  • Self-service templates
  • Query language
  • Eng intelligence
  • Integrations layer
  • On-call and ownership mapping

Only in Thredd

  • Issuer processing
  • Multi-country reach
  • Scheme certification
  • Programme support across verticals
  • High platform availability
  • Global office footprint

What is each one used for?

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

Cortex

  • A platform team that needs to prove to leadership how far a Kubernetes or framework migration has actually progressed across hundreds of servicesnot Thredd
  • An organisation where ownership of production services is genuinely unknown after reorganisations or acquisitionsnot Thredd
  • Enforcing production readiness standards on new services at creation time rather than at incident reviewnot Thredd
  • Replacing a self-hosted Backstage that is consuming a full-time engineer or two just to stay upgradednot Thredd

Thredd

  • A digital bank or fintech needing issuer processing across many countries under one contractnot Cortex
  • A BNPL, lending or crypto product needing certified card processing behind its own brandnot Cortex
  • A company that finds outdated Global Processing Services (GPS) material and needs to confirm it is now Threddnot Cortex
  • An embedded finance platform wanting a processor already integrated with core banking systems such as Mambunot Cortex

Where do Cortex and Thredd fall short?

Thredd's most cited limit: pricing is entirely unpublished, so cost comparison against competing processors requires a sales process. Documented limitations, not opinions. Every one is a constraint you would hit in normal use.

Cortex

  • Pricing is quote only, so a platform team cannot build a business case or compare against the true cost of self-hosted Backstage without entering a sales cycle first
  • The catalogue is only as accurate as the metadata you supply, so an organisation with inconsistent repository conventions spends its first quarter cleaning data before any scorecard means anything
  • Scorecards create political friction: publishing a per-team grade turns an engineering standard into a performance metric, and teams will game the rules rather than fix the underlying issue
  • It is closed source and hosted, so organisations with strict data residency or air-gap requirements have limited options compared with running Backstage themselves
  • Value scales with organisation size, so a company with fifty engineers and thirty services will find the catalogue tells them nothing they did not already know while still paying an enterprise contract

Thredd

  • Pricing is entirely unpublished, so cost comparison against competing processors requires a sales process
  • The 2023 rebrand from GPS to Thredd means research under either name alone can miss relevant material, and partner or press references before 2023 will still say GPS
  • Issuer processing does not include the banking licence itself, so a fintech still needs a separate BIN sponsor or bank partner, adding a second relationship to manage
  • As shared infrastructure behind many fintech brands, an outage or processing delay at Thredd becomes a simultaneous incident for every programme running on it, with limited visibility for any single customer into root cause
  • Its verticals span crypto, BNPL and remittance broadly, so depth of specialist support in any one vertical may be thinner than a processor focused narrowly on that niche

How much do Cortex and Thredd cost?

Cortex is priced on request; Thredd is priced on request. Plan by plan below, from each vendor's own pricing page.

Cortex

On request
  • CortexOn request
    • Service catalogue and ownership mapping
    • Scorecards and initiatives
    • Self-service templates

Thredd

On request
  • ThreddOn request
    • Volume and programme-based pricing, not published
    • Custom quote required via sales

Which should you pick?

Choose Cortex if

  • You need service catalogue.
  • You work on Web, API.
  • You also want scorecards.

Choose Thredd if

  • You need issuer processing.
  • You work on Web, API.
  • You also want multi-country reach.

Questions people ask

Is Cortex or Thredd better?
Neither clearly leads. Cortex starts at On request and Thredd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Cortex or Thredd?
Cortex starts at On request and Thredd at On request.
Does Cortex or Thredd run on more platforms?
Both run on Web, API, so platform support will not decide this one for you.
What is Cortex best used for?
Cortex is most often used for a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services, an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions, enforcing production readiness standards on new services at creation time rather than at incident review, replacing a self-hosted backstage that is consuming a full-time engineer or two just to stay upgraded. Of those, a platform team that needs to prove to leadership how far a kubernetes or framework migration has actually progressed across hundreds of services and an organisation where ownership of production services is genuinely unknown after reorganisations or acquisitions are not what Thredd is typically brought in for.
What can Cortex do that Thredd cannot?
Cortex covers Service catalogue, Scorecards, Initiatives, Self-service templates. Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals.

Answered from the vendors’ own pages

Cortex: How is Cortex different from Backstage?

Backstage is an open source framework you build and staff. Cortex is a hosted product with scorecards and initiatives out of the box and no platform team required to keep it running.

Thredd: Is Thredd the same company as Global Processing Services?

Yes, GPS rebranded as Thredd in 2023; it is the same company and platform.

Cortex: Is pricing published?

No. Cortex requires a sales conversation and prepares a custom proposal.

Thredd: Does it hold the banking licence for programmes it processes?

No, Thredd is the issuer processor; a separate bank or BIN sponsor holds the actual issuing licence.

Cortex: Can it self-host?

It is offered as a hosted product; on-premise arrangements are handled through sales rather than published.

Thredd: Is pricing published?

No, it requires a sales conversation.

Cortex: What is the main adoption risk?

Bad or missing service metadata. The catalogue and every scorecard on top of it inherit whatever quality your repositories already have.

Share

Related pages

Other head to heads