Software should belong to the place it runs.

We build software and systems for places where the network drops, people read Somali before English, and the people who run the software should own it. Then we write down how, so the work can be checked.

Dune ridge meeting a concrete seawall

It started with the tools. Each one asked the company to change its shape to fit it, and each one lived in someone else’s cloud.

Meanwhile the work was already running. An office issued certificates on paper, with stamps, a queue and a clerk who knew which desk came next. A business moved goods across three borders, and its memory lived in a WhatsApp thread. A dispatcher ran a fleet of trucks from a whiteboard. None of it was broken. It was slow, and it forgot.

So we stopped asking which tool had the most features and started reading the paper. The form already said what the office needed to know. The ledger already refused to rub anything out. The handover note already waited for the morning shift. Most of our techniques are older than software. We wrote them down and built them in.

The rest came from building where we are: phones before laptops, a weak connection at night, two languages at every counter, and servers that belong to the people who pay for them.

What we hold to

  1. Somali from the first day

    Somali and English sit side by side, because the people at the counter read both. Never a translation for later.

  2. Plan before code

    The goal, what is in, what is out, the steps in order, and how we will know it is done. Zero open questions.

  3. Read the paper before replacing it

    The paper form, the whiteboard and the WhatsApp group already run the work. The new system wins when it feels like the old one, without the queue.

  4. Stamp, never erase

    Every change is one named action that says who, when and why. Nothing is rubbed out.

  5. Plain rules, never guesses

    The machine watches and suggests. A person decides. Anything it tells you links to what proves it.

  6. The customer owns the server

    One organization, one deployment, on its own server. Your work is not a tenant in someone else’s cloud.

Where this goes

Six systems are working or in build. Each one taught us a technique, and each technique now has a name, a source and a list of places it is used. The next job is to hand them on.

We want a clinic, an office or a freight business to find a system built the way it already works, run it on its own server, and change it without asking us. And we want the people who build, translate and test those systems to find each other here. The case studies are what we have built. The workshop is what we are building. The community is who builds next.

Built for here. Owned by the people who run it.

If you build, dream, or make, you belong here.

Find your way in