Skip to content
Aftian

Founders

Who is behind this

A small company, deliberately. Everything on this site — nine services, four products, the machine they run on — was built by the people on this page.

Afuh Christian

Founder

Responsible for

  • Architecture of the shared platform
  • The services themselves — .NET, Rust, Postgres
  • Infrastructure and deployment
  • Product direction across all four

Started Aftian, and built the platform every product stands on.

Aftian began as one application and the realisation, somewhere around the third one, that the hard parts were identical every time. Rather than copy them, Christian pulled them out: identity, payments, a double-entry ledger, a catalogue, orders, billing, places, notifications and chat, each as a service with one job.

That decision is the company. It is why the fourth product cost a fraction of the first, and why a mobile-money improvement lands in four applications at once instead of one.

The work since has been as much about operations as code: moving the whole platform onto infrastructure it can survive on, making failures loud instead of silent, and proving every credential with a real request rather than assuming it works.

What that means in practice

The beliefs this company runs on

These are not values on a wall. Each one rules something out, which is the only test of whether a principle is real.

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.

Want to build this with us?

There is no open role posted today, but we read everything that comes in — and the people we end up working with usually wrote first.