Multi-domain
Serve one Autonnel deployment on several custom domains: attach pages per domain, pick a fallback default, run funnels across domains, set DNS, TLS and CDN.
A single deployment can have multiple domain names. Exactly one domain is the fallback default (isPrimary in the API). Each page is served only on the domains it is attached to.
Domain fields
Each domain has:
- Host — the domain hostname, e.g.
shop.example.com. - Fallback default (
isPrimaryin the API) — exactly one domain per deployment is the fallback default.
Adding a domain
- Go to Pages → Domains.
- Click Add domain.
- Enter the hostname (e.g.
shop.example.com). - Click Save.
You can add as many domains as needed. To change the fallback default domain, click Set as fallback default on another domain; the previous one is automatically demoted.
Fallback default domain behavior
Other domains are not redirected. A page can be attached to several domains, so the same funnel can run on several domains for different markets or brands. Each domain sends its order and recall emails under its own store name and sender, through its own provider; see Domains.
Attaching pages to domains
A page is served only on the hosts it is attached to (the request Host header, without port). An unregistered host, and the admin host’s /storefront/ path, serve no pages and show a coming-soon page. There is no fallback.
- The create-page modal and the page Settings panel have a domain multi-select. Create defaults to the fallback default domain. A page with no domain shows “No domain” and is not served.
- A domain’s Pages tab (Pages → Domains, then click the domain) lists the pages attached to that domain, with the same columns, filters and actions as the main page list; click a page to open it in the editor. To attach or detach a page, use the domain multi-select in that page’s Settings.
- Pages can only be created once at least one domain exists.
- A page’s own URL uses its default domain, else the fallback default domain if attached, else the earliest attached one.
- Every page with domains has exactly one default domain. It is the current default, else the fallback default domain, else the earliest attached, and is chosen again when the default is detached or deleted. Page uploads (editor, media fields, AI generation, page import) use the default domain’s storage and static base; see Domains. The page API and MCP accept
defaultDomainId, and the page response listsdomains[].isDefault. - A slug is unique per domain. Reusing one fails with
Slug "<slug>" is already used on <host> by page "<name>". - Locally, add a domain such as
shop.localhostand browse it; a host must contain a dot.
Funnels across domains
- The funnel launch URL uses the landing page’s domain (else the checkout page’s).
- The landing page and checkout page may be on different domains. The visitor identity is carried across as
anid, only to your own domains. - Every upsell, thank-you and error page must be attached to every domain of every checkout page in the funnel, otherwise saving fails with
Step "<page>" must be on every domain of checkout "<checkout>"; missing: .... - A/B variant pages must be attached to every domain of the entry page.
- Recall emails are not sent for a checkout page that has no domain.
Payment accounts
Each domain binds its own payment accounts on its Payment tab; see Domains.
Upgrading
Run npx autonnel pages:backfill-domains once after db push and before you deploy the new build, so no request is served while pages have no domain. It attaches every existing page to every existing domain; a deployment with no domain gets its pages attached when you add the first one. Run it again after upgrading to a version with default domains: it sets each page’s default domain, and on every run it repairs pages that lack one.
DNS configuration
Point each custom domain to your autonnel deployment by creating a CNAME record:
shop.example.com. CNAME your-autonnel-deployment.example.com.
Replace your-autonnel-deployment.example.com with the hostname of your Node.js server, Cloudflare Worker, or other deployment target.
If you use Cloudflare as your DNS provider, you can enable the Cloudflare proxy (orange cloud) for DDoS protection and edge caching. In Workers deployments, your custom domain must be routed through Cloudflare.
Domain verification (Cloudflare for SaaS) is a SaaS-only feature and is not available in the open-source edition.
TLS
autonnel does not issue or renew TLS certificates. You are responsible for obtaining a certificate for each custom domain. Common options:
- Cloudflare — enables automatic TLS when you proxy the domain through Cloudflare (recommended for most deployments).
- Caddy — automatically provisions Let’s Encrypt certificates when used as a reverse proxy in front of your Node.js server.
- Your hosting provider — most managed platforms (Fly.io, Railway, Render) can provision certificates for custom domains automatically.
Static and CDN domain
The static domain controls the hostname used for serving static assets (uploaded images, imported page assets, etc.). Autonnel uses this domain when rewriting asset URLs during HTML page imports.
If no static domain is set, autonnel defaults to static.<root domain>. For example, if the domain is shop.example.com, the default static domain is static.example.com. Each domain can override the static subdomain or use its own bucket under its Storage button.
Configure your S3 bucket, CloudFront distribution, or Cloudflare cache to serve from this domain. The domain must resolve to your storage origin.
To set a custom static domain:
- Go to Settings → Storage.
- Enter the value in the Static domain field.
- Save.
Example: two-domain setup
Fallback default: shop.example.com → autonnel deployment
Other domain: www.example.com → autonnel deployment (no redirect)
Static domain: static.example.com → S3 / CloudFront origin
Pages attached to both shop.example.com and www.example.com are served on both. Images and assets are served from static.example.com.
Caveats
- No wildcard domain support in OSS. Each subdomain must be explicitly added. Wildcard routing (e.g.
*.example.com → any deployment slug) is a SaaS-only capability. - Domain verification is SaaS-only. The Cloudflare for SaaS domain verification flow is not included in the open-source edition.
- TLS is not managed. autonnel does not provision certificates. A missing certificate causes browser TLS errors that autonnel cannot detect or surface to the admin.
- Static domain must resolve independently. Autonnel writes the domain into asset URLs but does not configure the DNS record or CDN distribution on your behalf.
Related
- Storage settings — S3 configuration and static domain
- Domains: email and branding - store name, logo, favicon and email sender per domain
- Domains - managing the domain list in the admin UI