Softwr

APIs · head to head

Tuum vs Zeplo

Tuum logo

Tuum

APIs

Modular core banking platform from Estonia, formerly branded Modularbank

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: Tuum it is a smaller, younger company than Mambu, so it has fewer live reference deployments and a shorter track record to evaluate risk against.; 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: Tuum covers Modular product structure, Zeplo covers URL prefix interface.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Tuum and Zeplo actually diverge.

Attributes where Tuum and Zeplo differ
AttributeTuumZeplo
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 Tuum

  • Modular product structure
  • Low-code integration middleware
  • Cloud-agnostic deployment
  • Multi-currency real-time accounts
  • Cards and lending modules
  • Faster migration timeline

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.

Tuum

  • A bank wanting to migrate specific banking products to the cloud within months rather than replacing its entire core at oncenot Zeplo
  • A fintech in the DACH region or Middle East wanting a European core banking vendor with regional expansion focusnot Zeplo
  • An institution wanting low-code middleware to connect new modules to an existing legacy core rather than a full rebuildnot Zeplo
  • A company researching "Modularbank" that needs to confirm it is the same company now branded Tuumnot Zeplo

Zeplo

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

Where each one falls short

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

Tuum

  • It is a smaller, younger company than Mambu, so it has fewer live reference deployments and a shorter track record to evaluate risk against.
  • The 2022-era rebrand from Modularbank to Tuum means older funding records, case studies and press coverage appear under a different name, complicating due diligence for anyone unaware of the change.
  • Pricing is entirely unpublished, requiring a sales conversation to budget against competing composable core vendors.
  • Its geographic expansion into DACH and the Middle East is comparatively recent, so support depth and local regulatory expertise in those markets are less proven than in its home Baltic and Nordic base.
  • As with any core banking platform, choosing Tuum is a multi-year infrastructure commitment; switching cores after implementation is a major undertaking regardless of how modular the initial adoption was.

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

Tuum

On request
  • Tuum$undefined/year
    • Subscription and module-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 Tuum if

  • You need modular product structure.
  • You work on Web, API.
  • You also want low-code integration middleware.
Tuum 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 Tuum or Zeplo better?
Neither clearly leads. Tuum 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, Tuum or Zeplo?
Zeplo has a free tier; the other does not. Paid plans start at On request for Tuum and Free for Zeplo.
Does Tuum or Zeplo run on more platforms?
Tuum 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. Tuum starts at On request.
What is Tuum best used for?
Tuum is most often used for a bank wanting to migrate specific banking products to the cloud within months rather than replacing its entire core at once, a fintech in the dach region or middle east wanting a european core banking vendor with regional expansion focus, an institution wanting low-code middleware to connect new modules to an existing legacy core rather than a full rebuild, a company researching "modularbank" that needs to confirm it is the same company now branded tuum. Of those, a bank wanting to migrate specific banking products to the cloud within months rather than replacing its entire core at once and a fintech in the dach region or middle east wanting a european core banking vendor with regional expansion focus are not what Zeplo is typically brought in for.
What can Tuum do that Zeplo cannot?
Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts. Zeplo covers URL prefix interface, Retries with backoff, Delayed delivery, Cron scheduling.

Answered from the vendors’ own pages

Tuum: Is Tuum the same company as Modularbank?

Yes, Modularbank rebranded to Tuum; 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.

Tuum: Where is it strongest geographically?

Its base is Estonia and the Nordic and Baltic region, with newer expansion into DACH and the Middle East.

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.

Tuum: Is pricing published?

No, subscription and module pricing require 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 Tuum

More on Zeplo

Keep looking

Other head to heads