AntiFlock

Open-source counter-surveillance for the networks you control.

Map your exposure. Verify your route. Gate sensitive actions.

Run the demo · Why it exists · Architecture · Contribute · Release status

_{Pre-alpha · The local simulation and dashboard work today. Host-level enforcement remains under active development.}

When the trusted path disappears, AntiFl0ck holds the action — records why, verifies the route recovered, and only then lets it through. Every step lands in a signed local audit log.

⭐ Star AntiFl0ck to follow the public build and help more privacy engineers find it.

Why AntiFl0ck exists

Your phone, laptop, accounts, VPN, Wi-Fi networks, and cloud services leave related metadata trails that move together — like a flock. Each product shows you one fragment. AntiFl0ck is an open attempt to reveal the whole path, label what is actually known, and let the operator decide what happens next.

The debate around Flock Safety and large-scale license-plate-reader (ALPR) networks made one problem impossible to ignore: surveillance infrastructure grows faster than ordinary people's ability to understand their own exposure. AntiFl0ck explores what the defensive side should look like.

AntiFl0ck is an independent open-source project. It is not affiliated with or endorsed by Flock Safety, and it does not interfere with third-party surveillance infrastructure.

What it does

Run the demo

Fully simulated coffee-shop scenario. Needs Docker and Node 24+; no VPN account or real data.

make dev

make lab

Then open http://127.0.0.1:4173 — username operator, token from .antiflock/dev.env. On Windows without make: npm run dev / npm run lab. Full guide: operator runbook.

Working today vs. open

The local, simulated slice is complete and sits behind a 10-gate release check (make verify). The real-world pieces are separate, later milestones — they are not claimed until proven.

Working today

• Coffee-shop simulation end-to-end, with five signed audit events
• Signed, hash-chained event and audit log (SQLite)
• Deterministic policy engine, findings, and signed expiring plans
• Secure-action gate + TypeScript SDK
• Endpoint enrollment bootstrap and mTLS device identity
• Linux route/interface observation; opt-in socket-table flow metadata (no packets or payloads)
• Read-only live mesh probes — Tailscale CLI and Headscale BYOK — via the durable agent queue
• Third-Eye dashboard
• Proposal-only Nano watchdog with audited program admission

Open engineering work

• Production enforcement and real packet-path integration
• Mobile (Android) enforcement beyond the reference state machine
• Provider lifecycle automation (key rotation, revocation) and broader platform collectors
• Independent security and privacy review

Details and hard boundaries: release status · OPEN decisions and release gates · Explore open work →

Architecture

Core is the brain — identity, events, policy, explanations — but it never sits in your traffic path. Each device keeps a local copy of the rules, so protection keeps working if Core goes offline.

flowchart LR
    A[Devices and providers] -->|Signed observations| B[AntiFl0ck Core]
    B --> C[Evidence and audit]
    B --> D[Third-Eye dashboard]
    B --> E[Policy engine]
    E -->|Signed expiring plan| F[Local agent]
    F --> G{Verify result}
    G -->|Success| H[Allow]
    G -->|Uncertain| I[Hold or roll back]

Deep dives: architecture · threat model · evidence model · enrolled-agent setup · Nano watchdog · all docs

Contributing

Help build the defensive layer surveillance technology never gave ordinary people. Five lanes:

• Observers — Linux/macOS/Windows/Android collectors, provider adapters
• Visualizers — topology, exposure maps, audit timelines (React)
• Policy builders — deterministic rules, secure-action integrations
• Researchers — metadata models, ALPR research, threat modeling
• Hardening engineers — signing, storage, privilege separation, testing

Start with CONTRIBUTING.md and the good first issues. Security and privacy changes begin with a short design note (ADR); how decisions get made is in GOVERNANCE.md.

Safety, security, and license

AntiFl0ck is pre-release defensive software. It does not provide anonymity, prove that surveillance is occurring, or replace a VPN. An AI may explain a finding, but it never makes the allow-or-block decision. Report vulnerabilities privately via SECURITY.md, never a public issue.

License: Apache-2.0. The AntiFl0ck name and eagle mark are project marks — see TRADEMARKS.md. AntiFl0ck is the public name; an earlier working title clashed with another project, so internal identifiers are still being migrated.