*.on.getfloo.com. You can add your own domain with automatic SSL.
Add a domain
Configure DNS
Add both records shown byfloo domains add at your DNS provider:
For apex domains (e.g.,
example.com without www), use your provider’s CNAME flattening or ALIAS record feature.
The traffic record routes requests to floo. The per-domain TXT token proves that
the current claimant controls DNS, even if an old record already points at floo.
Verify DNS
Once both records are in place, verify ownership from the CLI or the dashboard:_floo-verify TXT token. Once verified:
- Domain status changes to active
- SSL is provisioned automatically
- Org admins receive a confirmation email
DNS changes can take up to 24 hours to propagate, but most providers update within minutes.
Confirm control of an existing active domain
Domains activated before claimant-specific TXT proof was introduced stay live. The dashboard andfloo domains list mark these domains as reproof required
and show the TXT value to publish.
Add that TXT record, then run:
Check status
Per-service custom domains
For multi-service apps, you can bind a custom domain to a specific service by addingdomain to floo.app.toml:
--services to bind it to the service, and configure DNS:
A custom domain on a service overrides path-prefix routing — traffic to
api.example.com goes directly to the api service. The app’s access_mode still applies on the custom domain.