The Quiet Rise of the Civic Stack
A new generation of civic technologists is building public-interest infrastructure outside government. The tools are modest. The ambition is not.
Something is shifting in the way people build technology for public life. For two decades the dominant model was straightforward: charities and social enterprises built apps on top of platforms they did not control, government commissioned digital services from large suppliers, and citizens used whatever they were given.
That model is now being supplemented, and in places replaced, by something less centralised. Call it the civic stack: a growing collection of open-source tools, shared data standards, and community-governed infrastructure built specifically for public-interest uses. It does not have a headquarters, a launch event, or a press strategy. It has GitHub repositories and Signal groups and people who show up.
From apps to infrastructure
The shift is partly technical and partly political. On the technical side, the maturation of open-source geospatial tools, the spread of lightweight data standards, and the availability of low-cost hosting have made it possible for small teams to build things that previously required enterprise procurement. A neighbourhood group can now run a participatory mapping project on infrastructure that a council IT department would have spent eighteen months specifying.
On the political side, a combination of austerity, procurement fatigue, and declining trust in large technology firms has created appetite for alternatives. When a local authority's community engagement platform is owned by a company that also sells facial recognition to police forces, the tension is not theoretical. People feel it.
The tools we use to organise our communities shape the communities we can organise.
The civic stack is not one thing. It includes mapping libraries, consultation platforms, federated social networks for neighbourhood use, open data portals, and shared authentication systems that let people move between services without creating a new account for each one. What unites these projects is not a particular technology choice but a set of commitments: open code, community governance, and infrastructure designed to be replicated rather than monopolised.
What is new
Community-built technology is not new. The cooperative movement has been building mutual infrastructure for over a century. What is new is the technical sophistication, the speed of replication, and the emerging pattern of mutual support between projects.
When a participatory budgeting tool built for a borough in Barcelona is adapted for use in Manchester and then Bologna, each deployment improves the shared codebase. The economics of open-source software have been doing this for decades. What makes the civic stack different is that the users are not individual consumers but collective actors: tenants' associations, mutual aid groups, local campaigns. The software is designed for solidarity, not for individual productivity.
Three developments are worth watching:
- Federated identity. Projects like the European Digital Identity Wallet initiative are creating infrastructure that lets people prove things about themselves without handing data to a platform. The civic stack is beginning to adopt these standards, making it possible to move between services without a corporate intermediary.
- Data trusts and cooperatives. Legal structures that give groups of people collective control over data about them. Still experimental, but moving from white papers to working prototypes, particularly in health research and environmental monitoring.
- Local-first architecture. A technical approach where data lives on the user's device and syncs peer-to-peer rather than sitting on a central server. This matters for the civic stack because it removes the hosting provider as a single point of control and failure.
The risk and the response
The civic stack faces two obvious risks. The first is fragmentation: a thousand incompatible local experiments that never achieve the scale needed to challenge platform dominance. The second is capture: well-resourced incumbents adopting the language of community ownership while retaining control of the underlying infrastructure.
Both risks are real. The response, so far, has been a quiet insistence on standards and governance. The projects that are succeeding are the ones that treat interoperability not as an afterthought but as the point. A civic stack that only works in one city is not a stack. It is a pilot.
Field Station will be tracking these developments. The question is not whether communities can build their own infrastructure. They can, and they are. The question is whether the institutions that currently hold the budgets and the mandates will notice, and whether they will help or get in the way.