UNITYZM TECHNOLOGIES · LUSAKA

The ledger stays.
The compute can travel.

UnityZM is a sovereign economic platform for Zambia: identity, payments, settlement, tax, commerce and logistics on a single runtime. It is live and serving tenants today.

The mission is to soften and harmonise the Zambian and wider African economy, removing the shocks and friction between the people who make, move, sell and settle. That is a decade of work, not a product launch.

This is what it is, how it is built, and precisely which workloads we would place on Oracle Cloud Infrastructure.

Three independent estimation methods, COCOMO, a productivity benchmark, and a domain-by-domain check, put roughly 40 person-years of engineering effort in this codebase, delivered in 4.4 months. We publish our own honest grading of how complete that makes it. It is section 10.

01 · PRIMITIVES

An economy's vocabulary is finite. Build it once.

Most platforms grow as a portfolio: a payments product, then invoicing, then logistics, each with its own data model and its own auth. Integration then becomes a tax paid forever.

UnityZM made the opposite decision at the start. Every capability is a Primitive: a standalone, supervised service implementing one economic function behind one shared interface. Payments is a primitive. So is tax. So is a delivery, a warehouse shelf, and a clinic appointment slot.

Because they share an interface, any primitive can talk to any other without knowing where it runs, same machine, same city, or a lean node at a border post.

THE CATALOGUE, 62 IMPLEMENTED TYPES

A haulage business, a certification authority and a district clinic are on the same platform wearing different configuration, not three products.

TRUST IS TIERED, AND AUTHORITY ONLY FLOWS DOWN

A commerce primitive cannot mint currency, because there is no path by which it could ask.

02 · HOW IT LAYERS

The commercial stack and the technical stack are the same stack.

UnityZM sells at four altitudes. Each is a different buyer and a different contract, but all four are served by one running platform.

These are layers rather than a menu because tier 2 customers become tier 1 volume. An operator running dispatch on the cockpit settles through the network by default. That is not cross-selling; it is architecture.

A new commercial tier is not a new build. Tier 3 exists because of one environment variable and a signed partition licence.

The same mechanism that lets us run a lean node at a border post lets us license a whole edition to an institution. The commercial model is downstream of the deployment model, which is why three consequences follow that shape what we need from a cloud partner.

03 · WHY ELIXIR / ERLANG / PHOENIX

In this market, the runtime choice is a pricing decision.

Erlang was built to run telephone switches that could not go down, on expensive hardware, maintained by small teams. That is our problem statement almost word for word.

WHAT WE GIVE UP, BEFORE YOU ASK

THE STACK

Portability is a design property, not a migration project. We can place a workload on OCI because nothing in our stack is welded to where it currently runs.

04 · THE MESH

One platform, many nodes, across ten provinces.

All three tiers run the identical release artefact. A lean node is not a cut-down product. It is the same platform with a narrowed supervision tree and a signed licence saying which role it may be.

ONE ORDER, THREE PROVINCES

A wholesaler in Chipata orders stock from a supplier in Ndola, moved by a haulier registered in Lusaka.

One transaction, three provinces, four parties, one traceable record. And the tax event is produced by the transaction that moved the goods, not reconstructed from paperwork a month later.

NOW BREAK THE NETWORK

At step 7, the link between Chipata and Lusaka drops. The Chipata node keeps working: it captures proof of delivery against local storage, signs it with its node identity, and queues it. The driver is not blocked. On reconnect the envelope replays, escrow releases, settlement completes.

What is not permitted: Chipata cannot declare finality alone. Settlement lives at trust layer 12 and stays in Lusaka.

The edge can always capture truth. Only the core can declare it final.

HOW NODES ACTUALLY CONNECT

Nodes never address each other by IP. Every message is a signed envelope, routed by a topology policy chosen at runtime, over whichever transport is currently healthy.

05 · ORDER TO DELIVERY

We don't take over a business. We close the gaps between its steps.

