I · Origin
Know where the data came from.
Every system starts with a map of its sources. Who produces each event, under what guarantees, and what happens when it is wrong. We write that down before we write code.
Operational · Cape Town · taking contracts
Systems that remember where they began.
Afrogenitor is a software engineering company. We design and build systems for teams who need to know where their data came from, how it changed, and why. Senior engineering, on contract or embedded.
01 · Services
What we build.
Four kinds of work, one habit: every system we ship can explain where its data came from. That is not a product feature. It is how we engineer.
- 01
Data and event systems
Pipelines and services where order, history and replay matter. Built so the record of what happened is never in question.
Where it fitsSystems of record · integrations · real-time products
- 02
AI-native systems
Intelligent features that can show their working. Outputs traceable to their sources, with people reviewing where it matters.
Where it fitsAssistants and agents · search over your own knowledge · decision support
- 03
Product engineering
From data model to screen, on the web and on phones. The unglamorous parts done properly: access, migrations, testing, accessibility.
Where it fitsNew products · rebuilds · a second team on a deadline
- 04
Platform and infrastructure
The foundations most teams inherit rather than design. Delivery, environments, observability and hardening, from a background that started in server rooms.
Where it fitsCloud and on-premises · a first platform · clean-up after an incident
Fixed-term contract
Three to twelve months, outcome-scoped, with a written record of decisions handed over at the end.
Embedded senior engineer
Part of your team, your tools, your standups. Fractional or full weeks.
Advisory and review
Architecture reviews, provenance audits of data pipelines, and a second opinion before a big build.
02 · Approach
We build the way we record.
II · Lineage
Every change is traceable.
Append-only where it matters, migrations as history, decisions recorded with the code. Six months later, you can answer "why is it like this" without archaeology.
III · Relation
Systems are graphs, not silos.
Services, teams and data are related, and the integration is the product. We design the edges with the same care as the nodes.
03 · Interests
Meaning lives between things.
Questions we keep returning to between contracts. They shape how we engineer for everyone else.
| Seal | Record | Interest |
|---|---|---|
| interest:kinship0x204f47a5 | Kinship as dataClans, totems, guardianship and oral history, modelled as first-class data instead of notes in a free-text field. | |
| interest:custom0x73b3f278 | Customs as processesRites and life stages have participants, order and conditions. They are processes, not static facts. | |
| interest:provenance0x453cecb8 | ProvenanceFirst claims of creation, timestamped. Recorded before anyone has a reason to rewrite them. | |
| interest:lineage0x1d89e5a0 | Lineage as graphsKinship, custom and biology branch, borrow and rejoin. Graphs, not trees. | |
| interest:population0xafef5bdc | Population-aware lineage modelsLineage models that fit the people they describe, not the defaults of the tool that stores them. |
04 · Contact
Tell us what you are building.
A short note is enough. We reply within two working days, and every message gets a seal so you can see it was received, not just sent.
Cape Town
Remote across EU and US hours