Local-first, not cloud-dependent
UAS operations regularly run from staging areas with poor or intentionally limited connectivity. A maintenance system that stops working when the network does is not an operations tool.
Local-first means the workspace file is the source of truth on the machine in front of you. Records are created, edited, and read without a round trip.
Practical implications
- Encrypted workspace files with desktop persistence and native exports.
- Explicit, reviewable merges instead of silent background sync.
- Reports generated locally, so a readiness brief never waits on a server.
- Clear labeling of which capabilities are desktop-only versus available in the browser demo.
In the browser demo
The public demo runs on synthetic sample data. File operations there are previews only; encrypted workspaces, persistence, and native exports belong to the desktop application.