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 anchoring (rolling out)
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. Anchoring to Ethereum (Sepolia testnet first) is rolling out: records will be batched into a Merkle tree and the root written as calldata, verifiable by anyone with a block explorer. Sealed records can already be checked on the public verifier, and modifying any entry after sealing breaks the chain.
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 recorded. 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 certificate numbers
Mechanics enter their certificate number at sign-off, and the signature carries it. Anyone can look that number up on the FAA Airmen Inquiry, and the mechanic's passport has a Verify with FAA button that opens the Inquiry with their name filled in. We do not query the registry for you.
Signing walkthrough →Mobile-first, field-ready interface
The logbook was designed on a phone first. Tap a squawk, create a work order, sign, and co-sign — without leaving the apron. No minimum viable desktop required.
Open on mobile →Integrations: Stripe and IPFS
Subscription billing runs on Stripe with no custom payment code on our side. When a record is sealed we try to add a copy to a self-hosted IPFS node on our own server. This is best-effort: it is not a retention or recovery guarantee, and no offsite copy exists yet.
IPFS verification →Start free, or try Pro for 15 days.
Free needs no card. The Pro trial needs a card; cancel anytime before day 15. Your data exports in full.