Impact report · 2026

What happens when public data reaches people.

We measure success by community impact, not GitHub stars. Here's how the tools on CivicByte are being used — who's using them, what they've found, and what's changed.

Public records indexed
35M+
311 complaints, HPD violations, evictions, and school budgets — pulled from NYC Open Data, updated daily.
Addresses searchable
1.1M
Every residential and mixed-use address in the five boroughs is searchable across at least one tool.
NYC public schools
1,800+
Per-pupil spending, Title I, and PTA contributions — mapped and compared side-by-side.
Communities served
Free
No sign-ups. No paywalls. No tracking. Always.
Who uses this

Real people, real decisions.

Impact isn't a dashboard metric. It's the concrete things people do with the tools once they have them. A few examples.
P
A Bronx parentPre-lease research

Checked a building before signing.

Found 14 open HPD violations and three executed evictions in the prior 24 months. Kept looking. Saved a security deposit and a month of fighting to break a lease.

T
A PTA in QueensBudget advocacy

Asked where the money actually went.

Used the School Budget Tracker to compare Title I allocations at their school against similar ones in the district. Brought the printout to a community ed council meeting.

J
A local reporterAccountability journalism

Traced an LLC across 42 buildings.

Used Landlord Watch to map one portfolio's violation history. Story ran in a neighborhood paper; the office of the AG followed up a month later.

O
A tenant organizerCanvassing prep

Pre-canvassed a block with data.

Pulled every 311 heat complaint on a single block over the last two winters. Showed up at doors already knowing which apartments had been calling — and which ones had stopped.

L
A legal aid attorneyCase prep

Documented conditions for court.

Assembled a 24-month violation and 311 record for a client's holdover defense in under an hour. Would have taken days of portal hopping otherwise.

C
A community boardNeighborhood context

Brought facts to a land-use hearing.

Board members used the platform to build an overview of code violations on a proposed rezoning corridor. Testimony was specific instead of anecdotal.

In their words

What users tell us.

Parent · Queens
I spent two weeks looking for this data in PDFs before I found your tool. It took five seconds.
M. S.School Budget Tracker user
Tenant organizer · Brooklyn
Landlord Watch is how we decide which buildings to canvass first.
R. A.Housing advocacy org
Coverage

Where the tools have shown up.

A sampling of places — newsrooms, community forums, mutual aid channels — where CivicByte tools have been cited or shared.
Neighborhood press

"…one of the more useful civic tech projects to come out of NYC this year…"

Local news outlet · Feature on student-built tools

Tenant forums

"Shared in three tenant-organizing Discords the week we launched."

Platform metrics · Referral sources

Civic tech community

"Good example of usable open-data tooling, not another dashboard graveyard."

Civic tech newsletter · Weekly roundup

Milestones

The platform, year over year.

Q2 · 2026

Fifth tool live: 311 Complaint Lookup

35M+ records indexed, 100+ complaint types. Fills the last major address-level gap in the housing data stack.

Q1 · 2026

Eviction Records launched

All five boroughs, 100k+ executed marshal eviction records. Becomes the most-shared tool in tenant-organizing channels.

Q4 · 2025

Platform standards formalized

The four-standard review process goes live. First external submissions accepted into the directory.

Q3 · 2025

Landlord Watch & Building Report

Portfolio-level search on top of HPD violations. Tools start being cited in local reporting.

Q1 · 2025

NYC School Budget Tracker

The first CivicByte tool. Built in response to a PTA asking how to read their school's budget documents.

How we measure this.

We don't have, and don't want, user accounts. That means we measure carefully: server-side request counts (aggregate, non-identifying), referrer patterns (which tenant forums, newsrooms, and advocacy sites are sending traffic), and direct testimonials from people who email, open GitHub issues, or mention us publicly.

Numbers on this page are conservative — rounded down, excluding bots, and only counting sessions that completed at least one search. When a metric is directional rather than precise, we say so.