Platform capabilities
Built for the hangar,
not the boardroom.
Every feature exists because paper logbooks have a failure mode. These are the specific systems we built to close each gap — with the FAR as the spec sheet, not a marketing checklist.
Append-only logbook with blockchain anchor
Every maintenance entry is SHA-256 hashed into a per-aircraft chain. The server applies an Ed25519 signature; mechanics can co-sign with their certificate number. Records are batched nightly into a Merkle tree, and the root is anchored to Ethereum as permanent calldata — verifiable by anyone with a block explorer. Modify any entry after sealing and the chain breaks.
Open Explorer →Work-order pipeline: 0xSQ → 0xWO → 0xWI → 0xLP
Squawks become work orders, work orders spawn work items, work items resolve into logbook pages. Every state transition is time-stamped and signed. The pipeline enforces FAR 43.9 fields — description, date, method of compliance, aircraft total time, mechanic name and certificate number — at the work-item seal step, not as an afterthought.
See the pipeline →Aircraft transfer with cryptographic handoff
Selling or transferring an aircraft creates a one-time signed token tied to the N-number and a 72-hour expiry. The recipient accepts the transfer through a hardened endpoint; the chain of custody is appended to the aircraft record and permanently sealed. No more unsigned logbook pages passed between strangers.
Transfer flow docs →Mechanic signing with FAA cert verification
Mechanics enter their certificate number at sign-off. The platform cross-references the FAA Airmen Inquiry registry in real time and attaches the certificate status, ratings, and expiry date to the sealed record. Future inspectors see exactly who signed what and whether the certificate was current at the time of the work.
Signing walkthrough →Mobile-first, field-ready interface
The logbook was designed on a phone first. Tap a squawk, create a work order, scan a part number, snap a photo, and co-sign — without leaving the apron. Forms auto-save every 10 seconds. Offline drafts sync when connectivity returns. No minimum viable desktop required.
Open on mobile →Integrations: Stripe, IPFS, FAA Airmen registry
Subscription billing runs on Stripe with no custom payment code on our side. Sealed record bundles are pinned to IPFS via a self-hosted node for disaster recovery — if the platform disappears, your records remain verifiable on the public network. The FAA Airmen registry integration runs nightly to flag expired certificates before they become a compliance problem.
IPFS verification →Start the 14-day free trial.
No credit card. Cancel any time. Your data exports in full.