TL;DR
To put a custom domain on an app Claude built, declare it in floo.app.toml, release to prod, and publish two CNAME records: the host to edge.getfloo.com, and _acme-challenge to the target floo prints. floo issues the certificate and starts serving, usually within minutes of DNS resolving.
- The domain lives in config, so Claude can set it up.
- Custom domains serve the prod environment.
- Sign-in rules apply on the custom domain too.
Every floo app starts at https://<app>.getfloo.app, which is fine for a team tool. When the app goes in an email to customers, or the team wants tools.yourcompany.com, you add a domain. It takes two DNS records and no certificate work.
1. Ask Claude to add the domain
Add the custom domain tools.yourcompany.com to this floo app and tell me the DNS records to publish.
Claude adds this to floo.app.toml:
[domains."tools.yourcompany.com"]
service = "web"
2. Release to prod
A custom domain serves the prod environment, so the app needs a prod release. Commit and push, wait for the dev deploy to go live, then:
gh release create v1 --repo your-org/your-app
For an app without a GitHub repository, floo promote --app my-app does the same. The prod deploy output shows Custom domain waiting on DNS with the records.
3. Publish two records
floo domains show tools.yourcompany.com --app my-app
| Purpose | Type | Name | Target |
|---|---|---|---|
| Traffic | CNAME | tools.yourcompany.com | edge.getfloo.com |
| Certificate | CNAME | _acme-challenge.tools.yourcompany.com | The target floo prints |
Then wait for it:
floo domains watch tools.yourcompany.com --app my-app
floo checks every minute. When the certificate is active and traffic resolves to the edge, the host serves and org admins get an email.
Things that trip people up
- Turn off DNS proxying for both records. A proxied record points at the proxy, not floo, and the domain never activates.
- Don't type the zone twice. Some providers add
yourcompany.comto the name for you. - Django needs the host allowed. Read
DJANGO_ALLOWED_HOSTSintoALLOWED_HOSTS, as in the Python deploy post, then set it for prod before the release in step 2, since a running revision doesn't pick up new values:floo env set DJANGO_ALLOWED_HOSTS=tools.yourcompany.com --app my-app --env prod. - Root domains use an ALIAS, ANAME, or A record for traffic. See custom domains.
To remove a domain, delete its block and release. floo keeps the certificate for 7 days in case you change your mind. For getting the app live in the first place, see how to deploy an app built with Claude Code.
Frequently asked questions
How do I put a custom domain on an app Claude built?
Add a [domains."app.yourcompany.com"] block to floo.app.toml, release the app to prod, and publish the two CNAME records floo prints: one for traffic to edge.getfloo.com and one for the certificate. floo activates the domain once both resolve.
Does floo handle HTTPS for a custom domain?
Yes. floo issues and renews the certificate. Keep the _acme-challenge CNAME in place so renewal keeps working.
Can I use a root domain like example.com?
Yes. Use an ALIAS or ANAME record to edge.getfloo.com, or an A record to the address in floo's custom domain docs, in place of the traffic CNAME. The certificate record stays a CNAME.