Sometimes infrastructure decisions determine whether a mission can continue.

The email wasn't about a bug. It wasn't about performance, security, or even the product itself. It was about where the data lived. During a routine compliance audit, one question changed the entire conversation: "Can you confirm where citizen data is physically stored?" The answer was the United States. For a civic platform handling politically sensitive public data, that answer became a compliance issue overnight.
OpenBudget Ghana is a civic technology initiative based in Accra. Its platform helps citizens, journalists and civil society organizations explore public spending through interactive dashboards, making government budget data easier to understand and question. Built by a small team of two developers and a data analyst using Next.js, PostgreSQL and Redis, the project had one clear goal: improve transparency through accessible technology.
For years, the platform ran on a well-known international cloud provider. Technically, everything worked. The application was stable, deployments were straightforward and users never noticed where the servers were located. The donors did. The donor flagged data residency as a potential risk and gave the team three weeks to migrate to infrastructure that aligned with its funding requirements. Without a compliant hosting environment, the grant supporting the project could be suspended.
"Suddenly, infrastructure was no longer an engineering decision. It was an organizational one."
The team needed a platform that offered regional data residency, encrypted managed databases, documented service guarantees and an audit trail that could satisfy future reviews — not months later, but before the deadline. The migration turned out to be far less complicated than expected.
The application was redeployed directly from Git, while a managed PostgreSQL instance was provisioned with automated backups and encryption at rest. HTTPS was enforced across every endpoint with automatically renewed SSL certificates, and the organization completed local identity verification for team accounts as part of its governance process.
Four hours after the migration began, the platform was fully operational on its new infrastructure. Eighteen days after receiving the audit findings, the organization submitted updated compliance documentation to the donor. The grant was renewed.
For Kwame, the lesson was simple. Infrastructure doesn't just support applications. Sometimes, it protects the mission behind them. Today, OpenBudget Ghana operates on infrastructure designed to meet both technical and governance requirements — and a documented uptime SLA is now included in every future donor audit package.
Fun fact: OpenBudget Ghana's migration took four hours — but the compliance report it enabled took eighteen days to write. Infrastructure wasn't the bottleneck. Paperwork was.
We spent years thinking about transparency for public institutions. The audit reminded us that our own infrastructure had to be just as transparent.

Join the builders across Africa who ship faster with Qeda.