Three tiers. All transparent. All attributed.
Whether you're an attorney offering one template review, a 501(c)(3) underwriting accountability mailings for a ZIP code, or a neighborhood deploying its own federated node — there's a defined relationship and a defined recognition.
- Review one protocol, page, or template in your field
- Your name + credentials appear at the top of the page you reviewed
- Listed on the advisory page by cluster
- No commitment beyond the one review
- Citation-ready attribution if the project produces research output
- Underwrite Lob API mailings, custom resource imports, or translation work for a defined ZIP
- Your organization is the legal sender of any mail (we are word-processing software, not a political actor)
- Logo and one-line description on the partner ribbon of pages serving your ZIP
- Quarterly aggregate report on usage and outcomes for your sponsored area
- Optional: branded landing card for residents in your sponsored ZIP
- Deploy your own Cloudflare Worker + D1 + Netlify stack from the public spec
- You own all raw data — only anonymized weekly aggregates flow upstream
- Listed in the public node directory; cross-node coordination enabled
- Inherit civic.json templates from state/county defaults; override locally
- License-bound to federate — see
LICENSEfor terms
Current sponsors
As 501(c)(3)s and foundations come on board, they'll appear here.
Federated nodes
Public directory of active nodes.
Sponsorship inquiry
Tell us your organization, your ZIP focus, and the scale you're considering. We'll respond within 5 business days.
Common questions
Why don't you accept state or government funding?
Asking the government to fund infrastructure designed to hold it accountable compromises the infrastructure. We will accept partnership in the form of API whitelisting, data access, or formal endorsement — but not operating capital.
Who is the legal sender of accountability mail?
By default, the resident is. We generate a printable PDF; they print, sign, and mail it ($0.63 stamp). If a sponsor opts in to underwrite Lob API mailings, the sponsor's organization is the legal sender — using their own Lob API key, which they own and can revoke at any time. The platform is the word processor, not the political actor.
What data does the canonical server receive?
Anonymized weekly aggregates only: trigger counts by category, pledge counts (deduplicated by zero-knowledge nullifier), verification success rates, resolution outcomes when known. No names. No photos. No identifiers.
What happens to the code if the operator disappears?
The protocol specification is CC0 public domain — anyone can build a compatible implementation. The software is federation-required; if the current operator ceases maintenance, the federation continues and any node can continue operating its local instance.