Pick one sharp pain on your block. Ship a working tool for it in weeks. Use the tool to build trust, capacity, and self-governance. Rotate to the next pain when the first one is handled. That is the whole idea.
Most civic software tries to do everything for everyone. It ends up doing nothing for anyone.
neighborhoodOS goes the other way. We start with one concrete pain in one real neighborhood and ship a working tool for it in weeks, not quarters. When the tool earns trust, we keep it running and pick the next pain.
West Waldo, Kansas City, Missouri. Owner-occupied homes only. No rentals. No landlords.
Once a month, a group of neighbors picks one homeowner who cannot afford to fix their own house, and we go fix one thing. Roof patch. Porch rebuild. Storm-door replacement. Gutter haul. Whatever the house actually needs, picked from a list the homeowner helped write.
This is closer to a Habitat for Humanity work day than a tech product. Habitat builds new houses with volunteers and donated materials. We do the same thing, but for the houses that already exist on our blocks, and we do it every month, on the same Saturday, so people can plan around it.
Neighbors with hands. Some are tradespeople, retired or working. Most are not. The retired plumber leads a plumbing day. The carpenter leads a porch day. Everyone else hauls, scrapes, paints, holds the ladder, brings food.
Lives in the house. Owns the house. Cannot afford to pay for the fix. Picks the project from a short list scoped to what we can finish in one day. Is on site, makes the call on what gets done, gets thanked at the end.
Matches the next house to the next Saturday. Tracks who said they could come and what skill they bring. Builds a supplies list from the project type. Records what got done and what is still on the list for next month.
Keeps a record of every house we have visited and every fix we have made. So a year from now, we know which roofs we patched, which porches still need a railing, and which neighbors said yes the first time.
If those numbers do not show up at 90 days, we rotate the wedge. The platform stays, the wedge changes. No shame.
All code is open source. MIT licensed. Runs locally on one neighborhood node. No central server.
core/ node entry, shared wiring
connectors/ city data, social signals
ingest/ cron-ready scripts
identity/ trust levels, voting
wedges/ the swappable part
site/ this page
git clone
cd neighborhoodos
npm install
cd wedges/home-maintenance
node fetch-all.js
node ingest-all.js
Mirrored on GitHub and Codeberg. Issues welcome. Expect breaking changes weekly until v1.
One person, in one neighborhood, right now. Simon L. Paige in West Waldo, KCMO. Runs a small web design business and a few other things by day. This is where the rest of the energy goes.
If the pilot works, this becomes a real thing with real governance. Until then, it is a kitchen-table project you can watch and contribute to.