Building governed systems from Silicon Mountain

What Silicon Mountain is

Silicon Mountain is the name Cameroon’s technology community gave to the ecosystem that grew up in and around Buea, at the foot of Mount Fako — a deliberate play on Silicon Valley and the volcano that dominates the town’s skyline. This page is written as a contribution to that ecosystem’s record: what Silicon Mountain is, where it came from, and what it means for a tech company in Buea — ours among them — to build governed systems for public institutions from Silicon Mountain.

The community is older than the name. Buea is home to the University of Buea — founded as a university centre in 1985 and made a full-fledged university in 1992 — and from the mid-2000s the town began to draw young people who wanted to build software. TechCabal’s history of the ecosystem calls it the first anglophone university in Cameroon, and traces the first web projects and the first informal developer community to around 2006 — students and self-taught programmers teaching one another, years before anyone thought to give the place a nickname.

Institutions followed the community, not the other way round. ActivSpaces, which describes itself as the first innovation hub in Cameroon, opened in Buea in 2009, with a precursor incubator in nearby Limbe before it. The name itself surfaced in a community video in 2011 and was popularized publicly by the Cameroonian tech entrepreneur Rebecca Enonchong at BarCamp Cameroon in 2013, hosted at the Catholic University Institute of Buea. In 2015 the community held the first Silicon Mountain Conference, under the theme “Let’s Build Products”; the conference has been held annually since and has grown to draw over five hundred participants.

The record also includes hard years. In 2017 and into 2018, internet shutdowns in Cameroon’s English-speaking regions cut the ecosystem off for months at a time. The community kept working — relocating, improvising connectivity, holding itself together — and that resilience is part of why the name Silicon Mountain commands the respect it does. Any honest account of building from Buea starts from both facts: the talent is real, and so are the constraints.

A tech company in Buea, building for public institutions

Most writing about tech ecosystems counts startups, funding rounds, and exits. There is a question about Silicon Mountain that almost nobody writes down, and it is the one that will decide what this ecosystem becomes: what does it mean to build systems for public institutions — registries, evidence platforms, procurement-integrity tooling — from Buea? That is the work we do, so this section is partial by construction; we think it is also the ecosystem’s most underrated possibility.

Start with talent. The ecosystem formed around the university, layered on a self-taught developer culture that goes back to the mid-2000s. Governed systems are not exotic to build; they are exacting. They need engineers who will treat an audit trail as a feature and a refusal as correct behaviour — and an ecosystem that taught itself to ship under internet shutdowns has already demonstrated the temperament that kind of engineering requires.

Then language. Cameroon’s constitution gives English and French the same status, and any system a public institution operates must ultimately work in both. Buea sits precisely at that hinge: an English-tradition university town in a constitutionally bilingual state. A team formed here does not treat the second language as an afterthought to be translated later — it lives in both. Our own declarant-facing work is designed to go further still, into Cameroonian Pidgin, because an obligation a citizen cannot read is not an obligation.

Then proximity. A governance system embodies hundreds of small decisions about how an institution actually works — who may approve, what must be logged, what happens when the power fails or the network does. Made from far away, those decisions get imagined; made from here, they get lived. Building from Buea means the constraints of the institutions served — and of the citizens they answer to — are the designer’s own daily constraints, not a persona in a slide deck. The landscape of that work, and the frameworks that govern it, are mapped in our govtech and regtech hubs.

SIGIL’s place, honestly

SIGIL SARL is a young company, and this page would be worth less if it pretended otherwise. We were founded in 2023 by Junior Thuram Nana and are registered in Buea (RCCM RC.BUA.2026.B.0190). From here we build three systems: VIGIL, a governed cybersecurity and evidence platform; RÉCOR, a sovereign beneficial-ownership registry designed for Cameroon; and APEX, anti-corruption intelligence for public procurement. All three are pre-deployment, and their source code is kept strictly private.

Pre-deployment means exactly what it says: SIGIL has no customers, no deployments, no pilots, no revenue, and no partnerships today. What we have is a verifiable record, kept with its limits stated. RÉCOR was fully demonstrated to, and acknowledged by, Open Ownership on 1 July 2026. This is a technical demonstration, not an endorsement. UNDP Cameroon issued a letter of appreciation in 2026; a letter of appreciation is neither an endorsement nor a contract. And APME, the Small and Medium Enterprises Promotion Agency, invited SIGIL to present to its digitalization unit in 2026. Each entry is listed in the record.

We do not claim to represent Silicon Mountain; no company does, and the ecosystem’s breadth is exactly its strength. Our claim is narrower: we are one demonstration that institutional-grade systems can be conceived, engineered, and proven from Buea. Who we are as a company is set out on the company page, and what building security from this town means in practice is set out on our Buea cybersecurity page.

What the ecosystem needs next

Everything above says the ecosystem has proven talent and proven resilience. What we believe it needs next — and this is offered as a contribution, not a critique of anyone — is the layer of practice that lets institutions place systems from Silicon Mountain at the centre of how they govern. Consumer products and institutional systems carry different burdens. A social app can apologize and patch; a registry, an evidence platform, or a procurement system holds decisions people must be able to defend years later, and it has to be built accordingly.

Three disciplines make up that layer. First, institutional-grade engineering practice: systems that fail closed rather than open, that keep tamper-evident records of every consequential action, and that separate what is proven from what is merely observed. Second, standards: where an open standard exists, build to it and export to it, so an institution’s data outlives any vendor — including us. Third, verifiability: write claims an evaluator can test against the system in front of them, not claims a reader has to take on faith. Our own working rule is one sentence — the institution holds the keys; the data stays under the institution’s control; every consequential action is authorized, bounded, and proven — and our attempt to hold ourselves to it is written down in our doctrine.

None of this belongs to one company. A shared engineering practice raises the value of every team’s word, the way the conference and the hubs raised the ecosystem’s visibility a decade ago. If Silicon Mountain adds verifiability to its virtues — if “built in Buea” comes to mean built to be checked — then the ecosystem that taught itself to ship through shutdowns will have taught itself something rarer: how to be trusted with institutions. What that infrastructure looks like in full is mapped under sovereign governance infrastructure and governed cybersecurity.

Frequently asked

Request a briefing →

Related reading