← THE INDEX · VULN RESEARCH
DropHawk
Autonomous source-to-exploit research. One rule: nothing gets reported unless a deterministic test could reproduce it.
What it is
DropHawk watches for ticket inventory appearing on primary and resale sources and pushes a notification to a phone within fifteen seconds of a drop. It runs entirely on self-hosted infrastructure with no third-party service in the path.
Why the latency target drives the architecture
Fifteen seconds is the whole design constraint. It rules out polling on a comfortable interval, rules out batch processing, and rules out a notification path that queues. The system is built around a message bus with workers polling adapters independently, so a slow or rate-limited source cannot delay delivery from a fast one.
Notification delivery goes through a self-hosted push service rather than email or a third-party API, because the last hop is where most alerting systems lose their time budget.
Stack
Rust backend with a TypeScript front end, PostgreSQL for state, Redis and a message bus for coordination, containerized with health checks and metrics, deployed via compose on a single host. Configuration is environment-driven with no credentials in the repository.
Status
Phase one. Infrastructure is scaffolded and the first source adapter is in progress. The interesting remaining work is adapter-level: each source has different rate limits, different inventory semantics, and different definitions of what counts as available.