Doc-Assure

The sovereignty fund

A country whose records live on foreign infrastructure is a tenant on someone else's land — and a tenant can be evicted, audited, or overruled by a landlord in another jurisdiction. Most “African cloud” is foreign infrastructure wearing local branding. This fund pays the rent on servers that are African in law as well as in location, so those countries' records can come home — one region at a time.

“So let us not look north. Let us look west and let us look east and let us be determined always to remove the middle man, to remove the middle leg, and to remove the middle passage.”
“Many hands make light work… we must be prepared to share the bounty that can allow our people always to aspire and to feel that they live as owners in their own country and not tenants in the land.”

Prime Minister Mia Amor Mottley of Barbados, at Ghana's 65th Independence celebrations, Cape Coast, 6 March 2022. This fund is inspired by that speech. It is not affiliated with, endorsed by, or connected to the Prime Minister, the Government of Barbados, or CARICOM.

Reparations are usually framed as a debt owed by the states that profited. That claim is being pursued, and it should be. This fund does something alongside it: anyone who recognises that the repair is necessary can act now, in their own way, without waiting for a government to agree.

What your contribution buys is not a metaphor. It is the monthly rent on a physical server in an African country. Today a Ghanaian record travels to a foreign datacentre and back; a server in Accra ends that journey. That is the middleman, and it is removable.

You receive nothing in return. No storage, no discount, no service — only your name on the region you helped fund, if you want it there. What you can do, which almost no fund allows, is check: every region publishes a signed, public attestation of the records it holds, so you can verify the thing you paid for exists without taking our word for it.

A server on African soil is not automatically under African law

The US CLOUD Act (2018) lets American authorities compel any provider subject to United States jurisdiction to produce data it controls — no matter which country stores it. Not the country's courts. Not a treaty request the host government could refuse. A subpoena, served in America, reaching a machine in Africa.

And it does not stop at ownership. A US parent with an African subsidiary is the obvious case. The harder one is the arrangement now being built across the continent: an African-owned group partners with a US hyperscaler, installs that hyperscaler's platform in a local datacentre, and sells it under an African name. The building is African. The brand is African. The founders are African. But the software, the control plane, the support tooling and often the encryption keys belong to a company that answers to Washington — and it is control, not geography, that the CLOUD Act follows.

And “it is local” almost always describes one copy — the primary. A provider can tell you, truthfully, that your records are stored in Johannesburg, while its nightly backups replicate to Dublin, its failover region sits in Frankfurt, and a support engineer pulls a diagnostic export to a ticket system in California. Every one of those is a complete copy of your data, in a jurisdiction you never chose and were never told about. Residency promises are usually written about where the primary lives; the copies are where data actually leaves.

This is the narrative being sold as African digital sovereignty right now, and it is the reason a map pin proves nothing. Ask any provider four questions: who owns the company that operates the machine; whose software runs the control plane and who can push changes to it; who holds the encryption keys; and where every copy lives — backups, replicas, disaster recovery, failover, snapshots and support exports, each named separately, because a promise about “your data” is not a promise about your backups. If any answer points outside the continent, the data is African by address only.

Our certificate commits to the opposite, in writing and in the customer's hands: no copy — backups, replicas, disaster recovery or failover — leaves the country. That is why a region here costs what it costs. Keeping the second copy in-country is more expensive than shipping it to Europe, and it is the whole point. We put that question to our Burkina Faso provider before committing to anything; the answer was that backups stay in Burkina Faso, and we are moving it from the sales thread into the contract, because a verbal assurance is not a residency guarantee either.

Doc-Assure is operated by Manergy Consulting (Pty) Ltd, a South African company. It is not a subsidiary, licensee, or reseller of a United States or European platform, and it is not subject to the CLOUD Act. Our answer to the third question is the strongest one available: every stored document is encrypted with keys that never leave our own infrastructure, so the hosting provider — whoever they are, whatever flag they fly — holds ciphertext they cannot read, and a subpoena served on them produces nothing legible.

Our own answer, since we are asking you to interrogate everyone else's. AI chat over your documents now runs on models on machines we own — it was switched off for months rather than run on a foreign model, and it returned only when generation moved onto our own GPUs. The features still awaiting that move — AI reports and legal analysis — remain switched off rather than run abroad. Storage, text extraction, image understanding, indexing and search run on machines we own.

Filing no longer crosses a border. It used to: every document sent its opening characters to a third-party model to decide which retention category it belonged to. That path is shut. Filing now matches a document against categories held on our own machines, and anything the sovereign classifier is not confident about waits for a person rather than a foreign API. We would rather show you an uncategorised document than quietly ship it abroad to earn a label.

Uploading no longer crosses either. Every upload used to send a document's opening characters abroad to have a summary written for it — automatically, whether you asked or not. That is held too, along with document summaries, comment summaries, compliance analysis and the language-understanding step in search. Search itself is untouched: your words are matched against our own index instead. What remains is the whole product minus the sentences a foreign model used to write for us.

Regions

Loading…

Contributions are made to Manergy Consulting (Pty) Ltd, trading as Doc-Assure. They are a contribution, not a tax-deductible donation — we are not a registered public benefit organisation. Every rand pledged goes to the named region's infrastructure, and the fund publishes what came in and what it paid for.