Building practical systems with a longer horizon

It started in Zimbabwe. I was tinkering with drag-and-drop tools, building my first app. It was simple, clunky, but it worked… until the platform I relied on went out of business. That’s when I decided to learn how to code for real.

A few years in, I asked myself a big question: Why don’t we have a Google-equivalent in Africa? I saw a gap — not just in technology, but in opportunity, in the way resources and funding were distributed. That realization became a challenge: envision the future of intelligence and start building it piece by piece.

Centrigon began as that experiment: a platform to test ideas, refine tools, and build something useful along the way. Some of it was a moonshot — honestly, a huge leap of imagination — but I knew I needed something tangible in the interim. Tools that people could use, instantly, without fuss.

For now, the focus is practical utility. Fast tools. Clear interfaces. Systems that solve real problems immediately. But underneath that is a longer-term interest in how intelligence, interaction, and computation evolve over time. The tools are useful on their own, but they're also part of a larger process of learning what scales, what breaks, and what people actually need.

Most ambitious technology begins as abstraction. We’re more interested in systems that survive contact with reality. Tools are immediate, measurable, and brutally honest. Either they help people or they don’t. That makes them a good foundation for exploring larger ideas without drifting into empty futurism.

Building from Zimbabwe also changes perspective. Constraints force prioritization. Limited infrastructure forces efficiency. And distance from traditional tech centers creates room to think differently about access, resilience, and who technology is actually for.

Practical tools first: Every tool you see here is something we'd use ourselves. Instant results, no clutter, privacy-first. If it doesn't solve a real problem, it doesn't belong.

Systems over spectacle: We care more about durability than announcements. Useful systems compound quietly. Hype fades quickly; infrastructure tends to persist.

Continuous learning: We experiment, we improve, we listen. Feedback isn't just appreciated — it shapes the next step. The best ideas often come from people who actually use what we build.