> ## 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.

# Voyant and Voyant OSS

> What is the same and what differs between running Voyant OSS yourself and using Voyant: the platform, the integration surface, and the one capability that is Voyant-only.

Voyant is open core. The platform is the same either way, and so is almost everything you build against it. This page is the honest list of what differs.

## The same in both

The **platform** is identical: catalog, pricing, inventory, bookings, finance, CRM, proposals, distribution, and the verticals. Same data model, same behavior, same [domain modules](/docs/platform/modules).

The **integration surface** is identical too. However you run Voyant, you build on it the same way:

<CardGroup cols={2}>
  <Card title="APIs" icon="code" href="/docs/guides/consume-the-api">
    The admin, storefront, and app API surfaces, with typed [SDKs](/docs/sdks/overview).
  </Card>

  <Card title="Webhooks and events" icon="bolt" href="/docs/platform/fundamentals/events">
    Subscribe to domain events and drive your own systems from them.
  </Card>

  <Card title="Custom fields" icon="tag" href="/docs/platform/fundamentals/custom-fields">
    Carry your own data on core entities, namespaced to you.
  </Card>

  <Card title="Apps and extensions" icon="puzzle-piece" href="/docs/platform/extending/apps">
    Build your own apps and admin extensions against the same scoped APIs, events, and custom fields.
  </Card>
</CardGroup>

**Automations run on your infrastructure, not inside Voyant.** Orchestrate with whatever you already use — Vercel Workflows, Cloudflare Workflows, Temporal, a cron box — calling the Voyant API and reacting to its webhooks. Voyant does not ask you to write workflow code inside the deployment.

**[Voyant Connect](/docs/connect/overview) works with both.** Supplier connectivity is a hosted product you consume over its API and SDK, so a self-hosted deployment gets the same official connectors as a managed one. You can also [build your own connector](/docs/connect/private-connectors) either way.

## What differs

|                                    | Voyant OSS                                                                                                   | Voyant                                                  |
| ---------------------------------- | ------------------------------------------------------------------------------------------------------------ | ------------------------------------------------------- |
| **Who operates it**                | You. You run the container, own the Postgres database and secrets, and handle upgrades and scaling.          | Provisioned, operated, upgraded, and scaled for you.    |
| **Marketplace apps**               | Not available. You can still build and install your own apps.                                                | Install reviewed apps from the marketplace.             |
| **[Max](/docs/max/overview)**           | Not available. Max availability and token issuance are managed-only, and there is no self-hosted embed flow. | Included, in the admin and over messaging.              |
| **[Services](/docs/services/overview)** | Not included. Bring your own email, SMS, storage, search, and so on, selected as providers.                  | Messaging, vault, browser, video, realtime, and search. |
| **Support**                        | Community.                                                                                                   | Included with your plan.                                |

Everything else is a question of who runs the infrastructure, not what the platform can do.

<Note>
  A Voyant deployment can be exported to Voyant OSS at any time, so choosing the managed path is not a one-way door.
</Note>

## Choosing

Run **Voyant OSS** when you want to own the infrastructure, you already have a platform team, or your environment requires self-hosting.

Use **Voyant** when you would rather not operate a database, a runtime, and an upgrade path, or you want Max, marketplace apps, and the bundled services.

<CardGroup cols={2}>
  <Card title="Quickstart" icon="rocket" href="/docs/quickstart">
    Both paths, start to running.
  </Card>

  <Card title="Architecture" icon="diagram-project" href="/docs/concepts/architecture">
    How a deployment is put together.
  </Card>
</CardGroup>