Foxborne documentation
Rebuild the failure.
Cite every line.
Everything you need to deploy Foxborne in your own network, bring in flight logs and companion evidence, and hand a review board a report it can check against the originals.
Three ways in
Every section
What Foxborne does, a first reconstruction, and a tour of the console.
Jets, drones and ground robots, and which part of each machine records which log.
Clocks, error bounds, evidence levels and what a report can claim.
Architecture, the three deployment modes, basemaps, updates and backups.
Import files, connect storage, and enroll the companion collector.
Flight logs, journals, MAVLink records and flight test recordings, field by field.
The incident workspace, from the first finding to the signed-off report.
Alerts, automations, webhooks, SIEM forwarding and exports. All opt-in.
Identity, roles, CUI marking, export control, the audit log and keys.
Thirteen deterministic rules, their thresholds and the exact wording each finding uses.
Record formats, PX4 parameters, statuses, limits and defaults, and the glossary.
What changed in each release, and how every rule version moved.
Latest releases
All release notesRSS- Foxborne 1.4.2September 10, 2026Parser fixes for PX4 v1.16 rover topics
- Foxborne 1.4.1Earlier releaseReceive log latency estimates from SYSTEM_TIME
- Foxborne 1.4.0Earlier releaseManual clock alignment from matching events
Running an evaluation? Send one incident you have already investigated, and the team rebuilds it on your data beside your current tools.
Request a pilot