The classic enterprise play arrives with a system of record and asks the business to reorganise around it. In this market that is dead on arrival, and rightly so. The capital lands before the benefit, and it discards how the operator actually works.

The business is usually not broken. The seams are.

Walk a real order today: the customer orders on WhatsApp. Stock is checked on a spreadsheet, or by walking to the shelf. Payment goes to a personal mobile-money number. Dispatch is a phone call. Delivery is a photo of a signed paper note. The invoice is retyped. Tax is reconstructed at month-end from paperwork.

Every individual step works. The losses are entirely in the handoffs, and no single-purpose product fixes a handoff, because a handoff belongs to neither system on either side of it.

EVERY ECONOMIC SERVICE HAS THE SAME SHAPE

Same stages, same primitives, different configuration. This is why unrelated industries do not require forking the product.

06 · THE MISSION

Soften and harmonise.

To reduce the shocks and the friction between the people who make, move, sell and settle, so that participating in the formal economy stops being a cost and starts being an advantage.

Two verbs carry the whole thing, and they are chosen carefully.

SOFTEN, REMOVE THE HARD EDGES

An economy that runs mostly on cash has sharp edges, and people fall off them daily. Softening means replacing each cliff with a gradient. This is not aspiration. It is what the mechanisms already do:

HARMONISE, MAKE THE PARTS AGREE

Today the parts do not speak to each other. Mobile-money operators interoperate poorly, banks are separate estates, the tax authority reconstructs after the fact, the regulator sees things late, and cross-border is paperwork at a barrier.

Harmonising means the same participants settling on the same network under the same identity, so agreement is structural instead of reconciled. One network. One identity. One double-entry ledger that physically refuses a movement that does not balance. Tax and audit as products of the transaction rather than archaeology performed on it later.

Zambia borders eight countries, and our corridors already end at other economies. The same primitives that harmonise a domestic corridor harmonise a regional one. That is the ten-year shape of this: the same platform, more borders.

NOT JUST SERVICES, RESEARCH AND DATA

Zambia's economy has never been measured at transaction granularity. Policy is made on surveys, estimates and lagging indicators. Meanwhile a platform carrying orders, deliveries, invoices, settlements and corridor movements holds the most accurate picture of real economic activity anyone has had of this economy.

This is why the AI and GPU conversation is a mission conversation rather than a feature conversation. Research at this granularity is embeddings, clustering, time-series and inference over a growing corpus, precisely the workload our runtime is wrong for and elastic cloud is right for. Without capacity we do not currently have, it does not happen at all.

WIDEN WITHOUT DISTURBING DAILY LIFE

The failure mode for national infrastructure is well documented: a mandated cutover, a system that does not work on day one, and an economy that pays for the transition in lost trade. We have designed explicitly against it.

A national rail must never make somebody's Tuesday worse.

Growth is quiet by construction. We widen by being adopted, one gap and one operator at a time, not by being mandated.

07 · HARD RAILS FIRST

Build the parts that cannot be retrofitted.

There is an order to this work, and it is not the order that demos well. Identity, money, settlement and tax came first: before dashboards, before mobile apps, before anything a buyer gets excited about in a meeting.

You cannot retrofit correctness into a ledger. You can always add a screen to a correct ledger.

A ledger that has been wrong for two years cannot be repaired, every downstream balance, invoice and tax filing inherits the error. So the hard rails were built first and built strictly: double-entry journals that physically refuse a movement which does not sum to zero, hash-chained append-only event logs, trust tiers enforced at the service boundary, and settlement finality isolated at its own layer.

HOW THE SECURITY IS LAYERED

Security here is not a perimeter with an application behind it. It is seven layers, each of which assumes the one outside it has already failed.

SECURITY THROUGH THE IDENTITY VEIL

The hardest question a sovereign platform faces about AI is simple: how do you use a model without handing it your citizens?

