A marketplace on day one, a superapp by design

Mauritius is a small market. That is the reason usually given for why no one has built it a marketplace to international standard. I read the smallness the other way. One island, one payment culture, one logistics map, and no single platform tying commerce, services, and payments together. That is not a market too small to serve. It is a superapp waiting to be built.

Ship a multi-vendor marketplace that can go live this year. Then architect it so everything meant to come after it, from moving people around the island to moving money on it, attaches without a rewrite. And build the whole system audit-ready and integration-ready from the first commit, not bolted on under regulatory pressure the week before it matters. Compliance-first, not compliance-eventually.

A marketplace usually takes a team. A backend group, a frontend group, someone who owns payments, someone who owns infrastructure, someone who signs off on security and compliance. I was all of them.

The count of hats is not the point. The point is what one person can decide when they wear all of them at once. The hard part of a platform is never version one. It is whether versions two, three, and four cost an afternoon or a rewrite. So that is where the architecture went.

Payments sit walled off, schema-per-tenant: one merchant’s breach stays one merchant’s problem instead of everyone’s. The event spine is append-only, so nothing that happened can quietly un-happen, and it runs on a durable outbox drained by workers, with no message broker to keep alive at three in the morning. Security is enforced by constraint, not by convention: the system is built so the wrong thing is hard to do, instead of trusting everyone to remember not to do it. Every outside provider is pinned and watched for drift, so when a third party shifts under the platform, the platform notices before a customer does.

It is built by one person, but it is not built to stay that way. The tests, the pipelines, the monitoring, and the coding conventions a second engineer would follow are all in place and documented, so the next hire inherits a map instead of a mystery. Data-protection erasure reaches across every service on request, because on this island that is law, not a nice-to-have. And when the SMS provider stopped earning its place, I pulled it and rebuilt the whole channel on email in a weekend, because nothing downstream had been allowed to quietly depend on it.

Three surfaces, one core, one person, from the domain model to the production infrastructure. You can move at that speed on decisions that carry this much weight in exactly one situation: when the same person owns every layer.

One person, one architecture, and no team to coordinate. That is the part that catches the eye. The part that matters is the judgment underneath it: an architecture already right about mobility, payments, and compliance before any of the three had shipped, and built to hand to a team without a rewrite. This is the work behind the services on this site. I plan systems like it for other people’s ventures, and I build a few myself.