Skip to content
Wanda

The platform

Three modules, one platform, one deployment

Wanda is API management and API monetisation as a single product. The modules are how the platform is described, not how it is bought or installed.

  • One binary and Postgres
  • Self-hosted, in-country
  • Works with the gateway you already have

The three modules

Named so a conversation can be precise about which part is under discussion. They ship as one platform.

Wanda Monetize

The revenue engine, and the reason the platform exists. Metering as it happens, plans and quotas, rating against an effective-dated price book, statements in Pula with tax per line and credit notes as first-class corrections.

Wanda Portal

Two surfaces on one catalogue. Your team publishes APIs, versions and lifecycle through the publishing console; your partners take keys, read usage and download statements through the developer portal, branded as yours.

Wanda Gateway

Enforcement, bundled or bring your own. Keys, rate limits and quotas decided in about a millisecond, with no Wanda code executing inside the gateway itself.

How it fits together

The portal is two surfaces rather than one. Your team publishes through the console and your partners consume through the developer portal, on the same catalogue, with different permissions.

How Wanda fits togetherYour team, on the left, publishes APIs, plans and prices through the publishing console. Your partner, on the right, signs in to the developer portal for keys, usage and statements. Their application calls Wanda Gateway, which enforces the plan and passes allowed calls to your APIs. The gateway sends meter events to Wanda Monetize, which rates them, returns usage and statements to the portal, and produces a statement settled through payment rails.YOURSYOUR PARTNER'SWANDAWANDA PORTALPublishing consoleAPIs, versions, lifecycle.Plans, prices and quotas.Developer portalKeys, catalogue, docs.Usage, spend, statements.Wanda MonetizeMeter, rate against the price book, tax per line.Statements, immutable. Credit notes as corrections.Wanda GatewayKeys, methods, resources and quotas, decided in abouta millisecond. Configuration rendered from the catalogue.Your teampublishes and pricesPayment railsbank transfer, mobile moneyYour APIsunchanged, where they runYour partnertakes keys, reads spendTheir applicationmakes the callsplans and pricesusage and statementswhat to enforcemeter eventspublishessigns incallsallowed callsstatement
Publishing: what your team sets upConsumption: what your partners do with it
  1. 01Your team publishes an API
  2. 02Its plan and price reach the engine
  3. 03Your partner signs in and takes a key
  4. 04Their application calls
  5. 05An allowed call reaches your API
  6. 06The call is metered
  7. 07Usage and the statement come back
  8. 08The statement settles on a rail

What holds them together

Settlement to the rails you use

Statements settle through adapters to bank transfer, Orange Money, MyZaka and Smega, so collection follows how Botswana already pays.

Onboarding without a phone call

Invite a partner onto an account, or let them self-serve into a test account with live keys gated on your approval.

Roles and teams

Role-based access in the console, so a customer puts several colleagues in front of their own tenant without sharing a login.

Statements in Setswana

Portal and statement documents both read from a translation catalogue, so an invoice arrives in the language it is filed in.

One deployment, not a kit

The minimum is one binary and Postgres. You are not assembling a platform from parts and then owning the seams between them.

Multi-tenant to the row

Every scoped table carries a tenant and an environment, and a build guard reads the SQL to prove it: 77 statements across 14 tenant-scoped tables, with the two genuinely unscoped platform tables named in an allowlist.

In-country by default

Self-hostable anywhere, including on infrastructure that never leaves Botswana. Data residency is a deployment choice you make, not a tier you buy.

Your gateway keeps its job

An estate that already runs a gateway keeps it. Wanda decides and meters behind it, which turns an existing investment into a complement rather than a rip-out.

Publish once, enforced everywhere

An API version published in the console renders the gateway configuration that enforces it. The catalogue and the edge cannot disagree, because one is generated from the other.

Evidence over assurance

Structured logs carrying trace context on every line, metrics for decisions, denials, rating runs and statements, and alerting that watches its own delivery path.

Corrections, never edits

An issued statement is immutable, enforced by a database trigger rather than by convention. A correction is a credit note, so the figure a customer saw is the figure that stays.

One deployment, wherever you need it

The minimum footprint is one binary and Postgres. Identity and a gateway join it for public traffic, and the whole thing runs on infrastructure you control.

On your own hardware

In a rack in Gaborone or a cabinet in your own data centre. Nothing calls home, and no usage leaves the country unless you send it there.

On your cloud account

Containers and declarative configuration, non-root images, managed Postgres where you want it. No virtual machine is an architectural unit.

Beside what you already run

Your gateway keeps handling traffic. Wanda decides, meters and bills behind it, so an existing investment becomes a complement.

Price one of your own endpoints against it.

The fastest way to judge a platform like this is to meter something you already run and read the statement that comes out. That is a short conversation, not a procurement.

Talk to us about your APIsSign in to the portal
Wanda by Kalabeta