Travel apps that start with the supply you can actually sell

We don’t publish prices, because cost depends on the supply integrations, the payment model, which apps and portals you need and how much content you manage. Supplier and aggregator fees are separate. After a free call you get a written scope and a fixed quote.

It depends on scope and on supplier access: supplier approvals and certification take time, so we start them early. A focused first release with one supplier and one market comes first. Your written scope sets the date for each release, with a demo every week.

For flights: GDSs (Amadeus, Sabre, Travelport), airline NDC APIs and aggregators such as Duffel. For hotels: supplier APIs such as Expedia Rapid and Booking.com’s Demand API, plus direct contracts. Each has its own access rules and terms, which we confirm before scoping.

GDS access usually means a commercial agreement and, for ticketing, accreditation or a consolidator, which takes time. Many startups launch on an aggregator or direct contracts, then add GDS or airline NDC connections as volume grows. We design the booking layer so suppliers can be added without a rewrite.

NDC is IATA’s XML-based standard for airlines to distribute offers, including bundles and ancillaries, to third parties. IATA says it is open to any third party or IT provider. You need it if you want airline offers that only come through NDC; many apps get NDC content through an aggregator rather than connecting directly.

Not always. Accreditation lets you ticket directly; without it, you can work through a consolidator, host agency or an aggregator that handles ticketing. The right route depends on your markets and volumes. Elgrith holds no accreditation; we build for the route you choose. This is general guidance, not legal advice.

By keeping card data out of their own systems where possible: tokenized capture through the payment provider, hosted fields or pages, and control of every script on the payment page, as PCI DSS v4.0.1 requirements 6.4.3 and 11.6.1 require since 31 March 2025. Compliance itself is assessed by your acquirer or a QSA.

Yes. We generate passes with Apple PassKit and the Google Wallet API for bookings, tickets and boarding passes your supplier provides, and update them when times or gates change. Passes need your own Apple and Google developer accounts.