Skip to main content
Voyant is the back office an online travel agency, tour operator, or destination management company runs on. It is a complete travel commerce platform, not a toolkit you assemble into one, and not a generic CMS or storefront with travel bolted on. It covers the whole operation:
  • Catalog and products — tours, packages, charters, cruises, flights, and accommodation held as resellable inventory.
  • Pricing and sellability — offers, occupancy pricing, promotions, travel credits, and channel-aware rules.
  • Inventory and availability — allotments, departures, and the operational logistics behind them.
  • Bookings — the full lifecycle, participants, requirements, and itinerary composition.
  • Finance — invoicing, payments, supplier costs, tax, FX, and profitability.
  • CRM and proposals — people, organizations, pipelines, and versioned proposals that carry a trip from sales pursuit to confirmed booking.
  • Distribution and the Public API — channel distribution plus a public booking surface for your customers.
It sits on a normalized travel operations data model. Each domain contributes its own API surface, events, and React components, so what you integrate against is consistent across the whole platform.

​
Two ways to run it

Voyant is open core. The platform is the same either way; what differs is who operates it.

Voyant

Sign up and use it. Provisioning, upgrades, security, scaling, and maintenance are handled for you.

Voyant OSS

The open-source platform under Apache-2.0, shipped as a container image. Self-host it on your own infrastructure. Export a Voyant deployment to it at any time.
The platform, the APIs, webhooks, apps, and extensions are identical in both. See Voyant and Voyant OSS for the short list of what actually differs.

​
How you build on it

You do not fork Voyant or write modules for it. You integrate with it:
  • Call its APIs — admin, public, and app surfaces, with typed SDKs.
  • React to its events — durable webhooks into your own systems.
  • Automate on your own infrastructure — Vercel Workflows, Cloudflare Workflows, Temporal, whatever you already run.
  • Extend the admin — apps and extensions that add surfaces and behavior without changing the deployment.
  • Carry your own data — custom fields namespaced to you.

​
Beyond the platform

On Voyant, the back office comes with products built around it. You can use any of them on their own, or together.

Connect

Supplier and inventory connectivity. Bring your own supplier credentials, ingest a catalog once, and resell it across many connections.

Data

Travel data APIs: geography, aviation reference data, currency exchange, and business data behind a single client.

Max

An AI ops agent that drives your deployment through its own APIs, in the admin or over messaging.

Services

The operational services a travel app needs day to day: messaging, verification, a secrets vault, browser rendering, video, realtime, and search.

​
Start here

Quickstart

Get a Voyant deployment running, self-hosted or managed.

Architecture

How modules, links, jobs, subscribers, and the Public API fit together.

Module catalog

Every domain module and what it owns.

SDKs

Typed clients for the admin, public, and service APIs.
Need help? Reach out at hi@voyant.travel.