The Operating System
for Aviation

No. Nemus is built around business activities, not a single business type: flight training, flying clubs, and aircraft rental — with shared scheduling, maintenance, billing, and reporting underneath. You enable the activities you do, and the right modules light up.

Create an account and answer a few questions about your operation — we review and approve new organizations, usually within one business day. Then invite your team by email or with a shareable link, and import your fleet and people at your own pace.

Yes — people create individual Nemus accounts and request to join your organization (or use your invite link). Admins approve requests, assign roles and locations, and everything is audit-logged.

Yes. Booking checks aircraft, instructor, and student conflicts, maintenance overlaps, and grounded aircraft — and proposes alternative slots when there's a clash. Staff can override with a reason.

Closing a flight computes billable time from the meters, rolls them forward, and creates a priced draft invoice in the same transaction — with the rate, the basis, and the readings behind every line. A draft is not a bill: approving it posts the ledger entry and sends it. Payments, outstanding balances and overdue flagging, and card or bank payment into your own Stripe account are built in.

Yes, and you don't have to ask us. An owner or administrator exports the whole organization — people, fleet, schedule, maintenance, invoices, payments — as one file, and the file lists what it deliberately leaves out. Members export their own record the same way, and a pilot can download their hours in the format ForeFlight imports.

Every organization is a fully isolated tenant. Role-based permissions gate every page and API, and every important action lands in an append-only audit trail. The controls we actually have in place are listed on our security page — along with the certifications we haven't done yet.