Vol. 0 · No. 1 · CH · VAUD · EFFECTIVE 2026-05-23 · PRE-MVP

The aviation software exchange.

Discover, compare and contract aviation software in days, not 18 months. A vendor-neutral exchange built by pilots and aviation-IT operators.

01 · POSITIONING

Three sides, one exchange.

VENDOR-NEUTRAL · CAT-A
01 / AIRLINES BUY-SIDE

Skip the RFP marathon.

Compare 50+ verified vendors across EFB, MRO, crew, OCC, network planning.

Transparent pricing, real implementation timelines, EASA / FAA approval status visible up-front. No more 14-month RFI/RFP cycles to land at the same five vendors.

02 / VENDORS SUPPLY-SIDE

Reach airlines without the enterprise sales cycle.

List, claim, respond — without a launching customer to be heard.

Standardized RFP templates. Lead routing. Transparent ratings, no pay-to-rank. Small innovators stand next to the giants on the same shelf, judged on the same metrics.

03 / THE EXCHANGE CROSS-SIDE

Cross-vendor data exchange.

Obstacle, performance, NOTAM data — bought once, reused across products.

Stripe-style neutrality for aviation software. Transparent pricing, fair ratings, no walled gardens. The infrastructure layer no individual vendor can build.

02 · DIAGNOSIS

A USD 13 billion market, still procured like it's 1999.

FILED · 2026-05-23

Aviation IT is the last enterprise software vertical without a vendor-neutral exchange. The cost of that absence is measured in years of RFP cycles, five-figure response budgets, and a permanent moat for whoever the airline picked in 2018.

For airlines

  • Operate 50 – 200 IT contracts, each with its own ESB integration
  • Buy the same data — obstacle, performance, weather — over and over per vendor
  • RFPs take 12 – 18 months from need to contract
  • Smaller carriers can't afford full vendor management — they ride incumbent rails

For vendors

  • Need an airline as launching customer just to be heard at the next bid
  • 5-figure RFP-response costs, no guarantee — most lose
  • Can't share data across products — contractually blocked by airline IT
  • Innovation lives or dies by who knows whom at the carrier

Source: Mordor Intelligence · Aviation Software Market 2025-2030 ▸ SITA IT Insights 2025 ▸ Internal interviews CH/EU carriers 2026

03 · PROCEDURE

Four steps. Days, not months.

STANDARD OPERATING PROCEDURE
  1. STEP 01 · DISCOVER

    Search across categories.

    EFB, MRO, crew, OCC, flight planning. Filter by aircraft type, certification, region, pricing band.

  2. STEP 02 · MATCH

    Scored profiles, side-by-side.

    Real customer counts, real implementation weeks, real pricing bands. Your requirements, their match score — read in minutes, not weeks.

  3. STEP 03 · RFP

    From requirements to dispatch in a day.

    Start from category templates, layer in your IT-security and compliance docs, send to the shortlist. Responses come back structured — not as 60-page PDF appendices.

  4. STEP 04 · CONTRACT

    Negotiate, sign, hand off.

    SLA and liability clauses flagged where they matter. Sign in-platform. Pass the executed scope and timeline straight to the implementation team.

04 · DATA & SANDBOX

A working aviation dataset before a single vendor signs.

DAY-0 ASSET · PUBLIC SOURCES

The exchange ships with a vendor-neutral reference catalog and a synthetic sandbox — built on public aviation data, licensed cleanly, free for developers, paid for production. Indie vendors can build and demo a working product in days, with no airline NDA, no pilot customer, no proprietary data exposure.

  1. LAYER 4A · REFERENCE

    Consolidated public master data.

    Airports, aircraft type designators, airline codes, route standards — aggregated from ICAO, IATA, public registries and ourairports.com. One schema, one API, documented license trail per source.

  2. LAYER 4B · SANDBOX

    Synthetic operations, real fidelity.

    Plausible schedules, fleets, NOTAM streams — generated from operational patterns (hub-spoke, crew cycles, maintenance windows). Vendors test their product against a realistic load profile without ever touching airline-proprietary data.

  3. LAYER 4C · EXCHANGE

    Cross-vendor data, when the network is there.

    Obstacle, performance, weather, NOTAM — bought once, reused across products under a transparent license engine. Goes live when listed vendors reach critical mass. The infrastructure layer no individual vendor can build.

  4. ACCESS

    Free for developers, priced for production.

    Open reference API at no cost (attribution required). Developer sandbox from USD 200 / month. Vendor and enterprise sandbox tiers bundled with marketplace listings. Indicative pricing — final tiers fix at MVP.

