Every operations team I've worked with — supply-chain at a freight forwarder, SOC at an energy operator, breaking-news desk at a wire service — has the same problem. They are drowning in feeds.
USGS for earthquakes. NOAA for hurricanes. FIRMS for fires. GDELT for global news. ReliefWeb for humanitarian crises. NWS for severe weather. AIS for vessels. OpenSky for aircraft. Each one in a different format, on a different cadence, with a different idea of severity. The analyst's job is to merge all of that into a single picture of “what is happening within 50km of our stuff right now.”
That job — the unglamorous, expensive, easy-to-screw-up job of merging feeds and firing the right alert — is what Augur does.
The shape of the product
You draw a polygon (or a circle) on a map. You wire a Slack channel. You pick a severity threshold. Augur fires an alert the moment a matching event hits the public feeds, with a one-paragraph LLM-generated explainer so the on-call lead doesn't need to read three Wikipedia tabs to know whether this is a big deal.
That's the entire pitch. Everything else — the public API, the embeddable maps, the dwell-time alarms for AIS vessels, the AI alert triage — is downstream of that one core loop.
Why now
Two things changed. First, the cost of running an LLM cheaply enough to attach one to every alert dropped 50x in 18 months. Second, the OSINT feed landscape consolidated — the dozen useful public feeds are now stable, well-documented APIs we can rely on. The unit economics work for the first time.
If you operate something — a refinery, a port, a foreign-news desk, a pipeline corridor — and you've been told “we should really be monitoring OSINT signals” for three years but haven't had the headcount to wire it together, that's who we built this for. Hit the demo.