Straight answers to the questions shops ask

We import your aircraft, customers, and open maintenance events into the platform. Your current records map to the maintenance-event model — aircraft, squawks, findings, authorizations, and signatures — and the originals stay on as attributable source. Nothing is overwritten; imported history sits beside new events as committed facts, under the same provenance rules.

• —Aircraft, customers, and open events import first; your event profiles (routine, inspection, discrepancy) are configured to match how you already work.
• —Posted labor and issued parts import against the right aircraft and event, not as a flat dump.
• —Prior authorship, approvals, and signatures remain attributable — the record shows where each fact came from.

Onboarding is bounded by your data and your first real event, not a fixed contract. We configure the platform to your event profiles, import your aircraft and customers, then run your next live maintenance event through it with your people — that event is the training. We reply within two business days of your request; the first call is 30 minutes.

• —One product, configured to your shop. A single-location shop runs strong defaults; a multi-location operation activates hierarchy and delegation on the same product.
• —Your messiest recent event is the proof. If it does not hold up there, we fix the configuration, not your workflow.

Yes. The Mechanic Workbench captures work, photos, measurements, voice notes, and findings at the aircraft, offline. Captured work syncs when connectivity returns, and conflicts resolve by provenance — not last-write-wins. A mechanic’s observation stays a mechanic’s observation; nothing gets reordered by a bad signal.

You do. Your records, evidence, and publication history belong to your operation. No other shop can read your tenant. Export is yours on demand, in structured form, whenever you ask. We run the infrastructure; the facts stay yours.

Never as a side effect. Mechanic notes, photos, and findings stay internal until you publish them. Publication is an explicit, versioned, audience-scoped action — you choose what reaches the owner, in what form, and when. The customer sees the role-appropriate view of facts you committed to share, and nothing beyond it.

You run real maintenance events on the platform with your team, configured to how you actually work. We work alongside your shop to set event profiles, import records, and tune authorization to your authority structure. The pilot is the proving ground — built inside a working aircraft maintenance operation, then set up for a materially different shop without a fork.

Copilot proposes; your people confirm. It drafts record language, surfaces similar past cases, and suggests dispositions — and it stops there. Copilot never diagnoses, approves, authorizes spending, or signs. Every contribution carries its provenance: who reviewed it, when, and the source it drew from. The committed record always shows the human authority behind it.

• —Proposes only: drafts, retrievals, and suggestions. The decision is yours.
• —Never the authority: no autonomous technical diagnosis, no approval, no signature.
• —Full provenance: every AI-suggested line traces to its source and its human reviewer.