NEWWhat November 3 showed. Registration isn’t turnout. Read it →Sign in
The platform

Built to be checked, not trusted.

A dashboard that lies is worse than no dashboard, because you act on it. Here’s how Red Glare is built so its numbers hold up.

Build 12974,830 tests · passingLive
consent floor holds on resume
an import never widens reach
held reasons sum to the sentence
quiet hours per recipient
STOP holds on every line
walk link fenced to one street
a knock uploaded twice is one knock
the map count equals the send
0tests every build
0browser suites
0security checks
0failing
Tests check promises, not spelling.
How a number reaches a screen

Four rules between the data and you.

THE QUERYEvery number is one

Nothing on a screen is typed in or cached as a guess.

THE SOURCEKept with it

County file, a model, or a person, in separate columns.

THE SUMHas to balance

Drawn plus every named gap equals held.

THE SCREENSays what it can’t

A figure that can’t be computed says so, never a zero.

46screens
249API routes
70database tables
4,830automated tests on every build
48browser test suites
How it’s built

Plain parts, on purpose.

Readable all the way down

Every query is readable SQL, and an account is a database a person can back up, inspect and restore.

What happened, kept apart

What the county said, what a model guessed and what a person reported are separate columns.

One authority on opt-outs

The suppression list decides who’s reachable. An import can only make somebody less reachable.

Fast, and held to it

Every request records what it cost. Speed is a rule in the test suite.

Tested as promises

Tests check what the product promises, not how it’s spelled.

Penetration tested

A 51-check suite against every page volunteers open without a login.

Find them. Reach them. Get them to vote.

Thirty minutes with someone who has run a ground game. Bring your voter file.