Bio-OSINT
Method

How a public detection becomes your problem, on time.

Four stages between a state veterinarian publishing a confirmation and your procurement lead knowing which farms to call. Nothing here is proprietary data — the work is in the correlation and the speed.

Onboarding Days, once
Detection to alert Within the hour
Risk note Weekly
01

Your supplier list becomes coordinates

You send the farms and facilities you actually buy from, in whatever form you keep them — a spreadsheet, a purchase-order export, a list in an email. We geocode each site, resolve the ones with ambiguous or shared names, and send the resolved list back for your sign-off.

This is the step nobody else does, and it's why we do it by hand: a proximity system built on a wrong pin is worse than no system.

Hollis Ridge Farm 35.0412, −77.9163
Trent Valley Layer 35.1877, −77.6021
Kinsey Broiler #2 2 matches — confirm
Ambiguities come back to you, never guessed.
02

We monitor the public record continuously

Federal confirmations, state quarantine and control-zone orders, wild-bird surveillance sampling, and human-case reporting all publish on different schedules and in different shapes. We normalise them into one event stream with a location, a date, a flock type, and a source citation.

Every alert we send carries the citation, so your team can verify it against the primary source in one click.

USDA APHIS Confirmed detections
State ag departments Zone & movement orders
Wild bird surveillance Flyway sampling
CDC Spillover & human cases
03

Proximity correlation against your standoff radius

Each new event is measured against every one of your sites. You choose the radius that matters — most operators run a 10-mile watch and a 3-mile escalation, roughly matching the control-zone conventions regulators use.

County boundaries are noise: a detection can be 40 miles from your farm in the same county, or 3 miles away across a state line. We measure distance, not jurisdiction.

10 mi
3 mi
Your site
4.2 mi — alert
13 mi — logged only
04

An analyst writes the procurement read

The alert is automatic; the interpretation isn't. Every breach gets a short human note: which of your sites are exposed, what share of weekly volume that represents, what the state order is likely to do next, and what we'd do about it this week.

While the cohort is small, that's a person who knows your supply chain. As the pipeline matures, the routine parts move into the dashboard and the analyst stays for the judgement calls.

Immediate Proximity alert, with citation — within the hour of publication
Same day Exposure summary — sites in range, volume at risk, likely zone duration
Weekly Procurement-risk note across your whole supplier base
What we don't do

We're a reading of the public record, not an authority on it.

We don't test flocks, diagnose, or confirm detections ourselves.
We don't issue regulatory guidance or replace your state veterinarian.
We don't share your supplier list, ever — NDA before onboarding.
Photo placeholder
Analyst workspace or surveillance map

Run the method against your last 30 days.

Send us your supplier list under NDA and we'll show you every alert you would have received last month — with the distances, the citations, and the volume exposure. Thirty minutes, no obligation.

Request a briefing Back to overview
What we'll need
01Farm and facility names you buy from
02Rough weekly volume by site, if you have it
03Who should receive alerts, and how fast
A spreadsheet is fine. Most lists take us under a day to resolve.