Skip to main content
Domains

Domains

Connect custom domains to Easel projects and manage DNS, HTTPS, and routing.

Every Easel project receives an Easel-provided URL. You can also connect custom domains such as example.com, www.example.com, or docs.example.com.

A custom domain gives users a stable address for your application while Easel manages how requests reach the project's current production deployment.

Domain concepts

A domain setup has several independent parts:

  • Registration determines who owns the domain
  • DNS tells clients where to send requests
  • Project assignment tells Easel which project should receive the request
  • TLS secures requests over HTTPS
  • Deployment routing determines which deployment serves the request

Changing one part does not necessarily change the others. For example, assigning a domain to a project does not update DNS at your provider.

Supported domain types

TypeExampleDNS record
Apex domainexample.comA record to Easel edge IPs
Subdomainwww.example.comCNAME to cname.easelusercontent.com
Nested subdomainapp.eu.example.comCNAME to cname.easelusercontent.com

Wildcard domains such as *.example.com are not supported. Add each hostname you need.

The exact record values appear when you add the domain in the dashboard.

How domain setup works

A typical setup follows this sequence:

  1. Add the domain to an Easel project
  2. Configure the DNS records shown by Easel
  3. Wait for Easel to detect the records
  4. Allow Easel to provision a TLS certificate
  5. Test the domain over HTTPS
  6. Configure a canonical-domain redirect when needed

Adding a domain does not create a new deployment. The domain routes to the project's current production deployment.

Guides in this section

Domains and deployments

Custom domains belong to projects, not individual deployment artifacts. They follow whichever Production deployment is current.

See Domains and deployments for production assignment, promotion, rollback, and domain-routing behavior.