Custom domains

What you get

• Any app on an address you own
• Subdomains and bare domains
• Two DNS records to create
• An HTTPS certificate issued on verification
• No redeploy needed
• The whisk.page address keeps working

How it works

whisk domains add prints two DNS records: a TXT record that proves you own the name and a CNAME record that points it at the app. A bare domain such as yourcompany.com cannot have a CNAME, so it uses A and AAAA records instead. Once the records exist, whisk domains verify checks them and names any that are missing.

On verification, Caddy, the open-source web server in front of every app, obtains an HTTPS certificate from Let's Encrypt. The app answers on the new name straight away, with no redeploy. Certificates are only issued for names that have been verified.

The app sees the name the visitor used, so links within it should be relative. To put every app on your domain with one set of records, use a business-wide domain instead.

Example

A tool hire company moves its customer booking portal to bookings.harbourtoolhire.com. Its office manager adds the two records at the company's DNS provider, and the portal answers on the new name once they are verified. Links to the old whisk.page address keep working.

For your coding agent

whisk domains add <domain>
whisk domains verify <domain>

Pass the printed records to the person who manages the domain's DNS, then verify. The commands are in the CLI reference.