> ## Documentation Index
> Fetch the complete documentation index at: https://voyant.travel/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Module catalog

> The headless domain modules you compose into a Voyant app, with a link to the in-depth page for each one.

A Voyant application is assembled from **domain modules**. Each module owns one subdomain of the travel business: its tables, its services, its HTTP routes, and its React UI. You install the ones you need and link them together.

This page is the index. For the internal shape behind these modules, see [How Voyant is built](/docs/concepts/how-it-is-built).

## How a module is packaged

A single domain ships as a small family of packages:

* **`@voyant-travel/<domain>`** is the headless core: Drizzle schema, services, and HTTP routes.
* **`@voyant-travel/<domain>-contracts`** describes the wire types shared between server and client.
* **`@voyant-travel/<domain>-react`** provides hooks, clients, query keys, view-model helpers, and reusable components for that domain.

For example, bookings ships as `@voyant-travel/bookings`, `@voyant-travel/bookings-contracts`, and `@voyant-travel/bookings-react`.

## Selling and sourcing

| Module                                         | What it owns                                                                                        |
| ---------------------------------------------- | --------------------------------------------------------------------------------------------------- |
| [catalog](/docs/platform/modules/catalog)           | The normalized sellable catalog and the projection that interleaves operated and sourced inventory. |
| [inventory](/docs/platform/modules/inventory)       | Availability rules, slots, closeouts, allotments, and capacity.                                     |
| [commerce](/docs/platform/modules/commerce)         | Pricing, the cost, rate, and price distinction, markets, FX, promotions, and sellability.           |
| [distribution](/docs/platform/modules/distribution) | Channels, commission rules, channel push, reconciliation, and settlement.                           |

## Sales and relationships

| Module                                           | What it owns                                                              |
| ------------------------------------------------ | ------------------------------------------------------------------------- |
| [relationships](/docs/platform/modules/relationships) | The CRM core: people, organizations, contact points, and addresses.       |
| [proposals](/docs/platform/modules/proposals)         | The sales pipeline: proposals, proposal versions, stages, and activities. |

## Commitment and operations

| Module                                     | What it owns                                                                                    |
| ------------------------------------------ | ----------------------------------------------------------------------------------------------- |
| [bookings](/docs/platform/modules/bookings)     | The durable first-party commitment: bookings, items, allocations, fulfillments, and provenance. |
| [trips](/docs/platform/modules/trips)           | Trip envelopes that group component bookings into one customer-facing itinerary.                |
| [operations](/docs/platform/modules/operations) | Ground operations, dispatches, resources, and resource holds.                                   |

## Money and compliance

| Module                                           | What it owns                                                                           |
| ------------------------------------------------ | -------------------------------------------------------------------------------------- |
| [finance](/docs/platform/modules/finance)             | Invoices, credit notes, payments, payment schedules, guarantees, and collection plans. |
| [legal](/docs/platform/modules/legal)                 | Contracts, contract templates, signatures, policies, and policy acceptances.           |
| [notifications](/docs/platform/modules/notifications) | Templated notifications and multi-channel delivery.                                    |

## Travel verticals

| Module                                             | What it owns                                                                    |
| -------------------------------------------------- | ------------------------------------------------------------------------------- |
| [cruises](/docs/platform/modules/cruises)               | Cruise catalog, sailings, cabin categories, and itinerary modeling.             |
| [flights](/docs/platform/modules/flights)               | Flight search, pricing, booking, and order management.                          |
| [accommodations](/docs/platform/modules/accommodations) | Accommodation as catalog inventory for resale, packaging, and trip composition. |
| [charters](/docs/platform/modules/charters)             | Charter operations and inventory.                                               |

## Platform packages

These are not domain modules, but the runtime and surfaces everything builds on: `@voyant-travel/core`, `@voyant-travel/db`, `@voyant-travel/hono`, `@voyant-travel/auth`, `@voyant-travel/storage`, `@voyant-travel/i18n`, the [Public API](/docs/platform/public-api), and the [admin](/docs/platform/admin) shell. There are also supporting modules such as `catalog-authoring`, `identity`, and `octo` (OCTO-standard connectivity for tours and activities).

<Note>
  Each headless module has matching `-contracts` and `-react` packages where a UI surface exists. The tables list the core module name; install the family that fits your app.
</Note>

## Next steps

<CardGroup cols={2}>
  <Card title="How modules work" icon="cubes" href="/docs/concepts/how-it-is-built">
    The internal shape, at the altitude you need to use the API.
  </Card>

  <Card title="Links" icon="link" href="/docs/concepts/how-it-is-built">
    How modules relate without coupling.
  </Card>

  <Card title="Data models" icon="table" href="/docs/concepts/how-it-is-built">
    How module schemas are authored.
  </Card>

  <Card title="Glossary" icon="book-open" href="/docs/concepts/glossary">
    The vocabulary these modules share.
  </Card>
</CardGroup>