A county-deployable counter-UAS (C-UAS) detection, incident-coordination, and national-federation platform built for critical infrastructure protection and crowded-event security.
This is the public companion repository for EagleEye. It exists so federal partners, congressional offices, sector ISACs, and prospective evaluators can read about what the platform does, who built it, and how to engage — without us having to expose the production source code or operational tuning.
The implementation lives in a controlled private repository. Evaluation access is granted under the model described below.
Posture. EagleEye is detection and awareness only. Mitigation authority over unmanned aircraft systems is reserved to DHS, DOJ, DoD, and DOE under the Preventing Emerging Threats Act of 2018 and the FAA Reauthorization Act of 2018. The platform's role is to be a disciplined, auditable talker that vectors federal partners — never to act outside SLTT statutory authority.
The United States has spent billions of dollars on federal radar, airspace surveillance, and counter-UAS sensor infrastructure. None of it currently flows to the county sheriffs, EMA directors, water districts, electrical cooperatives, hospitals, schools, and houses of worship that have to act when a drone shows up over a substation, a parade route, or a stadium full of people.
The reverse is also true: when a county sensor sees a recurring overflight pattern, there is no clean path for that signal to surface nationally through DHS-coordinated channels in seconds rather than days.
EagleEye is the platform that closes both gaps:
- Sensor-agnostic ingest — one webhook accepts detections from FAA RemoteID, DJI Aeroscope, DroneShield, Dedrone, Echodyne radar, 5G passive coherent location, acoustic, optical, and manual operator reports
- Geofence-based threat scoring — protected critical-infrastructure polygons, time-windowed event geofences, and TFR-style temporary restrictions are evaluated against every detection
- Voice-ready operator briefings — distance + cardinal bearing + altitude + heading + speed + ETA-into-polygon, formatted so a dispatcher can read it straight into a radio: "DJI Mavic 3, 780m N of [protected asset], alt 60m, heading 000° at 55kph, ETA inside ~51s"
- Federation outbound — escalated incidents and high-confidence detections fan out to authorized peer systems (state fusion centers, neighboring jurisdictions, DHS-coordinated endpoints) with a complete audit trail
- Sync inbound — protected-asset, event, and TFR geofences sync to deployed edge devices in near-real-time via a WebSocket push channel
- Working backend (FastAPI / Python 3.11+ / SQLAlchemy 2.x / SQLite or Postgres)
- Working frontend (Leaflet single-page dashboard with PPI radar sweep)
- 125 automated tests passing in continuous integration
- Architecture diagrams maintained
| Capability | Description | | Source-agnostic detection ingest | Single REST endpoint normalizes detections from any vendor or modality | | Source modalities supported | RemoteID, Aeroscope, DroneShield, Dedrone, Echodyne, 5G PCL, acoustic, optical, ADS-B (context), manual | | Geofence model | Protected assets (CI), scheduled events, time-windowed temporary restrictions with issuer attribution and altitude floors/ceilings | | Threat scoring | Multi-rule heuristic across geofence proximity, RemoteID compliance, approach kinematics, swarm clustering, and multi-sensor agreement. Per-deployment tunable — exact constants intentionally not published | | Incident lifecycle | Auto-open on detections crossing elevated threshold; dedupe to existing open incidents within a window; escalation triggers federation outbound; closes with full timeline | | Operator vectoring | Distance, 16-point cardinal bearing, closure speed, ETA-into-polygon, voice-ready summary line per detection | | Live track display | WebSocket-fed Leaflet dashboard with rotating plane / drone markers, PPI radar sweep, threat-color overlay | | Edge device sync | Geofence revision tracking with delta endpoints and a push channel; deployed sensors stay current without polling | | Federation outbound | PeerFeed registry with subscription filters, severity floors, bearer/basic auth; FederationEvent audit log with retry | | Federal contact integration | Built-in escalation contact list (template only in public artifacts; populated only in controlled deployments) | | Legal guardrails | Persistent operational banner enforcing detection-only posture; legal citation list bundled with the dashboard |
EagleEye is structured for a tiered evaluation model:
- Read this repository. Public artifacts: this README, the architecture overview, and the IP and partnership posture.
- Request a demonstration. A live, password-gated demonstration instance is available at eagleeye.fraudtrax.net (provisioning in progress) via Cloudflare Access. Email
codyrose@fraudtrax.netwith the email addresses you would like credentialed and the role they represent (federal evaluator, congressional staff, sector ISAC, partner). Access is granted per-user with full audit logging. - Request source-code evaluation. For technical evaluators (DHS S&T, CISA, federal innovation labs), read-only collaborator access on the private source repository is provisioned on request after demonstration. This step is for serious partnership conversations only.
- Discuss partnership. SDVOSB / SBIR / STTR / CRADA / OTA pathways are all open and appropriate for what EagleEye is and who built it.
| Channel | Use |
|---|---|
| codyrose@fraudtrax.net | Federal / private-sector partnership inquiries, demonstration access, security reports |
For specifically time-sensitive matters, telephone contact is available on request.
This repository contains:
- This README and its links
- High-level architecture overview (ARCHITECTURE.md)
- IP and partnership posture (LEGAL.md)
This repository deliberately does not contain:
- Source code
- Threat-scoring weights, kinematic thresholds, or any operational tuning constants
- Specific protected-asset polygons or any deployed-site identifying information
- Federal contact details (use the controlled deployments for those)
- Sensor integration contract specifics (vendors integrate under controlled access)
That separation is deliberate. The public side establishes credibility and capability; the private side preserves the operational moat.
EagleEye — built by a veteran, this is built to serve this nation, not to profit from it.
© 2026 CCR Capital. All rights reserved.
EagleEye is developed under the Omega Point Solutions umbrella — an applied-AI and public-safety technology company built by law enforcement and intelligence veterans.
Suite products: FraudTrax · SVT — Stolen Vehicle Tracking · Hatchet Trace · County EMA Operations Map · EagleEye