Skip to content
Wanda

Compare

The question a self-hosting buyer actually asks

Not which platform has the longest feature list. Which one turns calls into a statement you can defend, on infrastructure you control, without a managed tier.

Capability by capability

The first three rows are the ones that decide a Botswana deal, and no platform on this list answers them. A statement in Pula with tax at the rate in force, collection on the rails your customers already use, and a deployment that never leaves the country.

Wanda compared with Kong OSS, Tyk OSS, WSO2 API Manager, Gravitee CE and Zuplo
CapabilityWandaKong OSSTyk OSSWSO2 APIMGravitee CEZuplo
Billing in Pula, tax at the rate in forceEffective-dated rates as exact rationals, zero-rated and exempt distinguishableNativeNot offeredNot offeredNot offeredNot offeredNot offered
Settlement to Botswana railsBank transfer, Orange Money, MyZaka, SmegaNativeNot offeredNot offeredNot offeredNot offeredNot offered
In-country deployment, no call homeNativeNativeNativeNativeNativeNot offered
Metering with re-runnable ratingQuantity events, idempotent on the producer's own idNativeNot offeredPaid tierBasicBasicHosted only
Statements and credit notesImmutable once issued, corrected rather than editedNativeNot offeredNot offeredBasicNot offeredNot offered
Plans, entitlements and per-consumer quotasNativePaid tierPaid tierNativeBasicHosted only
White-label developer portalPer-tenant brand and hostname, contrast enforced at the writeNativePaid tierPaid tierBasicBasicHosted only
Multi-tenancy: operator, tenant, environmentNativePaid tierPaid tierBasicBasicHosted only
Works with the gateway you already runNativeNot offeredNot offeredNot offeredNot offeredNot offered
Self-host footprintOne binary and Postgres for the money pathNativeBasicBasicNot offeredBasicNot offered

Open source editions unless marked otherwise. Where a capability sits behind a commercial tier it is shown as such rather than as absent.

The five axes behind those rows

Kong, Tyk, WSO2 API Manager, Gravitee and Zuplo are the names that come up. Here is each axis that decides a self-hosted evaluation, with our position on it stated plainly.

Monetisation, self-hosted

Wanda

The full loop is in the product you install: metering, an effective-dated price book, rating, tax per line, statements, credit notes and a settlement boundary.

The established platforms

Usually the paid tier, the managed tier, or a partner integration. This is the axis Wanda is built to win.

API management

Wanda

Keys, plans, quotas, a branded developer portal, and a real catalogue: APIs as first-class objects with versions and a draft, published, deprecated and retired lifecycle, browsable and searchable by your consumers.

The established platforms

Mature, and deeper in places. The established platforms have spent a decade here. If authoring depth is your first requirement rather than revenue, say so early and we will tell you straight.

Traffic handling

Wanda

Deliberately not ours. Wanda decides and meters behind a gateway rather than being one, which is what lets you keep the traffic layer you have.

The established platforms

Their ground, and deservedly. The point of our integration story is that you keep it.

Deployment footprint

Wanda

One binary and Postgres for the money path, with identity and a gateway joining it for public traffic. Small enough to run in a rack, complete enough to bill on.

The established platforms

Varies from comparable to considerably heavier.

In-country deployment

Wanda

Self-hostable anywhere, including infrastructure that never leaves Botswana, with no call home.

The established platforms

Possible for several, and commercially awkward for the ones whose model is managed.

What makes the difference

Monetisation is not a tier

Metering, rating, tax, statements and credit notes are in the product you install, not behind an enterprise plan or a managed offering.

Your gateway keeps its job

We integrate with the traffic layer you already run instead of asking you to replace it, which turns a live investment into a complement.

In-country, with no call home

Deployed where your data has to live, including infrastructure that never leaves Botswana. Residency is a deployment fact rather than a clause.

Bring the shortlist.

If another platform is the right answer for your estate we would rather establish that in a conversation than in an implementation.

Wanda by Kalabeta