Skip to content
Aftian

Software company · Cameroon

One platform.
Every product.

Identity, payments, accounting, commerce and messaging are the same problems in every application. We solved them once, as nine shared services — then built our products on top. A marketplace, a retail system, an ISP platform and a video service, all standing on the same foundation.

9

shared services

built once, used by every product

4

products

on the same platform

1

identity provider

one sign-in across everything

Why we work this way

Four products. One of everything.

Most companies building four applications build four of everything underneath them: four login systems, four payment integrations, four ways of counting money. Each one is a place to get it wrong.

We built the underneath first. There is one identity provider, so an account works across every product and a revoked session is revoked everywhere. There is one payments gateway, so a mobile-money integration that improves improves for all four. There is one double-entry ledger, so a balance is never a number someone incremented — it is the sum of transactions, and it can always be explained.

The effect compounds in the other direction too. A new product does not start from nothing. It starts with accounts, payments, accounting, a catalogue, orders, subscriptions, notifications and chat already working — and ships with the parts that make it different, not the parts every application needs.

  • One account across every product
  • One integration per payment provider, not four
  • Every balance traceable to its transactions
  • A fix in a shared service is a fix everywhere, at once

The platform

Nine services, built once

Each one does a single job for every product that asks. None of them knows what the others are for.

How it fits together

Identity

One account across every product.

Payments

Mobile money, collected and paid out.

Ledger

Double-entry accounting as a service.

Catalogue

Products, variants and stock.

Orders

Cart to invoice, end to end.

Billing

Subscriptions, renewals and dunning.

Places

A gazetteer that knows this region.

Notifications

Email, push and in-app, once.

Chat

Conversations between any two parties.

What we build

The products on it

Different industries, different customers, the same foundation.

How we build

Four things we hold to

Build it once

Nine services exist so that four products do not each need their own identity, payments and accounting. A fix to the ledger is a fix for every product at the same moment - and a bug there is one bug, found once.

Money is accounted for, not stored

No balance on this platform is a number someone increments. Balances are the sum of double-entry transactions, which means every figure can be traced to the events that made it.

Built for how payment works here

Mobile money first, not a card form with mobile money added later. Prices in XAF. A gazetteer that understands landmarks rather than street numbers.

Failure should be loud

The expensive bugs in a distributed system are the silent ones - a service answering 200 while doing nothing. Credentials are tested against a wrong-key control, not assumed, and a misconfigured service refuses rather than pretends.

Building something that needs this foundation?

We work with teams who need accounts, mobile money, accounting or commerce to already work — so they can build the part only they can build.