Sources: ICAO · IATA · ourairports.com (CC0) · FAA / EASA registries ▸ Synthesis engine: in-house, built on captain + aviation-IT-architect domain knowledge ▸ Synthetic — never anonymized

05 · PLAYGROUND

Sign in. Build a dataset. Ship a prototype.

PRE-MVP · 8 DOMAINS

The playground is the live face of the data foundation. Sign in, pick the domains you need, assemble a dataset of reference and synthetic operations, pull it through the API, and — phase 2 — build the demo in the browser. One workspace, no airline NDA, no pilot customer required.

01 / EFBCOCKPIT

Electronic Flight Bag

Everything a pilot reaches for on the iPad.

DATA

Aircraft type designators · airport codes & geometries · synthetic METAR/TAF · NOTAM streams · performance tables for 5 generic types.

EXAMPLE PRODUCTS

Briefing-pack generator · performance calculator · charts viewer · take-off / landing tool.

02 / MROMAINTENANCE

Maintenance, Repair, Ops

Keep the fleet airworthy.

DATA

ATA-chapter part-number schema · public FAA / EASA AD & service-bulletin subset · synthetic 30-AC maintenance records · MEL/CDL templates.

EXAMPLE PRODUCTS

Maintenance tracker · parts sourcing · AD/SB compliance dashboard · MEL tracker · tail-config manager.

03 / CREWROSTERING

Crew & Rostering

Schedules that respect FTL and human factors.

DATA

EASA FTL · FAA Part 117 · qualification matrix · synthetic 200-pilot roster (3 months) · fatigue-risk profiles · currency / recency.

EXAMPLE PRODUCTS

Roster optimizer · fatigue-risk tool · currency tracker · pairing generator · crew self-service · disruption re-allocation.

04 / OCCOPS CONTROL

Flight Operations Control

When the day breaks, who saves it.

DATA

Slot / CTOT spec · airport capacity profiles · synthetic 1000-flight EU day · disruption-event patterns · synthetic position streams.

EXAMPLE PRODUCTS

Disruption manager · slot coordinator · ops dashboard · re-routing tool · aircraft-swap optimizer · IROPS communications hub.

05 / NETWORKPLANNING

Network & Schedule

From route map to revenue management.

DATA

Airport-pair distances · time zones · synthetic O&D demand · connecting-wave patterns for 5 generic hubs · block-time statistics.

EXAMPLE PRODUCTS

Schedule planner · hub-connectivity analyzer · block-time optimizer · slot-bid tool · yield curves · route-profitability analyzer.

06 / CARGOAIR FREIGHT

Cargo & Air Freight

ULDs, manifests, ONE Record.

DATA

IATA ULD-type schema · dangerous-goods code subset · ONE Record schema · synthetic cargo manifests · hub-spoke cargo routing.

EXAMPLE PRODUCTS

ULD tracker · capacity optimizer · DG compliance tool · ONE Record integration demo · booking engine · cool-chain monitor.

07 / PAXEXPERIENCE

Passenger & Disruption

When the flight goes sideways, what does the passenger see.

DATA

Service-class definitions · loyalty-tier schema · EU261 / DOT disruption rules · synthetic 1M bookings · 200k loyalty profiles.

EXAMPLE PRODUCTS

Re-booking engine · loyalty calculator · service-recovery tool · EU261 compensation calculator · pax communications hub · tier-upgrade optimizer.

08 / SUSTAINCOMPLIANCE

Sustainability & Compliance

SAF, CORSIA, ETS — and the reports that follow.

