Softwr

Developer Tools · head to head

Cloud Native Buildpacks vs Thredd

Cloud Native Buildpacks logo

Cloud Native Buildpacks

Developer Tools

Specification and tooling that turns source code into OCI images without Dockerfiles

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

  • Cloud Native Buildpacks is a specification plus a lifecycle and the pack CLI.
  • Cloud Native Buildpacks is free; Thredd prices on request.
  • Only Cloud Native Buildpacks lists detect and build lifecycle; 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 Cloud Native Buildpacks and Thredd differ?

Cloud Native Buildpacks and Thredd differ on starting price (Free against On request), pricing model and free tier (Yes against No). Only the attributes on which Cloud Native Buildpacks and Thredd actually diverge.

Attributes where Cloud Native Buildpacks and Thredd differ
AttributeCloud Native BuildpacksThredd
Starting priceFreeOn request
Pricing modelOpen source, no licence feeQuote
Free tierYesNo
PlatformsLinux, macOS, Windows, API, Self-hostedWeb, API
CategoryDeveloper ToolsAPIs

Which features does each one have?

They share no listed features; 6 appear only for Cloud Native Buildpacks 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 Cloud Native Buildpacks

  • Detect and build lifecycle
  • Image rebasing
  • Reproducible layers
  • Builder images
  • Automatic SBOM output
  • pack CLI

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.

Cloud Native Buildpacks

  • Patching a base image once and rebasing hundreds of application images rather than rebuilding and redeploying eachnot Thredd
  • Removing per-team Dockerfiles at an organisation where inconsistent base images have become an audit findingnot Thredd
  • Giving application teams a supported path to a hardened image without teaching every team container securitynot Thredd
  • Choosing a build system that a risk committee will accept because governance is vendor neutral rather than single vendornot Thredd

Thredd

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

Where do Cloud Native Buildpacks 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.

Cloud Native Buildpacks

  • The operational cost is real: you own builder images, base image refresh cadence and migrations between specification versions, which currently sit at Buildpack API 0.10 and Platform API 0.12 with published migration guides, so breaking changes are a recurring chore
  • A cold build with no warm cache is noticeably slower than a well layered Dockerfile, and because the cache lives in a cache image or volume, ephemeral continuous integration runners pay full price on every run unless you deliberately warm them
  • Reproducibility depends on discipline rather than defaults, because buildpacks resolve runtime patch versions at build time unless you pin them and stability is only as good as the builder image tag you point at
  • The specification is neutral but the buildpacks are not, and in practice you depend on Paketo, Heroku or Google, whose roadmaps, support levels and update cadences differ; CNCF also records contributing organisations down 12 per cent year on year
  • Native dependencies, unusual monorepo layouts and non-standard project structures push you into writing custom buildpacks or extensions, which is a genuine engineering investment and not a configuration change

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 Cloud Native Buildpacks and Thredd cost?

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

Cloud Native Buildpacks

Free
  • Cloud Native BuildpacksFree
    • Apache-2.0, hosted by the CNCF
    • No commercial edition from the project itself
    • Commercial support only from vendors of specific buildpack distributions

Thredd

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

Which should you pick?

Choose Cloud Native Buildpacks if

  • You need detect and build lifecycle.
  • You want to start without paying.
  • You work on Linux, macOS, Windows, API, Self-hosted.
  • You also want image rebasing.

Choose Thredd if

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

Questions people ask

Is Cloud Native Buildpacks or Thredd better?
Neither clearly leads. Cloud Native Buildpacks 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, Cloud Native Buildpacks or Thredd?
Cloud Native Buildpacks has a free tier; the other does not. Paid plans start at Free for Cloud Native Buildpacks and On request for Thredd.
Does Cloud Native Buildpacks or Thredd run on more platforms?
Cloud Native Buildpacks runs on Linux, macOS, Windows, API, Self-hosted. Thredd runs on Web, API.
Can I use Cloud Native Buildpacks for free?
Yes. Cloud Native Buildpacks has a free tier, so you can try it without paying. Thredd starts at On request.
What is Cloud Native Buildpacks best used for?
Cloud Native Buildpacks is most often used for patching a base image once and rebasing hundreds of application images rather than rebuilding and redeploying each, removing per-team dockerfiles at an organisation where inconsistent base images have become an audit finding, giving application teams a supported path to a hardened image without teaching every team container security, choosing a build system that a risk committee will accept because governance is vendor neutral rather than single vendor. Of those, patching a base image once and rebasing hundreds of application images rather than rebuilding and redeploying each and removing per-team dockerfiles at an organisation where inconsistent base images have become an audit finding are not what Thredd is typically brought in for.
What can Cloud Native Buildpacks do that Thredd cannot?
Cloud Native Buildpacks covers Detect and build lifecycle, Image rebasing, Reproducible layers, Builder images. Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals.

Answered from the vendors’ own pages

Cloud Native Buildpacks: What does CNCF graduation actually change?

Nothing technically, but it signals audited governance, security review and multi-vendor maintenance, which is usually what a procurement or risk team needs before approving a build system.

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

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

Cloud Native Buildpacks: How is this different from writing a Dockerfile?

Container build knowledge lives with the platform team in a builder image rather than in every repository, and rebasing lets you patch the runtime base of many images without rebuilding them.

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.

Cloud Native Buildpacks: Does it cost anything?

No. The specification and tooling are Apache-2.0 and free. You pay only if you buy commercial support for a specific buildpack distribution from Broadcom, Heroku or Google.

Thredd: Is pricing published?

No, it requires a sales conversation.

Cloud Native Buildpacks: Is it slower than a Dockerfile?

On a cold build with no cache, yes. Warm builds are competitive, but continuous integration runners that start empty every time will feel the difference.

Share

Related pages

Other head to heads