CASE STUDIES

Airline Document Generation on OpenShift with Iron Suite

AVIATION
Updated:

A major Middle East commercial passenger airline (a national flag carrier preparing for international route launches) embedded IronPDF and the full Iron Suite inside its OpenShift-based microservices platform to handle high-volume document generation across reservations, ticketing, check-in, and operations. The deployment runs in-process on Red Hat OpenShift on Microsoft Azure, scales horizontally with the rest of the platform, and is anchored by a three-year Unlimited Enterprise SaaS OEM agreement that locks in the full Suite (IronPDF, IronOCR, IronXL, IronBarcode, IronQR, IronZIP, IronWebScraper, IronSecureDoc, and IronPrint) under a single commercial envelope.

TL;DR

  • Industry: Aviation (commercial passenger airline, Middle East flag carrier preparing for international launch).
  • Iron products: Iron Suite (the full bundle), with IronPDF in primary production use and the rest available for adjacent workflows.
  • Workflow: Embedded, high-volume PDF document generation inside .NET microservices on Red Hat OpenShift on Azure.
  • Headline outcome: Single-vendor document and data stack delivered in time for inaugural international service, with a scaling architecture authored jointly with Iron Software's solutions team.
  • Licensing model: Iron Suite Unlimited Enterprise SaaS OEM, three-year subscription, renewing May 2028.

The Challenge

The decision was driven by three problems running in parallel (business, technical, and commercial) that all had to clear before the carrier's launch window.

The business pressure: The carrier was preparing for inaugural commercial operations and international route launches, with no slack in the schedule to absorb tooling failures. Every PDF the platform produces (boarding passes, ticket receipts, baggage tags, manifests, regulator-bound reports) goes directly to passengers, ground handlers, and regulators. Any defect cascades to the gate, the regulator, and the customer on a timeline visible to executives and civil aviation authorities. Layered on top: enterprise procurement, legal review, EULA negotiation, and Kingdom of Saudi Arabia–specific contractual treatment all had to clear before purchase, and the licensing model had to scale with the airline without per-developer, per-pod, or per-cluster cost surprises.

The technical wall: Early evaluations surfaced performance issues that had to be resolved before any commitment. PDF rendering had to scale alongside the rest of the platform by adding more containers under load. The carrier's engineering stack uses three languages: .NET for the production path, with Node.js and Python alongside. The library family had to work across all three. Compatibility with Red Hat OpenShift on Microsoft Azure, inside the carrier's own cloud, had to be verified directly.

The commercial blocker: The carrier needed OEM-grade redistribution rights to embed the libraries inside applications it operates internally and ships across partner-facing channels. Per-developer or per-deployment metering was a non-starter at airline scale; the cost shape was as important as the technical fit. Legal review covered EULA, insurance, liability terms, and KSA-specific tax treatment, with multiple rounds between in-house and external counsel. Open-source PDF libraries on the table fell short on three counts: rendering fidelity for airline-grade templates, commercial support and liability protection, and predictable performance. Multi-vendor stitching (separate PDF, OCR, Excel, and barcode vendors) would have multiplied the EULA review and support relationships the carrier needed to manage.

How Iron Software Helped

Why this vendor

Today, the carrier's document pipeline runs on IronPDF built directly into the microservices on Red Hat OpenShift on Azure. The rendering workload scales by adding more worker pods alongside the rest of the platform; the full Iron Suite is licensed and available for adjacent workflows as they come online; and the three-year Unlimited Enterprise SaaS OEM agreement is in place as the commercial floor.

The decision to consolidate onto a single vendor wasn't driven by one capability. It was driven by the alternative: stitching together separate PDF, OCR, Excel, and barcode vendors would have multiplied EULA reviews, redistribution risks, and support relationships at exactly the scale where each of those carries operational cost. Iron Suite covered the full document and data toolkit (PDF generation, OCR, spreadsheets, barcodes and QR codes, ZIP packaging, web scraping, secure documents, and print) under a single commercial agreement aligned to the carrier's platform model.

Three criteria beyond raw feature coverage carried weight in the evaluation:

  • Runtime portability. .NET is the carrier's main production language, but Node.js and Python are under active evaluation for adjacent services. Iron Suite covers all three, with the carrier informed up front that Node.js and Python bindings typically receive new features approximately one month after .NET.
  • OpenShift-on-Azure compatibility. Proven behavior inside the specific container platform the carrier runs. Iron Software's solutions team confirmed this during the trial phase.
  • Quality of the engagement. A vendor whose architects sit down with the customer's engineers and produce a working scaling design signals a different kind of partnership than a vendor that points at the public docs.

What Iron delivered

