One rule, one alert, and the reason attached
Push, desktop, mobile or webhook. A squawk fires when a live condition crosses a line you drew, and arrives carrying the evidence, so you are not alt-tabbing to work out why it went off.
- Radar matches crossing your score floor
- Copied-wave spikes and coordinated posting
- Halt and resume events, with the reopening print
- Filings that hit EDGAR before the newswire
An alert without its reason is noise
Every squawk carries the evidence that triggered it: the preconditions met, the cluster share, the halt code, the filing link. The point is to let you decide without going to look, because the four minutes spent looking is usually the whole trade.
EDGAR direct, not the wire
We watch the filing feed rather than waiting for a newswire to reprint it. In our episode set the gap runs to tens of minutes on 8-Ks, which on a low float is the difference between the move and the receipt.
Webhooks make it programmable
Any squawk can POST to your own endpoint, so the same rule that pings your phone can trigger an agent, write to a sheet, or post into your desk's channel with the reasoning attached.
The founding cohort is 1,000 seats.
We admit 1,000 traders at a time because that is the largest number whose feedback on radar accuracy we can actually work through before opening the next batch. Applications are admitted in order; the intake asks what you trade, and answering it moves you up.
No card at application. Founding price locked for the life of your account. The full intake asks what you trade and moves you up the queue.
Admitted in order of application · momentum traders who complete the intake go first · founding price locked for the life of your account