+230 580 47608
Foxborne
Incident reconstruction

What the logs can prove, and what they cannot.

Foxborne reconstructs what happened when a drone, a ground robot or a jet-powered uncrewed aircraft fails. It takes the flight log, the companion computer journal, the ground receive records and the range files, puts them on one UTC timeline with the clock error of each source stated, and traces every line of the final report back to the file it came from. It runs inside your own network, and sends nothing out of it.

In Partnership with Dude Lemon LLC, USA

Talk to usfoxborne.com
  • PX4 flight logs, companion journals, ground receive logs, IRIG 106 Chapter 10 recordings and range records on one UTC timeline
  • A stated clock error for every source, and order unknown where the evidence cannot decide
  • Each finding names the rule, its version and the threshold that fired, so the same files give the same answer next month
  • Every original hashed with SHA-256 on arrival, stored write-once, under a hash-chained audit log
  • Runs in your own cloud account, your own data centre, or a network with no path out
ReadsPX4 flight logsCompanion journalsMAVLink receive logsIRIG 106 Chapter 10Range recordsCollector samples
Overview

What it does.

One timeline, honest about its error

Each source arrives on its own clock and lands on UTC with an error bound stated beside it. GPS time anchors the flight log, the companion computer’s clock is only trusted while it reports a synchronised source, and a ground log records when a packet arrived rather than when it was sent. Two events closer together than their combined error are marked order unknown instead of being put in an order the evidence cannot support.

Four words for how sure you are

Every statement is marked observed, correlated, hypothesis or unknown, so a reader can see the difference between a log line and an explanation. The rules report what they found; your engineer writes the conclusion, and the report keeps the two apart. No invented confidence score stands in for the evidence.

A report the other side can check

Exports carry the excerpt exactly as it appears in the source, with the file, the line or byte offset and the SHA-256 of that file, under your own marking. Anyone holding the original can verify each line. The limits of the evidence and the questions still open travel with the report instead of being left out of it.

Inside your own boundary

Foxborne deploys into your cloud account, your own servers or an air-gapped network. It reads logs and never commands a vehicle, there is no remote access path for anyone else, and a self-hosted install sends no telemetry, crash reports or licence checks. The AI models it uses run on an inference node inside your deployment, so nothing goes to a model provider.

What it covers

Three parts, one investigation.

Evidence and alignment

  • PX4 flight logs, companion journals and collector samples
  • Ground receive logs and range radar, telemetry and termination records
  • IRIG 106 Chapter 10 recordings read with their own setup record
  • SHA-256 on arrival, originals stored write-once
  • A stated error bound for every clock, and a limit on how far it will align
  • Stable event IDs, so the same file always gives the same references

Reconstruction and reporting

  • Rules for vibration, telemetry gaps, failsafes, memory pressure, device disconnects and GNSS jamming
  • Every finding stamped with the rule ID, version and threshold
  • Sortie closeout, failsafe evidence packs and repeat-fault detection
  • Marked PDF case files with exact excerpts and file hashes
  • Evidence bundles, originals with a checksum manifest, MCAP, Parquet, CSV, JSONL and MATLAB
  • Findings pushed to email, chat, ticketing and your log platform, at the data level you allow

Deployment and security

  • Your cloud account, your data centre, or air-gapped with signed update bundles
  • Single sign-on over SAML 2.0 or OIDC, with SCIM provisioning
  • Five fixed roles: admin, investigator, reviewer, viewer and auditor
  • A hash-chained audit log of every import, view, edit and export, streamed to your SIEM
  • Encryption with your own keys, and a marking banner your administrator sets
  • An optional vehicle collector that is outbound-only, read-only and redacts before upload
Four steps

How it works.

  1. 01

    Import

    Drop in the flight log, the journal export and whatever ground records you kept, or point Foxborne at the storage where they already land. Every original is hashed the moment it arrives.

  2. 02

    Align

    Each source is placed on UTC with its error bound stated. Anything that cannot be anchored to a trusted clock stays visibly separate instead of being quietly merged.

  3. 03

    Reconstruct

    Rules pick up the memory climb, the service exit, the telemetry gap and the failsafe, each naming the version and threshold that fired, and your engineer works the timeline from there.

  4. 04

    Hand off

    Export a marked case file with exact excerpts, the hash of every source, what the evidence cannot decide, and the questions still open.

Included

Everything included.

  • Six source formats
    Flight logs, companion journals, collector samples, ground receive logs, Chapter 10 recordings and range records.
  • Clock alignment with bounds
    Every source on UTC with its error stated, and order unknown where that error is larger than the gap.
  • Deterministic rules
    Findings that name their rule, version and threshold, so a rerun gives the same answer.
  • Evidence marking
    Observed, correlated, hypothesis and unknown, kept apart from the engineer’s conclusion.
  • Case files and exports
    Marked PDF, evidence bundles, originals with a manifest, MCAP, Parquet, CSV, JSONL and MATLAB.
  • Report checking
    Every figure and time in a draft matched back to the records, and marked where it is not supported.
  • Write-once originals
    Files hashed with SHA-256 on arrival and never rewritten. Reviewers annotate beside the evidence.
  • Hash-chained audit log
    Every import, view, edit, export and admin change recorded, verifiable, and streamed to your SIEM.
  • Storage connectors
    S3 and S3-compatible storage, Azure Blob, Google Cloud Storage, SFTP, SMB and NFS, an ingest API and manual upload.
  • Alerts and automations
    Findings routed to email, chat, ticketing and log platforms, at the data level you authorise.
  • Identity and roles
    SAML or OIDC single sign-on, SCIM provisioning, five fixed roles and a break-glass account on a hardware key.
  • Air-gapped operation
    Maps drawn from elevation data you load, licences checked offline, and updates as signed bundles with a bill of materials.
Who it is for

For teams that have to explain a failure.

Flight test and evaluation groups, operators flying survey, inspection and surveillance work, ground robot and autonomous vehicle programmes, and the manufacturers and integrators behind them. Anyone who has to say what happened, to a regulator, a customer, an insurer or a safety board, and be able to show where every statement came from.

  • Flight test and evaluation organisations
  • Drone operators on survey, inspection and surveillance work
  • Ground robot and autonomous vehicle programmes
  • Uncrewed systems manufacturers and integrators
How B Hub helps

B Hub deploys Foxborne inside your own environment, whether that is a cloud account, your own servers or a network with no path out, connects it to the storage and log servers your files already land in, and sets the rules, roles and markings with your team. We start with one incident you have already investigated: we reconstruct it beside the tools you use today, then compare where the evidence agrees with your conclusion, where it does not, and what it cannot decide.

Talk to us about Foxborne
Foxborne

In Partnership with Dude Lemon LLC, USA

Talk to usAll products