Softwr

APIs · head to head

Tuum vs Weavr

Tuum logo

Tuum

APIs

Modular core banking platform from Estonia, formerly branded Modularbank

From
On request
Rated
-
Full reviewWebsite
Weavr logo

Weavr

APIs

Packaged embedded finance for B2B SaaS, with an in-house EU e-money licence

From
On request
Rated
-
Full reviewWebsite

The short version

  • 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.; Weavr products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • They diverge on capability: Tuum covers Modular product structure, Weavr covers Plug-and-play products.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Tuum and Weavr actually diverge.

Attributes where Tuum and Weavr differ
AttributeTuumWeavr
PlatformsWeb, APIWeb, REST API

Identical on both: starting price (On request), pricing model (quote), free tier (No), 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 Weavr

  • Plug-and-play products
  • Regulated cover
  • Card issuing
  • Multi-currency accounts
  • Identity and onboarding
  • Data insights

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 Weavr
  • A fintech in the DACH region or Middle East wanting a European core banking vendor with regional expansion focusnot Weavr
  • An institution wanting low-code middleware to connect new modules to an existing legacy core rather than a full rebuildnot Weavr
  • A company researching "Modularbank" that needs to confirm it is the same company now branded Tuumnot Weavr

Weavr

  • A project management SaaS adding expense cards without hiring a compliance officernot Tuum
  • A marketplace paying out sellers from accounts held inside its own productnot Tuum
  • A procurement platform issuing virtual cards against approved purchase ordersnot Tuum
  • A European SaaS vendor wanting a regulated entity to sit behind its financial featuresnot 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.

Weavr

  • Products are packaged rather than open, so a flow Weavr does not support is not something you can build around, and you discover the limits after integrating.
  • Programme economics depend on interchange, and SaaS vendors routinely overestimate how much card volume their customers will actually route through the embedded product.
  • It is a small company with limited headcount supporting a regulated dependency, which is a real concentration risk for a feature your customers rely on.
  • Monthly minimums on card programmes mean a slow-adopting customer base leaves you paying for volume you never reach.
  • European interchange caps hold programme revenue well below what US embedded finance case studies suggest, so imported business cases do not transfer.

Pricing, plan by plan

Tuum

On request
  • Tuum$undefined/year
    • Subscription and module-based pricing, not published
    • Custom quote required via sales

Weavr

On request
  • Weavr embedded finance$undefined/year
    • Platform subscription plus per-account and per-card fees
    • Interchange share negotiated as part of the commercial terms
    • Monthly minimums apply to card programmes

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 Weavr if

  • You need plug-and-play products.
  • You work on Web, REST API.
  • You also want regulated cover.
Weavr review

Questions people ask

Is Tuum or Weavr better?
Neither clearly leads. Tuum starts at On request and Weavr at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Tuum or Weavr?
Tuum starts at On request and Weavr at On request.
Does Tuum or Weavr run on more platforms?
Tuum runs on Web, API. Weavr runs on Web, REST API.
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 Weavr is typically brought in for.
What can Tuum do that Weavr cannot?
Tuum covers Modular product structure, Low-code integration middleware, Cloud-agnostic deployment, Multi-currency real-time accounts. Weavr covers Plug-and-play products, Regulated cover, Card issuing, Multi-currency accounts.

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.

Weavr: Do I need my own financial licence?

No. Weavr holds an e-money licence, including a Maltese authorisation for the EU, and acts as the regulated entity for the embedded product.

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.

Weavr: How is it different from a banking-as-a-service API?

It sells finished product shapes with compliance built in rather than raw banking primitives, which trades flexibility for a much shorter route to launch.

Tuum: Is pricing published?

No, subscription and module pricing require a sales conversation.

Weavr: How does Weavr make money?

Platform fees plus per-account and per-card charges, with a negotiated share of card interchange.

Share

Related pages

More on Tuum

More on Weavr

Keep looking

Other head to heads