Softwr

APIs · head to head

Skaleet vs Vodeno

Skaleet logo

Skaleet

APIs

Cloud-native core banking and payment hub with deployments measured in months

From
On request
Rated
-
Full reviewWebsite
Vodeno logo

Vodeno

APIs

Banking-as-a-service platform running on a partner bank licence, backing NatWest's UK BaaS venture

From
On request
Rated
-
Full reviewWebsite

The short version

  • Each has a real cost: Skaleet the installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.; Vodeno its actual regulatory backing differs by geography, Aion Bank in continental Europe versus NatWest in the UK, so a customer must understand which entity and licence they are actually contracting under rather than assuming one uniform Vodeno product.
  • They diverge on capability: Skaleet covers Cloud-native core, Vodeno covers Core banking infrastructure.
  • Prices and features above were last checked on 1 September 2026.

Where they differ

Only the attributes on which Skaleet and Vodeno actually diverge.

Attributes where Skaleet and Vodeno differ
AttributeSkaleetVodeno
PlatformsWeb, REST API, LinuxWeb, 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 Skaleet

  • Cloud-native core
  • Payment hub
  • Card management
  • Lending
  • API-first
  • Configurable products

Only in Vodeno

  • Core banking infrastructure
  • Card issuance via Mastercard
  • Lending and BNPL modules
  • White-label mobile apps
  • Digital onboarding and compliance
  • UK entity backed by NatWest

What people use each for

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

Skaleet

  • A banking group launching a digital savings or deposit brand in a new country within a yearnot Vodeno
  • A bank modernising payments to ISO 20022 without replacing its whole corenot Vodeno
  • A payroll or HR software company adding embedded banking to its productnot Vodeno
  • A payment service provider needing a ledger and accounts under its existing licencenot Vodeno

Vodeno

  • A European retailer or e-commerce business wanting to embed savings, lending or BNPL products under its own brandnot Skaleet
  • A UK business wanting banking-as-a-service backed specifically by NatWest's banking technology and licencenot Skaleet
  • A fintech wanting white-label mobile banking app infrastructure rather than building its own from scratchnot Skaleet
  • A company comparing banking-as-a-service providers that want to understand which underlying bank licence actually backs the product in their marketnot Skaleet

Where each one falls short

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

Skaleet

  • The installed base is in the tens rather than the hundreds, so the pool of consultants and systems integrators who know the platform is small and expensive.
  • Speed references are mostly greenfield launches inside large groups, which is an easier problem than migrating an existing book off a legacy core.
  • It is European-centric, with payment rails and regulatory work concentrated on SEPA and EU requirements rather than global coverage.
  • As a smaller vendor carrying a bank core, it attracts hard concentration and viability questions in procurement that larger competitors do not face.
  • Pricing is unpublished and scaled by accounts and transactions, so a bank whose volumes grow faster than forecast faces cost escalation it did not model.

Vodeno

  • Its actual regulatory backing differs by geography, Aion Bank in continental Europe versus NatWest in the UK, so a customer must understand which entity and licence they are actually contracting under rather than assuming one uniform Vodeno product.
  • Pricing is entirely unpublished across both the European and UK businesses.
  • The scale of NatWest's investment (up to roughly £120 million) signals a business still working toward profitability, with NatWest itself targeting breakeven within five years of the venture launching, which is a meaningful timeline risk for a customer building long-term infrastructure dependency on it.
  • As banking-as-a-service infrastructure, any customer remains dependent on Vodeno's underlying bank partner maintaining its own licence and risk appetite, which is a layer of dependency beyond Vodeno's own commercial terms.
  • Product scope, such as lending and BNPL availability, may differ between the UK and European entities, so a company operating in both markets should not assume identical capability across the two.

Pricing, plan by plan

Skaleet

On request
  • Skaleet Core Banking Platform$undefined/year
    • Subscription licence scaled by accounts and transaction volume
    • Payment hub licensable separately from the full core
    • Implementation and configuration charged as a project

Vodeno

On request
  • Vodeno$undefined/year
    • Platform licensing fee, not published
    • Terms differ between the European (Aion Bank) and UK (NatWest) entities

Which should you pick?

Choose Skaleet if

  • You need cloud-native core.
  • You work on Web, REST API, Linux.
  • You also want payment hub.
Skaleet review

Choose Vodeno if

  • You need core banking infrastructure.
  • You work on Web, API.
  • You also want card issuance via mastercard.
Vodeno review

Questions people ask

Is Skaleet or Vodeno better?
Neither clearly leads. Skaleet starts at On request and Vodeno at On request, and user ratings are close enough to be indistinguishable. Choose on capability and platform support.
Which is cheaper, Skaleet or Vodeno?
Skaleet starts at On request and Vodeno at On request.
Does Skaleet or Vodeno run on more platforms?
Skaleet runs on Web, REST API, Linux. Vodeno runs on Web, API.
What is Skaleet best used for?
Skaleet is most often used for a banking group launching a digital savings or deposit brand in a new country within a year, a bank modernising payments to iso 20022 without replacing its whole core, a payroll or hr software company adding embedded banking to its product, a payment service provider needing a ledger and accounts under its existing licence. Of those, a banking group launching a digital savings or deposit brand in a new country within a year and a bank modernising payments to iso 20022 without replacing its whole core are not what Vodeno is typically brought in for.
What can Skaleet do that Vodeno cannot?
Skaleet covers Cloud-native core, Payment hub, Card management, Lending. Vodeno covers Core banking infrastructure, Card issuance via Mastercard, Lending and BNPL modules, White-label mobile apps.

Answered from the vendors’ own pages

Skaleet: What was Skaleet called before?

TagPay. The company rebranded to Skaleet while keeping the same platform lineage.

Vodeno: Does Vodeno hold its own banking licence?

No, it operates through partner banks, Aion Bank in continental Europe and NatWest in the UK.

Skaleet: Can I buy just the payment hub?

Yes. The payment engine is licensable standalone and can sit over an existing core, which is a common first step.

Vodeno: Is the UK business the same as the European business?

They are related but distinct entities backed by different bank partners, with different investment structures.

Skaleet: How fast are real deployments?

Named European deployments have gone live in six to twelve months, including a Crédit Agricole savings platform live in Germany in eight months.

Vodeno: How much has NatWest invested?

A capped commitment of up to roughly £120 million into the UK entity, plus a separate roughly €58 million investment in Vodeno Group for an 18% stake.

Share

Related pages

More on Skaleet

More on Vodeno

Keep looking

Other head to heads