Skip to content
Aftian

The platform

The parts every application needs, built properly, once

Nine services sit underneath everything we make. Each has one job and does it for whichever product asks. They are not a library bundled into four codebases — they are running services with their own data, which is why a change to one is a change for all four at the same instant.

01

Identity

One account across every product.

Used by

DeygoShop ERPSwiftNetStreaming

An OpenID Connect provider issuing the tokens every other service trusts. Products hold no passwords and mint no tokens of their own: they validate a bearer token by asking the identity service about it, so a revoked session is revoked everywhere at once.

Instead of

writing a login screen, a password reset flow and a session store per product

02

Payments

Mobile money, collected and paid out.

Used by

DeygoShop ERPSwiftNet

A gateway over MTN Mobile Money and Orange Money - the way money actually moves in Central Africa. Collections and disbursements, idempotent requests, signed webhooks back to the product that asked, and a single record of every attempt whether it settled or not.

Instead of

integrating two carrier APIs, and reconciling them, four separate times

03

Ledger

Double-entry accounting as a service.

Used by

DeygoShop ERPSwiftNetStreaming

Every balance on the platform lives here, as entries rather than a number in a column. Wallets, merchant payouts, commissions and ERP accounts all post to the same ledger, which means a balance can always be explained by the transactions that produced it.

Instead of

a balance column that drifts, and no way to prove what it should have been

04

Catalogue

Products, variants and stock.

Used by

Shop ERP

One model that covers physical goods, subscriptions and vouchers, with variants and stock levels tracked per location. Inventory writes go through an outbox, so a stock movement is never lost to a failed request half way through a checkout.

Instead of

a products table per product, each with its own idea of what a variant is

05

Orders

Cart to invoice, end to end.

Used by

Shop ERPSwiftNetStreaming

Carts, orders, payment capture, shipments, invoices and returns. It is the service that ties catalogue, payments, ledger and notifications together into one checkout, so a product gets a working order lifecycle without owning any of it.

Instead of

re-deriving order state machines, and getting the refund path wrong

06

Billing

Subscriptions, renewals and dunning.

Used by

SwiftNetStreaming

Recurring plans on top of orders: proration when a customer changes plan mid-cycle, scheduled renewals, and a dunning sequence when a charge fails instead of silent cancellation. One ISP and one streaming service bill through it today.

Instead of

a cron job that charges cards and hopes

07

Places

A gazetteer that knows this region.

Used by

DeygoShop ERPSwiftNet

Place search and reverse geocoding built on a harvested gazetteer rather than a per-call commercial API - because addresses here are landmarks and neighbourhoods, not street numbers, and the global providers are both expensive and wrong about that.

Instead of

paying per lookup for results that do not match how people give directions

08

Notifications

Email, push and in-app, once.

Used by

DeygoShop ERPSwiftNetStreaming

One send path for transactional mail, push notifications and the in-app bell, with templates and delivery records. A product asks for a notification by name and audience; it does not hold a provider credential or a template engine.

Instead of

four codebases each with their own SMTP settings and HTML email

09

Chat

Conversations between any two parties.

Used by

Deygo

Threads keyed by an opaque reference the calling product chooses, so the chat service never learns what a conversation is about - a delivery, a support ticket, an order dispute. New messages are delivered by signed webhook into whatever the product uses for real-time.

Instead of

a messages table and a WebSocket server per product

Architecture

How it fits together

Four decisions shape the whole thing. They are worth stating plainly, because each one rules out a class of problem rather than solving an instance of it.

01

One place holds identity

A person signs in once, at the identity service. No product stores a password or issues a token of its own — they receive one and ask the identity service whether it is still valid. The consequence that matters: revoking a session revokes it everywhere, immediately, with nothing to propagate.

02

Services talk privately

The services reach each other over a private network, not over the public internet. Only the front door is exposed; the database publishes no port at all. A service that should never be called from outside cannot be.

03

Products own only their own domain

A marketplace owns jobs and providers. A retail system owns merchandising. Neither owns accounts, money or stock-keeping, because those are not what makes them different. The shared service owns the hard part, and the product owns the decision.

04

Shared services never learn the context

Chat threads are keyed by a reference the calling product chooses, so the chat service cannot tell a delivery from an order dispute. Payments are tagged by client, not by purpose. Each service does its job without accumulating knowledge it has no use for.

What we do about silence

The expensive failure in a system of services is not the one that crashes. It is the one that returns success while doing nothing — a wrong key accepted, a webhook that never arrives, a balance that was never written.

  • Credentials are proved, not assumed

    Every service-to-service key is tested with a real request and a deliberately wrong one. Matching values prove nothing; a 401 for the wrong key does.

  • Misconfiguration refuses

    A service missing the secret it needs returns an error rather than accepting anything. An unset webhook secret would make an endpoint open to the world, so it is treated as a hard failure.

  • Money is written twice or not at all

    Ledger postings are double-entry and balanced. A payment that cannot be accounted for does not silently become a balance.

  • Stock movements survive a crash

    Inventory changes go through an outbox, so a request that dies half way through checkout does not lose the movement it had already decided on.

See what we built on it

Four products in four industries, each one shipping the part that makes it different.

Our products