Our answer is a subsystem called the Identity Veil (Unityzm.AI.IdentityVeil). It sits between the platform and any model, and no real identifier ever crosses it.

This is the mechanism that makes cloud AI compatible with a sovereign platform, and it materially widens what we can place with you.

It is worth stating plainly, because it changes the shape of our ask: a great deal of the inference we want to run is not residency-constrained once it passes the Veil, because there is nothing identifying left in the prompt. What stays sovereign is the mapping, the alias table itself, which never leaves.

AN SDK FOR DEVELOPERS

The fourth commercial tier is other people building on the rails. Today that surface is real but raw, and we should be precise about which is which:

An integrator today reads a spec and writes HTTP calls. That works, and several do it. But it is friction, and friction is what decides whether an ecosystem forms. Generating typed clients from the spec we already publish is a small, well-understood piece of work with a disproportionate effect on tier-4 adoption.

08 · THE DECADE

Connect the hidden regions, quietly.

Zambia's economy is not evenly visible. A corridor town has prices, records and counterparties. A ward two hours off that corridor has all the same economic activity and almost none of the infrastructure that would let anyone see it, price it, or lend against it.

The ten-year work is closing that gap, and the method matters more than the ambition. We do not arrive with a programme. We put a node where trade already happens and let it become useful.

WHY THIS COMPOUNDS ECONOMICALLY

Connecting a hidden region is not charity and it is not coverage for its own sake. Three specific things change, and they compound:

WHY IT HAS TO BE QUIET

Loud national rollouts fail here, and they fail expensively. They require a cutover date, they assume digitisation that is not there, and when they stumble the whole idea is discredited for a decade.

Nobody should ever have to be told the platform arrived. They should notice that the truck can be tracked, and that the money landed.

So expansion is deliberately unremarkable: one depot, one cooperative, one clinic at a time. Each is invisible nationally and decisive locally. That is slower, and it is the only version of this that survives contact with reality.

09 · WHY OCI

Three needs: early adoption, usage capacity, AI acceleration.

EARLY ADOPTION

The platform is built. The constraint is no longer engineering. It is capacity bought ahead of revenue.

Onboarding an operator means a configured estate, seeded data, a UAT environment and a parallel-run period: weeks of infrastructure consumed before the first invoice. Self-funded, that cost is the actual throttle on how fast we can say yes. Not demand. Not engineering. And every tier-3 licence multiplies estates to build, test and support from one team.

USAGE CAPACITY

Our load is not shaped like our steady state.

The BEAM handles concurrency well on modest hardware, which is exactly why buying permanently for the peak is such poor economics for us. We would be paying for 40× headroom that sits idle most of the month.

There is a second capacity argument, and we should raise it before you do: a single Lusaka cluster is a concentration risk. A warm standby is the cheapest credible DR available to us: encrypted, with keys held sovereign, and with certain tenants excluded from replication entirely rather than fudged.

AI ACCELERATION

Our AI posture today is deliberately frugal: all traffic passes through an internal provider-agnostic router; an intent router answers routine requests on fast deterministic paths and escalates to a model only when genuinely required; usage is metered token → credit → kwacha with double-entry ledger integration, so cost is attributable per tenant and an agent's wallet refuses to overspend before the model can.

That design cuts spend at source. What it cannot do is these five things, all of which need real compute:

10 · WHAT RUNS WHERE

State stays. Compute travels.

WHY THIS BOUNDARY IS CREDIBLE

Every vendor hears "we'll keep the sensitive part on-prem" from every prospect. What makes ours different is that the boundary is enforced in code, not in policy:

A burst node cannot silently become a settlement node because someone changed an environment variable. It is not permitted to boot into that role.

THE SHAPE OF THE TRAFFIC

This is not a bulk-data platform. It is millions of very small events, in bursts, with a hard latency expectation on a handful of them. Sizing it like a data warehouse would get the answer badly wrong in both directions.

EXPECTED THROUGHPUT BY FEATURE

