Domains overview

A domain is one installable vertical of the platform — Catalog, Commerce, CMS, Blog, CRM, Marketing, Helpdesk, Kanban, Copilot. Each domain owns its own data, its own API prefix, and (where it has one) its own admin section and storefront surface. Your purchase determines which domains are installed on your deployment; an uninstalled domain’s menu, routes and API simply don’t exist, rather than existing but being locked.

Note

This page is the map. Day-to-day usage lives in the Admin Guide; configuration lives under Configuration.

The domains

CatalogProducts, variants, categories — browse and quote.

CommerceCart, checkout, orders, inventory, payments, couriers.

CMSHomepage, collections, policy pages — content without deploys.

BlogThe storefront journal — articles, SEO, webhooks.

CRMAccounts, contacts, leads, pipelines, quotes — a sales desk.

MarketingSocial campaigns and posts across connected channels.

HelpdeskSupport tickets and a knowledge base.

KanbanBoard-style work tracking.

CopilotAn engineering agent that drafts OpenProject tickets from a requirement.

How domains relate to everything else

Layer	What lives there	Examples
Domain	One vertical, installed or not	Catalog, Commerce, CRM
Add-on	An optional feature sold on top of exactly one domain	Blog Autopilot (parent: Blog)
Platform	Shared capabilities every domain can use, and that never depend on a domain	Identity, notifications, file storage — see Platform
Package	A shared, versioned integration a platform service delegates to	Payment, courier, SMS, fraud adapters — see Provider packages

Dependencies between domains

Domains don’t import each other sideways. The one declared exception: Commerce requires Catalog — the product, variant and stock records commerce sells against live in Catalog, so Commerce cannot run alone. Every other domain (CMS, Blog, CRM, Marketing, Helpdesk, Kanban, Copilot) is independent: you can run any of them with or without the others.

Catalog-only vs. full commerce

A catalog-only store (Catalog without Commerce) shows products and takes “Request a quote” inquiries instead of a cart — no checkout, no stock reservations. Add Commerce later to turn the same catalog into a sellable shop; nothing about the product data changes.

What’s actually installed on your deployment

Ask support, or check what appears in your admin sidebar — an uninstalled domain never renders a menu section, a route, or an API prefix. See Features for the full purchase-facing tour, and Deployment shape for how domains map onto the three hostnames.