Autonnel v0.1.0
Get started

Multi-domain

Bind multiple custom domains to one autonnel deployment. Shopify-style domain table.

A single deployment can have multiple domain names. Exactly one domain is marked isPrimary. All domains serve the same set of pages.

Domain fields

Each domain has:

  • Host — the domain hostname, e.g. shop.example.com.
  • isPrimary — boolean; exactly one domain per deployment should be primary.

Adding a domain

  1. Go to Settings → Domains.
  2. Click Add domain.
  3. Enter the hostname (e.g. shop.example.com).
  4. Check Primary if this is your main domain.
  5. Click Save.

You can add as many domains as needed. To change the primary domain, mark another domain as primary; the previous primary is automatically demoted.

Primary domain behavior

Non-primary domains can optionally redirect visitors to the primary domain. Whether this redirect is active depends on your deployment configuration. If you run the same funnel on multiple domains for different markets and do not want cross-domain redirects, leave the redirect behavior disabled.

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.<primary domain>. For example, if your primary domain is shop.example.com, the default static domain is static.shop.example.com.

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:

  1. Go to Settings → Storage.
  2. Enter the value in the Static domain field.
  3. Save.

Example: two-domain setup

Primary domain:    shop.example.com   → autonnel deployment
Secondary domain:  www.example.com    → autonnel deployment (no redirect)
Static domain:     static.example.com → S3 / CloudFront origin

Both shop.example.com and www.example.com serve the same pages. 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.