Skip to main content
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. The integration surface is identical too. However you run Voyant, you build on it the same way:

APIs

The admin, storefront, and app API surfaces, with typed SDKs.

Webhooks and events

Subscribe to domain events and drive your own systems from them.

Custom fields

Carry your own data on core entities, namespaced to you.

Apps and extensions

Build your own apps and admin extensions against the same scoped APIs, events, and custom fields.
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 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 either way.

​
What differs

Everything else is a question of who runs the infrastructure, not what the platform can do.
A Voyant deployment can be exported to Voyant OSS at any time, so choosing the managed path is not a one-way door.

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

Quickstart

Both paths, start to running.

Architecture

How a deployment is put together.