
Overview
Meridian sits in front of a site and decides, request by request, whether it is talking to a person or a bot. It terminates TLS, fingerprints the client, scores it, and passes, challenges or blocks.
Challenges are proof of work: the browser does a little computation instead of a person solving a puzzle. New protection can run in shadow mode first, counting what it would have stopped before it enforces.
Every request is kept as time series, so a site owner can look at an hour or a month and open any single request to see why it was decided the way it was.
What we built
Gateway
A Go reverse proxy that terminates TLS, fingerprints clients and decides every request.
Challenges
Proof of work the browser solves on its own, harder when a client looks suspicious.
Rules and bans
Rules, bans and rate limits per site, with a history of every change.
Shadow mode
Protection that watches without enforcing, counting what it would have stopped.
Simulation
Replay a new rule against past traffic before turning it on.
Alerts and webhooks
Thresholds that notify by email, Slack or signed webhooks.
Screens





Stack
- Gateway
- Go
- Dashboard
- React and TypeScript
- Storage
- Postgres with TimescaleDB
- Hosting
- DigitalOcean, behind a Cloudflare tunnel
