Softwr

Developer Tools · head to head

Keycloak vs Thredd

Keycloak logo

Keycloak

Developer Tools

Open-source identity and access management server.

From
Free
Free plan
Yes
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

  • Keycloak is an open-source IAM platform supporting OpenID Connect, OAuth 2.
  • Keycloak is free; Thredd prices on request.
  • Where Keycloak falls short: requires self-hosted deployment and operational expertise to install, configure and maintain.
  • 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 Keycloak and Thredd differ?

Keycloak and Thredd differ on starting price (Free against On request), pricing model (Open-source against Quote) and free tier (Yes against No). Only the attributes on which Keycloak and Thredd actually diverge.

Attributes where Keycloak and Thredd differ
AttributeKeycloakThredd
Starting priceFreeOn request
Pricing modelOpen-sourceQuote
Free tierYesNo
PlatformsSelf-hosted, Linux, Windows, APIWeb, API
CategoryDeveloper ToolsAPIs

Which features does each one have?

They share no listed features; 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 Keycloak

Nothing recorded that Thredd does not also cover.

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?

Keycloak is most often brought in for open-source projects and communities requiring free IAM without licensing costs. The jobs each tool is most often brought in to do.

Keycloak

  • Organisations requiring self-hosted identity infrastructure for compliance or data residencynot Thredd
  • Companies with existing LDAP/Active Directory systems needing federated authenticationnot Thredd
  • Open-source projects and communities requiring free IAM without licensing costsnot Thredd
  • Enterprises building custom identity workflows requiring fine-grained authorisationnot Thredd
  • Teams with sufficient operational expertise to manage infrastructurenot Thredd

Thredd

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

Where do Keycloak and Thredd fall short?

Keycloak's most cited limit: requires self-hosted deployment and operational expertise to install, configure and maintain. Thredd's: 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.

Keycloak

  • Requires self-hosted deployment and operational expertise to install, configure and maintain
  • No managed cloud option provided by Red Hat; organisations must operate infrastructure themselves or use third-party distributions
  • Clustering and high-availability configurations require additional operational knowledge
  • Community support only; commercial support requires third-party vendors or distributions

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 Keycloak and Thredd cost?

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

Keycloak

Free
  • Open-sourceFree
    • Full platform functionality
    • Self-hosted deployment
    • Community support

Thredd

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

Which should you pick?

Choose Keycloak if

  • You want to start without paying.
  • You work on Self-hosted, Linux, Windows, API.

Choose Thredd if

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

Questions people ask

Is Keycloak or Thredd better?
Neither clearly leads. Keycloak starts at Free and Thredd at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Keycloak or Thredd?
Keycloak has a free tier; the other does not. Paid plans start at Free for Keycloak and On request for Thredd.
Does Keycloak or Thredd run on more platforms?
Keycloak runs on Self-hosted, Linux, Windows, API. Thredd runs on Web, API.
Can I use Keycloak for free?
Yes. Keycloak has a free tier, so you can try it without paying. Thredd starts at On request.
What is Keycloak best used for?
Keycloak is most often used for organisations requiring self-hosted identity infrastructure for compliance or data residency, companies with existing ldap/active directory systems needing federated authentication, open-source projects and communities requiring free iam without licensing costs, enterprises building custom identity workflows requiring fine-grained authorisation. Of those, organisations requiring self-hosted identity infrastructure for compliance or data residency and companies with existing ldap/active directory systems needing federated authentication are not what Thredd is typically brought in for.
What can Keycloak do that Thredd cannot?
Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals.

Answered from the vendors’ own pages

Keycloak: What protocols does Keycloak support?

Keycloak supports OpenID Connect, OAuth 2.0 and SAML 2.0 protocols for authentication and authorisation.

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

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

Keycloak: Can Keycloak integrate with existing user directories?

Yes. Keycloak supports user federation with LDAP and Active Directory systems, allowing organisations to leverage existing user directories.

Source
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.

Keycloak: Is Keycloak free?

Yes. Keycloak is fully open-source and free to deploy and use. No licensing fees are required.

Source
Thredd: Is pricing published?

No, it requires a sales conversation.

Share

Related pages

Other head to heads