Domains and deployments

Custom domains are assigned to projects and route to the project's current Production deployment.

Adding or removing a domain changes routing configuration. It does not create or modify a deployment artifact.

For DNS, TLS, verification, redirects, and migration, see Domains.

Domain assignment model

The relationship is:

Custom domain
      ↓
Easel project
      ↓
Current Production deployment

Custom domains cannot be assigned to Preview deployments or Git branches. Preview traffic uses generated Easel hostnames. See Deployment URLs.

Production deployment versus current deployment

A Production deployment is built using Production configuration.

The current deployment is the Production deployment receiving traffic from:

• The project's Easel-provided production URL
• Custom domains assigned to the project as content hosts

A Production deployment may be Ready without being Current when Auto-assign production domains is off. See Environments.

New production deployments

When automatic production assignment is enabled:

1. The existing current deployment continues serving domains
2. Easel creates and builds the new Production deployment
3. The new deployment reaches Ready
4. Easel updates project-domain routing
5. The previous deployment remains in deployment history

A failed or canceled deployment does not change domain routing.

Promotion

Promoting an existing Ready Production deployment updates project-domain routing without changing DNS and without rebuilding.

DNS maps the hostname to Easel. Promotion changes Easel's internal routing target.

See Promoting deployments.

Rollback

Instant Rollback reassigns project domains to a previous Ready Production deployment.

Rollback does not require DNS changes and does not rebuild the deployment.

See Rolling back deployments.

Adding a domain

When a domain is added to a project with an existing current deployment, it begins routing to that deployment after:

• DNS is correctly configured
• TLS is ready
• Easel activates the assignment

Adding the domain does not trigger a new build.

Removing a domain

Removing a domain detaches it from the project. It does not delete deployments and does not affect other project domains.

When DNS still points to Easel, an unassigned domain returns a not-found response rather than another customer's project.

Domain redirects

A domain configured as a redirect does not invoke the deployment's application output. Easel handles the redirect before WAF, cache, and functions.

Both the source and destination hostnames still require valid domain configuration and TLS.

See Domain redirects.

Cache behavior

Promotion and rollback do not automatically purge ISR or runtime caches.

Caches are keyed by deployment ID, so traffic to the newly Current deployment uses that deployment's cache namespace. Edge responses follow the newly aliased deployment's routes and assets.

Domain routing changes and cache invalidation are separate operations.