DATA

SAF mandates (ReFuelEU, UK, Turkey, Japan, …) · CORSIA routes · ETS coefficients · emissions factors · fleet emissions profiles · SAF-uplift scenarios.

EXAMPLE PRODUCTS

CO₂ calculator · SAF reporter · CORSIA tracker · ETS cost forecaster · fleet decarbonisation planner · investor sustainability dashboard.

Phase 1 (Q3 2026): sign in, build a dataset, pull it through the API. Phase 2 (Q1 2027): code the demo in the browser, ship it as a working RFP submission — no airline contract required.

Reserve playground access

06 · CREDENTIALS

Built by operators, not consultants.

FOUNDING TEAM

Sven Gartz

CO-FOUNDER · A350/A380 CAPTAIN · AVIATION-IT ADVISOR

Twenty years in cockpit, multiple aviation-software product launches as launching customer, current advisor to a Tier-1 aviation IT provider on flight-ops strategy. Knows the procurement pain from both sides of the table.

Ashraf "Ashi" Hoseini

CO-FOUNDER · SENIOR AVIATION-IT ARCHITECT

Decade-plus designing aviation software products used by major European carriers. Sees firsthand how vendor lock-in and missing standards slow down the industry. Believes a neutral exchange can fix what no individual vendor can.

Stage: idea + concept. Domain secured, problem validated, market mapped. Joining early access means you help shape what we build first.

07 · NOTICE

Early-access roster.

CLOSED-COHORT

Drop your address. We share progress every four to six weeks, and invite you to the closed beta on launch. No spam, no third-party tracking, easy unsubscribe.

By filing you agree we may contact you about Rulaxy. We will never share or sell your data. See privacy.

08 · ADDENDUM

Frequently filed questions.

UPDATED 2026-05-23
Are you a vendor selling software?

No. Rulaxy is a vendor-neutral exchange. Revenue comes from platform subscription, transaction-free; never by competing with the vendors we host. Stripe-style neutrality, not Apple-style commission.

How is this different from Aircraft IT Operations or Aircraft IT Magazine?

Aircraft IT does directory and editorial. Rulaxy is built for the transaction — RFP automation, contract management, cross-vendor data exchange. Discovery is step one of four, not the whole product.

How is this different from Honeywell GoDirectTrade, Jeppesen Aviator, or SITA developer.aero?

Those are vendor-owned app stores — they showcase the owner's products. Walled gardens cannot be vendor-neutral by structural definition. Rulaxy is neutral: every vendor lists on equal footing, airlines see honest comparison.

Aren't Cirium, OAG and FlightAware already doing aviation data?

They sell real-time and historical flight intelligence at enterprise scale — that's a different product. Rulaxy ships consolidated public reference data plus a synthetic vendor sandbox. We don't compete on real-time coverage; we make it trivial for a vendor to build and demo against realistic operations without an airline contract.

"Synthetic" — does that mean anonymized?

No. Synthetic means generated from statistical operational patterns (hub-spoke profiles, crew duty cycles, maintenance windows), not derived from real flights. Anonymized aviation data is reverse-engineerable — tail sign plus route plus time is identifying. We don't go there.

When does it launch?

MVP target Q4 2026. Open reference API earlier — phase 0, alongside this landing page. Early-access cohort gets first look in Q3 2026.

Is this real, or just a landing page?

It's a landing page on top of a deep concept document, market analysis, business plan and risk register. Domain secured (rulaxy.com), founders identified, compliance pathway mapped. We are transparent: concept stage, not pre-revenue stage. The platform exists in spec, not in production.

Who is behind Rulaxy — and what are AirComply and RoolCon?

Rulaxy is a product of RoolCraft SA, a Swiss aviation services group based in Aubonne, Vaud (UID CHE-320.528.458, founded 2018). Two sister products run under the same roof: AirComply ships regulatory data as JSON (SAF mandates, CORSIA, ReFuelEU) to operators like SITA. RoolCon is the aviation-advisory practice. The three products share domain expertise and a clean Swiss legal seat; each has its own go-to-market and brand.