Cathay Technologies Is Selling Its Own EFB to Competitors — and That's a Bigger Deal Than It Looks

There’s a specific kind of credibility that only comes from having actually operated the software you’re selling. Most EFB vendors built their platforms by studying airline operations from the outside and then designing toward a specification. Cathay Technologies is doing something different: taking a tool that Cathay Pacific built for its own pilots in 2019, has run across its entire group fleet for years, and is now selling externally to other airlines — starting with Cargolux.

The Cargolux deal, announced in June, is the first external commercial deployment of Cathay’s Electronic Flight Folder (EFF). It deserves attention not because of the contract size or the parties involved, but because of what the model represents.

What the EFF Actually Is

The EFF is a pilot-facing digital platform that consolidates the core document stack a crew needs for every flight: flight plans, load sheets, fuel data, NOTAMs, and the rest of the preflight information set. The goal is the same one every EFB platform pitches — one place for the information that used to exist across paper, multiple apps, and radio voice communications — but the lineage here is different. Cathay’s own aviation professionals built this tool to solve problems they were experiencing on the flightdeck, not problems inferred from customer interviews.

Cathay Technologies was formally established as a subsidiary in April 2025, specifically to commercialize that in-house digital work for the broader aviation market. The EFF is its flagship product. Cargolux — Luxembourg’s all-cargo carrier and one of the larger freight operators in Europe — is the first external customer to go live with it.

The Cargolux deployment includes the EFF’s Ops Chat feature: a crew-to-ground communications tool embedded directly inside the flight folder workflow rather than running as a separate ACARS or messaging application. The design bet is that consolidating comms within the document context reduces the need to context-switch between systems during preflight and in-flight coordination. That’s a sensible idea in principle, and I think it can deliver real value — provided the integration doesn’t somehow mask or degrade the primary functionality of the app. When the flight folder itself is the thing crews depend on most, anything that adds cognitive overhead to reaching it works against the whole point.

The Entrant Model Is the Story

EFB platform competition has historically been between purpose-built vendors — Jeppesen ForeFlight, NAVBLUE, Bytron, Aviobook and a handful of others — who built products for the market from the outset. Cathay Technologies’ position is structurally different: it comes from years of real operational use across Cathay Pacific, Cathay Cargo, HK Express, and Air Hong Kong before a single external sales call was made.

That kind of operational track record is genuinely difficult to manufacture. When an evaluating airline asks “what does your failure rate look like at scale?” or “how do you handle a load sheet revision 20 minutes before departure?” — Cathay Technologies can answer with production data from a group that operates hundreds of widebody departures a day, not a reference customer list assembled to support a sales cycle.

That heritage is a real credibility asset, but it cuts both ways. The same operational depth that makes the platform credible can also raise a reasonable question in a procurement room: is this tool genuinely built for the market, or is it specifically optimized around Cathay’s own operational patterns? And relatedly, will Cathay Pacific always be the de facto priority customer when roadmap decisions get made? Those aren’t unfair concerns for an airline evaluating a long-term EFB commitment, and Cathay Technologies will need to address them directly as it broadens its commercial footprint.

The deeper test is whether the product maps cleanly onto a European cargo carrier’s workflow without significant adaptation. A platform shaped by Cathay Pacific’s regulatory environment, internal systems, and operational culture won’t automatically translate — and the EFB evaluation process at a major carrier cares as much about integration depth, vendor support infrastructure, and long-term roadmap alignment as it does about operational heritage.

The Cargolux win suggests Cathay Technologies has at least cleared the initial hurdle. Whether it can scale the commercial model beyond its first external reference customer is the more interesting question.

What It Signals for the Broader Market

The Cathay Technologies model isn’t unique in concept — airlines have occasionally tried to monetize internal tools before — but it’s rare to see it executed with this level of organizational intent. Establishing a formal subsidiary, partnering with Hong Kong Science and Technology Parks for innovation infrastructure, and positioning Cargolux as a reference customer rather than a pilot program — these are commercial-market moves, not internal IT experiments.

For traditional EFB vendors, this represents a new category of competition: operators who built software for their own use and now have both the product and the credibility to compete externally. The Ops Chat integration is a useful illustration of that difference — embedding operational comms inside the flight folder reflects how a real airline thinks about the preflight workflow, not how it might be sketched out from the outside.

The Cargolux deployment will be the real test of the concept. If the EFF performs in a different airline’s operational environment with the same reliability it has shown inside the Cathay group, the commercialization case gets considerably stronger. If adaptation friction turns out to be higher than expected, that’s a different kind of market signal entirely.

Either way, the model is worth watching. Airline-built flight ops software entering the commercial market is a structural development, not just a product story.

Sources

← Back to all posts