For cities.
Public works · Constituent services · Budget offices
The citizen app stays free forever. That is a covenant. The city-side dashboard — where the reports land, the contractors get tracked, and the budget meetings get their numbers — is where Fault Line sustains itself. If you run a public works department in New England, this page is for you.
Who this page is for: DPW directors, constituent services / 311 managers, city council staffers who prep the annual road-repair budget ask, and grants managers assembling infrastructure funding applications. If you're any of the above and you want a call, jump to the demo request at the bottom of this page.
1. What your city gets
📥 Real-time report intake
Every Fault Line report inside your jurisdiction lands in a dashboard your team can triage. GPS, photos, category, community-verification count, deduplication against your existing tickets.
🔗 Open311 in & out
Bidirectional sync with your existing 311 or work-order system (SeeClickFix, CivicPlus, custom Open311 endpoints). Fault Line reports become tickets in your system; status updates flow back to residents automatically.
🏗️ Contractor performance data
Recurrence tracking on every "closed" work order. When the same GPS reopens 90 days after a contractor signed off, that pattern goes into a contractor scorecard you can pull into procurement review.
📊 Budget-meeting exports
One-click PDF and CSV exports of open backlog, severity distribution, and neighborhood-level report density. Formatted for council packets and grant applications, not for engineers.
🔮 Pre-deployment reports
Designed to flag where damage is likely before pothole season based on seasonal patterns, deterioration curves, and historical density. Intended to make winter/spring pre-deployment routing defensible.
🏛️ Resident-facing city page
An embeddable public page at fault-line.dev/city/[yours] showing your live grade (once above the data threshold), methodology, response-time trend, and the current backlog. Journalists and residents both land here.
2. What your city does not get
- Editorial control over grades. The Shame Index is computed from the published methodology. Cities can dispute inputs and get corrections applied — but not change the grade for the grade's sake.
- Reporter identities. Anonymous reports stay anonymous, forever. Even a subpoena directed at Fault Line finds no PII to hand over, by design.
- The ability to hide backlog. The public dashboard shows what residents already know from their own commutes. We don't offer a private-only tier.
Those three constraints are the reason Fault Line is trusted by residents. They're also the reason the city-side product has any value at all — a rubber-stamp app doesn't move behavior.
3. Pilot pricing
The current posture is honest: Fault Line is in beta, no city has a live grade yet, and the citizen app is running on solo-maintainer infrastructure. Pilot pricing reflects that. Real pricing gets set when there are enough pilot cities to know what the value actually looks like.
| Tier | Who it's for | What's included | Cost during pilot |
|---|---|---|---|
| Pilot city (MA / RI / NH, through Q1 2027) |
Public works departments serving < 250k residents who want to shape the product. | Intake dashboard, Open311 sync, contractor scorecard, monthly budget-export bundle. Direct line to the maintainer. | $0 |
| Mid-market | Cities 250k–1M residents. | Everything above plus quarterly pre-deployment predictive report + dedicated staging environment. | Pilot-pricing conversation Target: covers infra + review time. |
| Major metro | Cities > 1M residents, or state-level DOT offices. | Custom scope. Multi-department dashboards, historical dataset import, on-site kickoff. | Custom |
In exchange, pilot cities get: a named product contact, a written commitment on which methodology version their grade is computed under (so grades don't change out from under a council packet), and a two-week notice before any price changes.
4. Why buy this instead of building it
- Residents already use it. The reporting pipeline exists and is running. Your existing 311 has been asking for behavior change from residents for a decade. Fault Line already changed the behavior.
- Open311 in-and-out means no migration. Reports become tickets in the system you already have. Your work-order flow doesn't change. Your staff doesn't learn a new tool. The dashboard is a read layer.
- Contractor recurrence data is otherwise inaccessible. Nobody else is systematically tracking when a "fixed" pothole reopens 90 days later at the same GPS. That signal is worth the pilot alone.
- Grant-application material. The exports are formatted for the ask — density maps, severity distributions, cost projections. If your city is applying for federal infrastructure funding, these are the tables that go in the application.
5. Frequently asked
Is our resident data being sold?
No. Anonymous reports carry no PII. Signed-in reports carry the reporter's email (used for status updates back to them) and nothing else. There is no ad-tech or data-broker pipeline on the resident side.
If we're a pilot, can we lock in the pricing?
Pilot cities in MA/RI/NH get $0 through the end of Q1 2027 in writing. Beyond that, pilot cities get 60 days written notice of any pricing change and the option to continue at the pilot rate for one renewal cycle.
What happens to our data if we leave?
You get a one-time export of all reports, tickets, and analytics your city generated, in CSV and JSON. Public-facing report threads remain visible on Fault Line (residents filed them) but the city dashboard access ends on the last day of the term.
Can we get a grade even if the resident volume is low?
Grades only publish once a city clears the minimum-data threshold. This is deliberate: a below-threshold grade is worse than no grade for everyone. Pilot cities that clear the threshold get their grade with a lead-time preview so nothing surprises the council.
Is this replacing our 311?
No. It sits on top. Cities that have gotten value from Fault Line have kept their 311 and used Fault Line for the parts 311 doesn't do well — de-duplication, community verification, and public-accountability data.
Who runs Fault Line?
Moonlit Social Labs — Michael Wylde, solo. That is the honest state. It is also why pilot pricing is what it is, and why the citizen app will never carry a paywall. See About.
Request a demo
Public works directors, constituent services managers, and council staffers: send one line about your city and its current 311 setup. I'll follow up with a scoped demo — no sales rep, no CRM sequence.
Request a demo → Or email directlyResponse within 2 business days · No sales rep · One person, one inbox.
Not legal or financial procurement advice
Any procurement decision is yours and your city attorney's. Pricing described above is a good-faith description of the current pilot posture, not a binding contract. A binding term sheet is issued only after a demo conversation and a signed pilot agreement.