Wildcard Domains Are Now Supported

Agiler now supports wildcard custom domains. Add a domain such as *.example.com to a project, and any matching subdomain—including store.example.com, docs.example.com, or one you create later—will route to that project automatically.

Wildcard domains include automatic HTTPS. When you add one from your project’s Domains page, Agiler shows the two CNAME records needed for traffic and certificate validation. Keep both records in place so Agiler can renew the certificate for you.

A wildcard covers one subdomain level, but not the root domain or deeper names. For example, *.example.com covers shop.example.com, but not example.com or preview.shop.example.com. Add the root domain separately if you need it. Wildcard domains cannot be selected as the project’s primary site domain, but you can add the exact domain used for the site domain, even if it overlaps the wildcard domain.

Wildcard domain support is available now in the dashboard, REST API, and MCP server.