Who Leon is for

Start with the one-month free trial, which requires no credit card. Before it begins we implement your fleet, your users and your FTL rules, so you are evaluating the system with your own data rather than a demo dataset. The account is fully functional, so you can run real trips through it during the trial and decide on the basis of your own operation.

Leon covers flight operations, crew, sales and maintenance monitoring, but it is deliberately scoped to flight scheduling and operations rather than trying to be every system an aviation business runs. It is not a maintenance management system or an accounting system; instead it acts as a central data repository and integrates with dedicated tools such as CAMP and TRAXXALL for maintenance, plus flight planning, ground handling and fuel providers. The GraphQL API supports reading, writing and webhooks, including via Zapier or Power Automate, if you want to connect systems of your own.

Yes. Leon includes an Airline Schedule Manager for handling scheduled series, and our client base includes airlines operating ACMI, charter and scheduled services. PRO's MTOW-based tiers extend to aircraft above 110,000 lbs, so larger equipment is priced explicitly rather than treated as an exception.

Yes. Brokers are priced per user rather than per aircraft, at €99 per user per month, since there is no fleet to bill against. The Sales module supports quoting several aircraft in a single offer, a built-in CRM, a client database and an advanced Avinode integration.

Yes, and there is a plan built for it: a flat fee per month, independent of how many aircraft you handle or how many coordinators you employ. The system supports grouping and filtering flights per client, individual document templates per client, ordering services on clients' behalf, defining your own services and permits with costs, guest logins for clients and automatic billing sheets.

Yes — this is a core use case, and Leon is designed for aircraft scheduling in corporate flight departments and management companies alongside charter work. Access levels are set per user group (Admins, OPS, Sales, Crew, Ground), so a flight department that does no charter sales simply does not grant access to the Sales module. Management companies benefit from being able to separate data by client and produce client-specific document layouts, and owners can be given their own access to see their aircraft's schedule.

Business and charter aviation, corporate flight departments, aircraft management companies, airlines, trip support companies and charter brokers. We publish dedicated material for business operators, airlines and trip support companies, and the system supports work across multiple AOCs. What these operations share is the need to schedule aircraft and crew against regulatory limits, which is the problem Leon is built around; the differences show up in which parts you configure — a corporate flight department may never open Sales, while a charter operator lives in it.

The FTL engine is included in BASIC, at €99 per aircraft per month. Regulatory duty and rest limits apply regardless of fleet size, so we do not treat FTL as a premium capability. Rules are configured by our team to the regulations you actually operate under rather than being supplied as a generic template.

No, and this is what the BASIC plan exists for. BASIC costs €99 per aircraft per month and contains the same functional scope as PRO: the FTL engine, crew duty roster and currency tracking, handling requests, post-flight data, Flight Watch, quotes, fuel prices, per diems, checklists, the crew mobile app, Report Wizard and API access. It differs from PRO in offering the Table flights view rather than all three views, the Avinode integration rather than all integrations, and paid rather than included training. A two-aircraft operator pays €198 per month with an unlimited number of users.

Both. There is no minimum fleet size, no minimum number of users and no minimum contract value. Billing is per active aircraft per month, so a single-aircraft operator pays for one aircraft, and our client base runs from two-aircraft companies to airlines operating narrowbody fleets across multiple AOCs. The same system serves both — what changes is the plan and how much of the configuration you use, not the product.