Softwr

APIs · head to head

Thredd vs Zeplo

Thredd logo

Thredd

APIs

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

From
On request
Rated
-
Full reviewWebsite
Zeplo logo

Zeplo

APIs

Message queue as a URL prefix, adding retries and delays to any HTTP request

From
Free
Rated
-
Full reviewWebsite

The short version

  • Only Zeplo has a free tier, so it costs nothing to try first.
  • Each has a real cost: Thredd pricing is entirely unpublished, so cost comparison against competing processors requires a sales process.; Zeplo zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
  • They diverge on capability: Thredd covers Issuer processing, Zeplo covers URL prefix interface.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Thredd and Zeplo actually diverge.

Attributes where Thredd and Zeplo differ
AttributeThreddZeplo
Starting priceOn requestFree
Pricing modelquotePer month by request count
Free tierNoYes
PlatformsWeb, APIWeb, Cloud

Identical on both: user rating (Not yet rated), category (APIs).

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 Thredd

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

Only in Zeplo

  • URL prefix interface
  • Retries with backoff
  • Delayed delivery
  • Cron scheduling
  • Concurrency limits
  • Deduplication keys
  • Request logs
  • Team workspaces

What people use each for

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

Thredd

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

Zeplo

  • A Vercel or Cloudflare Workers application that needs retried background jobs without deploying a separate always-on workernot Thredd
  • A team that wants a webhook receiver protected by a concurrency limit so a burst does not overwhelm a downstream APInot Thredd
  • A small product needing cron jobs against HTTP endpoints without adding a scheduler to its infrastructurenot Thredd
  • A developer adding idempotent retries to an unreliable third-party API call with a one-line URL changenot Thredd

Where each one falls short

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

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.

Zeplo

  • Zeplo sits directly in the execution path of your background work, so an outage at a very small vendor means your jobs do not run at all, and there is no published SLA below Enterprise.
  • The free Developer tier includes only 500 requests a month and one team member, so it is a demonstration allowance rather than a usable free plan for anything real.
  • Overage on the Developer tier is 20 US dollars per 100,000 requests, two hundred times the marginal rate on the Company tier, so exceeding the free allowance without upgrading is expensive.
  • Team members cost 15 US dollars each beyond the plan allowance, which is an odd charge on an infrastructure product billed by request volume.
  • Log retention is 30 days on both published tiers, so anything requiring longer audit trails on job execution has to be logged separately.

Pricing, plan by plan

Thredd

On request
  • Thredd$undefined/year
    • Volume and programme-based pricing, not published
    • Custom quote required via sales

Zeplo

Free
  • DeveloperFree
    • 500 requests a month included
    • $20 per additional 100,000 requests
    • 1 team member
  • Company$39/month
    • 1,000,000 requests a month included
    • $10 per additional million requests
    • Up to 3 team members
  • Enterprise$undefined/month
    • Volume discounts
    • Custom team size
    • Support with SLA

Which should you pick?

Choose Thredd if

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

Choose Zeplo if

  • You need url prefix interface.
  • You want to start without paying.
  • You work on Web, Cloud.
  • You also want retries with backoff.
Zeplo review

Questions people ask

Is Thredd or Zeplo better?
Neither clearly leads. Thredd starts at On request and Zeplo at Free, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Thredd or Zeplo?
Zeplo has a free tier; the other does not. Paid plans start at On request for Thredd and Free for Zeplo.
Does Thredd or Zeplo run on more platforms?
Thredd runs on Web, API. Zeplo runs on Web, Cloud.
Can I use Zeplo for free?
Yes. Zeplo has a free tier, so you can try it without paying. Thredd starts at On request.
What is Thredd best used for?
Thredd is most often used for a digital bank or fintech needing issuer processing across many countries under one contract, a bnpl, lending or crypto product needing certified card processing behind its own brand, a company that finds outdated global processing services (gps) material and needs to confirm it is now thredd, an embedded finance platform wanting a processor already integrated with core banking systems such as mambu. Of those, a digital bank or fintech needing issuer processing across many countries under one contract and a bnpl, lending or crypto product needing certified card processing behind its own brand are not what Zeplo is typically brought in for.
What can Thredd do that Zeplo cannot?
Thredd covers Issuer processing, Multi-country reach, Scheme certification, Programme support across verticals. Zeplo covers URL prefix interface, Retries with backoff, Delayed delivery, Cron scheduling.

Answered from the vendors’ own pages

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

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

Zeplo: How does Zeplo work?

You prefix your endpoint URL with zeplo.to and add query parameters for retries, delay, cron or concurrency. No SDK or broker is needed.

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.

Zeplo: What does it cost?

Free for 500 requests a month; 39 US dollars a month for a million requests, then 10 dollars per additional million.

Thredd: Is pricing published?

No, it requires a sales conversation.

Zeplo: Is it suitable for critical jobs?

It is a small vendor in your execution path with no published SLA below Enterprise, so weigh that against the convenience.

Zeplo: Does it work with serverless platforms?

Yes, that is its main use, covering Vercel, Cloudflare Workers, Netlify and similar environments that lack long-running workers.

Share

Related pages

More on Thredd

More on Zeplo

Keep looking

Other head to heads