Civic Technology
Technology in service of the public good
Government serves everyone. The technology that powers it should be open, accessible, and built with the people who use it. We build civic tools that work for real communities.
Why Civic Tech Matters Now
Public institutions are at a turning point.
Governments at every level are adopting new technologies faster than they can evaluate them. AI is making decisions about benefits, permitting, and public safety. Data systems built decades ago still power critical services. And the gap between what technology can do and what public institutions actually deploy keeps growing.
Civic technology is not about making government more like a startup. It is about building tools that are worthy of the public trust they require. That means open code, transparent processes, and design that starts with the most underserved users.
What We Are Working On
Five areas where technology can serve the public good.
Open Data
Making public data truly public. Standardized formats, accessible APIs, documentation, and tools that help citizens and organizations use government data effectively.
Digital Public Services
Government services that work on a phone, in plain language, and without requiring a visit to a physical office. Accessibility-first design for public-facing systems.
Participatory Governance
Tools that make it easier for residents to participate in local decision-making. Budget input, community feedback, and transparent planning processes.
Smart City Infrastructure
Sensor networks, environmental monitoring, traffic systems, and utility management that are open, interoperable, and controlled by the public - not vendors.
AI in Public Services
Responsible deployment of AI in government. Auditable models, bias testing, human oversight, and clear documentation of how automated decisions are made.
Our Principles
Non-negotiable commitments that guide every civic tech project.
1
Open by Default
All code is open source. All data is published in open formats. Closed is the exception that requires justification, not the default.
2
Designed With, Not For
The people affected by a system have a seat at the design table. User research is not optional. Community input shapes the product.
3
Privacy as Infrastructure
Privacy is not a feature toggle. It is a structural requirement built into every layer of the system, from data collection to storage to access control.
4
Interoperability
Systems must talk to each other. We use open standards, documented APIs, and avoid vendor lock-in so public infrastructure remains publicly controlled.
5
Document Failures
When something does not work, we publish what happened and why. Failures are expensive. Repeating them because nobody documented the first one is unforgivable.
Cleveland as a Testbed
A mid-size city with the infrastructure to pilot civic technology at scale.
Cleveland is the right size for this work. Large enough to have complex, real-world civic infrastructure challenges. Small enough that you can talk to the people who run the systems and the people who use them. The feedback loops are tight, the problems are real, and the results are measurable.
What works in Cleveland can be replicated across mid-size cities nationwide. The challenges facing this region - aging infrastructure, digital equity gaps, workforce transitions - are not unique. The solutions we build here are designed to travel.
Build With Us
We are always looking for collaborators - technologists, public servants, community organizers, and anyone who believes government technology can be better.