💡 Community-powered disease and pest proximity alert network for apiary biosecurity

[github-actions[bot]]

Summary

Aggregate state apiary inspector reports, privacy-preserving user-submitted disease sightings (American Foulbrood, European Foulbrood, Nosema, small hive beetle), and confirmed pest reports into a proximity alert system. Beekeepers receive push notifications when confirmed outbreaks are reported within a configurable radius of their apiaries. Models the proven UK BeeBase 3km notification approach for the US market, extending well beyond the hornet-only scope of existing idea #88 to cover the full spectrum of transmissible bee diseases.

Market Signal

Beentry (Czech Republic, used in 30+ countries) already offers automatic disease outbreak alerts near user apiaries — validating the concept commercially. UK BeeBase operates a mature proximity notification system alerting beekeepers within 3km of confirmed AFB outbreaks — proving the model at government scale. AFB reporting is legally required in 45 US states, creating a latent data source. Colony losses remain at 39.9% (2025-26 survey) with disease as a primary driver. VarroaVault has deep varroa management but no proximity alerting for transmissible diseases. State inspection programs in Florida, Montana, Ohio, and others mandate beekeeper registration, creating geographic databases that could feed alerts.

User Signal

Existing idea #88 covers yellow-legged hornet sighting reports only — a single invasive species. No existing idea addresses proximity alerts for American Foulbrood (the most devastating transmissible bee disease), European Foulbrood, Nosema, or small hive beetle — threats that are far more common and impactful in most US regions than invasive hornets. The PRD's proactive environmental hazard alerts (#475) address pesticide drift, wildfire smoke, and weather but not biological disease threats from neighboring managed and feral colonies. AFB can devastate all apiaries within its spread radius — early warning is the most effective intervention.

Technical Opportunity

Privacy-preserving location sharing via grid-cell approximation (report within a ~1km grid cell, not exact coordinates). Community reporting flow with optional photo verification leveraging Broodly's existing camera and image analysis pipeline. State apiary inspection API integration where data is publicly accessible. Push notification infrastructure from idea #453 (agentic notifications). Location-based proximity queries using PostGIS extensions on the existing PostgreSQL 16 + pgvector database. The disease report data model is a natural extension of inspection observations.

Assessment

Dimension	Score	Rationale
Feasibility	med	Community reporting component is straightforward. State data integration is fragmented — availability varies wildly by state, from real-time APIs to paper-only records. Privacy-preserving location model requires careful design.
Impact	high	AFB can destroy an entire apiary and spread to neighbors. Early proximity warning is the most effective intervention. No US-focused beekeeping app offers this. Proven at scale by UK BeeBase.
Urgency	med	Disease threats are year-round but peak during active season (spring-fall). Building the community reporting network takes time — network effects require a critical mass of users. Can start with state data where available.

Adversarial Review

Strongest objection: State inspection data is fragmented, inconsistent, and often not publicly available. Low user adoption means sparse community reporting and useless alerts. False positives and potential gaming of anonymous reports create trust issues. You'll build a feature nobody can use because the data doesn't exist.

Rebuttal: Data availability is the strongest objection, and it's partially valid. However: (a) the user-reported component provides value independently of state data — community reports work even with incomplete geographic coverage, (b) Beentry validates the concept commercially in 30+ countries with similar data fragmentation challenges, (c) even incomplete coverage is actionable — if you know there's confirmed AFB 2 miles from your apiary, that's critical biosecurity intelligence regardless of data completeness elsewhere, (d) photo verification and confidence scoring via Broodly's existing AI image analysis pipeline mitigate false positive risk, (e) the phased approach (community reports first → state data integrations as they come online) manages scope while building network value. Start with the 10 states with the most accessible inspection data.

Suggested Next Step

Survey available state apiary inspection data sources for the top 10 US beekeeping states by managed colony count. Design the privacy-preserving grid-cell location model. Prototype the community disease reporting flow with structured observation fields and optional photo verification. Define the proximity alert radius configuration (default 5km with user override).

---

Generated by weekly feature ideation scan — 2026-08-31