Relative event volume at a modest deployment. Bars are logarithmic, because the range spans five orders of magnitude and a linear scale would show only one bar.

Latency-critical. Everything else can absorb seconds of delay without anyone noticing.

The two bars that matter are not the tall ones. Telemetry dominates the count and is entirely tolerant of delay; settlement is a rounding error in volume and tolerates none. An architecture that cannot separate those two ends up buying fast infrastructure for pings.

HOW THE AI AGENTS SPEND

Agents do not call a model whenever they feel like it. Every call passes through a metering path that makes spend attributable and bounded before it happens.

12 · HAVE vs NEED

What a valid production environment would actually require.

The platform is real and serving tenants. The environment around it is not yet what a settlement platform should run on, and we would rather set that out precisely than let it be discovered. Everything below is measured, not estimated.

A single node with one database is a deployment. It is not yet a production environment.

ENVIRONMENT TIERS

THE ONE THAT MATTERS MOST

Everything above is a degree of maturity except one row, and we will not soften it: there is no staging environment. A change to a platform that moves money, files tax and holds identity is validated by compiling, then applied to production, where migrations and an idempotent seed run on boot.

It has not bitten us yet. That is not the same as it being safe, and it is the first thing we would build with capacity we do not currently have.

AND THE MACHINE IT IS ALL BUILT ON

The whole platform, 303,000 lines across 39 applications, is written on one laptop. Here is its state as measured today, because it is the most binding constraint on this project and pretending otherwise would be silly.

Nine out-of-memory kills a month is not a preference for better hardware. It is work being lost.

This is why cloud development is on the have-versus-need list rather than filed under nice-to-have. A remote build environment would take compilation, the test suite and the local service stack off a saturated laptop. It is also the cheapest item in this entire briefing, and the one that would most immediately change delivery rate.

ENTERPRISE CAPABILITIES

THE DYNAMIC PARAMETERS

The mission expands along four axes. Each one makes a different gap binding, which is why the answer is not simply "a bigger box":

WHAT WE WOULD BUILD FIRST

None of this is exotic and none of it is research. It is the ordinary scaffolding a platform of this consequence is supposed to stand on, and it is what we mean when we say the constraint is capacity rather than engineering.

13 · IMPACT & INFRASTRUCTURE

Move the sliders. Watch the boundary pay for itself.

This is a model, not a measurement, every coefficient is shown and every one is arguable. Its purpose is to make one claim testable: that owning the peak is what makes coverage unaffordable, and that renting it is what makes rural reach possible.

14 · THE ASKS

Three questions, in the order they matter to us.

15 · WHERE WE ACTUALLY ARE

The honest grading.

We publish our own assessment of how complete this is, because velocity without disclosure is marketing. The disclosure is what makes the velocity trustworthy.

A real platform, roughly 6/10 complete, with hardening waves between here and go-live. Not "40 person-years of production-grade, done". The solo-plus-AI build bought breadth and speed and deferred some hardening. That is real debt, not a free lunch.

That gap between breadth and hardening is the reason for this conversation. A meaningful part of the remaining work is literally infrastructure.

Disaster recovery. A transport mesh between nodes. Load headroom for the peaks we can already predict. GPU capacity for the five AI workloads we cannot currently attempt. These are not features we need to invent. They are capacity we need to place.

WHAT WE WOULD LIKE TO AGREE TODAY

WHAT KIND OF CUSTOMER THIS MAKES US

We are not a startup looking for a runway. We are infrastructure looking for a decade.

That last row deserves to be said plainly. Some vendors want hybrid to be a phase. For us it is the architecture, permanently. A partner comfortable with that gets a customer who grows steadily for a decade, and should know it now rather than later.

The ledger does not move. Identity, tax and settlement finality stay on infrastructure we control. That is the product, not a preference. Everything else has no residency constraint at all, and that is what we would like to place with you.

WHO IS BUILDING IT