Business-wide domain

What you get

• Every app at its own name on your domain
• New apps added with no further DNS work
• One TXT record and one wildcard CNAME
• An HTTPS certificate for every app's address
• Existing records such as www and mail keep working
• Works on a subdomain such as apps.yourcompany.com too

How it works

An owner or admin adds the business's domain once. Whisk answers with two DNS records: a TXT record that proves ownership and a wildcard CNAME, *.yourcompany.com, that points every unused name at Whisk. Records the business already has, such as www and mail, keep working, because an exact record takes priority over a wildcard.

After verification, every live app answers at its own name on the domain, such as crm.yourcompany.com, and apps created later get an address there too. Each address gets its own HTTPS certificate from Let's Encrypt, obtained by Caddy, the open-source web server in front of every app.

Previews stay on their whisk.page address. Each business can have one domain of this kind, and removing it leaves every app's other addresses in place. Sending email from the domain is set up separately, under transactional email.

Example

A commercial roofing contractor adds northpeakroofing.com for its quoting, job scheduling and safety checklist apps. After one set of DNS records they answer at quotes.northpeakroofing.com, jobs.northpeakroofing.com and checks.northpeakroofing.com. A fourth app added later needed no DNS change at all.

For your coding agent

whisk domains business add <domain>
whisk domains business verify
whisk domains business show

These commands need an owner or admin signed in. They are in the CLI reference; a single app on its own name uses a custom domain.