Across three days in mid-January 2025, Iron Software's solutions team worked alongside the carrier's engineers to produce the reference design for IronPDF in the carrier's OpenShift environment. The work covered an architecture review on January 16, technical liaison and proof-of-concept work on January 17 through 19, and a complete scaling architecture and technical block diagram delivered on January 20. The performance issues raised earlier in evaluation were resolved through a combination of configuration tuning and the architectural changes that engagement recommended. The customer confirmed resolution before commercial close.

Integration was straightforward once the architecture was in place. IronPDF was installed as a library inside the carrier's existing .NET services; other services call it directly when they need a document rendered, and load spreads across additional pods on OpenShift. Because IronPDF runs inside the services, document content never leaves the platform; security stays inside the carrier's own Azure account, which simplified information security review and removed an entire category of compliance question from the procurement track.

Engagement and timeline

The engagement itself was high-touch. A dedicated sales lead, more than a dozen meetings spanning technical, commercial, and legal topics, and fast escalation through both Iron support and solutions engineering kept the evaluation on schedule. Enterprise-grade support (priority queue, faster response times, priority bug fixes) was available throughout the trial and continues today. The carrier flagged 24/7 support coverage as a preferred future state; coverage is 24/5 currently, with the 24/7 question under active evaluation by Iron Software.

Time from first contact to signed contract spanned about seven months (October 2024 to May 22, 2025), paced by extended legal and procurement review. Technical decision-making was substantially complete well before signing. The system was live in time to support the carrier's international route launches later in 2025, and is in production today supporting live commercial operations.

Licensing and Procurement Fit

The agreement is an Iron Suite Unlimited Enterprise SaaS OEM license, three-year subscription, with support and updates included. The "unlimited" word does a lot of work here: developer headcount, container counts, and transaction volume can all scale without re-pricing. The OEM rights cover embedding the libraries inside both internal applications and partner-facing channels.

The specific commercial questions that had to be answered first were OEM-grade redistribution and unlimited-use scaling. The carrier operates a hosted platform that ships document outputs across multiple partner relationships. That usage had to qualify cleanly as OEM rather than external SaaS redistribution, and the licensing model had to accommodate a microservices platform without per-pod or per-cluster metering. Both were addressed in the contract structure: redistribution rights were written explicitly, and the unlimited-use model replaced any per-developer or per-deployment cost shape.

The legal track was where the calendar lived. EULA, insurance, contractual indemnities, and Kingdom of Saudi Arabia–specific tax treatment all required multiple review cycles between Iron Software's legal team and the carrier's in-house and external counsel. The seven-month evaluation-to-commercial-close timeline reflected that work and ended with both sides aligned on every commercial term before signature.

Commercially, the agreement delivered the fixed multi-year envelope the carrier needed to replace what would have been variable per-server, per-developer, or per-pod cost models from alternative vendors. For an enterprise finance team planning TCO across the life of a fast-scaling airline platform, that structure carries more value than any single product price point.

Results

Specific production metrics (p95 latency, throughput, pod counts, incident rates) remain confidential and customer-supplied for the published version. The directional outcomes the engagement produced are concrete.

Vendor consolidation. Document generation, OCR, spreadsheet handling, barcode and QR codes, ZIP packaging, secure document handling, and print all now run through one vendor's SDKs under one commercial agreement. What would have been multiple separate library purchases (each with its own EULA, redistribution model, support relationship, and renewal cycle) collapsed to one.

Scaling architecture in place from launch. The scaling design Iron Software's solutions team authored in January 2025 closed the performance question before purchase. The carrier's platform now has a documented, tested pattern for handling rendering load on its OpenShift setup, built around the carrier's specific environment.

Commercial predictability. Fixed three-year envelope. Unlimited usage rights for developers, pods, and transactions. The licensing math is decoupled from platform growth, which removes one of the larger forecast uncertainties for a finance team underwriting a fast-scaling carrier.

Document infrastructure delivered on time. The system was in production through the carrier's inaugural international service period in late 2025 and is operating today across live commercial workflows. Adjacent workflows are licensed and positioned for activation as the carrier brings them online: IronOCR for identity-document handling at check-in, IronBarcode and IronQR for boarding and baggage, IronSecureDoc for protected document delivery.

The carrier's Iron Suite engagement reduces to a set of aligned decisions: a single vendor covering the full document and data surface, a licensing model that matches how a fast-scaling airline platform actually operates, an engineering engagement that produced a working scaling design before commercial close, and a fixed three-year commercial floor a finance team can plan against. The production metrics behind it remain confidential.

If you're evaluating a similar consolidation (high-volume document generation, multi-runtime stack, container deployment, strict enterprise procurement), Iron Software's Solutions Engineering team runs architecture-review calls that cover exactly this kind of decision, and trial licenses are production-capable so you can validate before signing anything.