GDS content as a scoped supply conversation

We do not publish a list of certified GDS connectors, and we do not invent mid-office badges. If your programme or your agency depends on a GDS path, that is a question for a demo, answered only with what is actually available. The Sabre and Amadeus pages exist for buyers who arrive on those names, and they follow this same rule. GDS mid-office workflows covers the operations view.

GTOS is the Global Travel Operating System from Voraal, built on operating experience across 100,000+ trips. The system you can evaluate today keeps policy, approvals, documents, spend and servicing on one trip record. Content sourcing is a conversation around that record, not a substitute for it.

What a GDS conversation should settle

It should settle what is available, what would be configured in implementation, and what will not be claimed in a proposal. It should also settle whether a booking from that path can still be approved, reported and serviced in GTOS the way a corporate client expects. If it cannot, the content path is not yet a programme path.

NDC is discussed with the same discipline. Many buyers will use mixed content. The comparison page is an explainer, not a ranking.

Family products, kept distinct

Rezencia and Folio6 are Voraal products for reservations and travel accounting. We do not claim a live production integration with GTOS beyond the family relationship. Avunzo is designed to connect content to your own channels and is not yet live on production; early access is available on request.

USD is the main currency on this site. Pricing is in USD and available on request. Each client sees only its own data. We do not claim certifications we do not hold. Bring the GDS path you actually run, and expect a factual answer rather than a logo row. Mid-office quality work, a client-visible booking, and a later invoice should all be part of the same discussion, because a source that is familiar to the desk but invisible to finance is still a broken programme path. The walkthrough should leave you with fewer implied certifications, and with a clearer view of what would actually be scoped. That is the only kind of GDS conversation that still holds after a second internal meeting. Bring the path you run and the client-visible booking you need, and keep both in the same discussion until the answer is specific. A GDS path that cannot be described that way should not be described as ready. Specificity is the whole point of the page.