Appearance
Custom domains
Instead of sharing the default /p/<projectId>/<fileId> link, you can attach your own hostname — like hello.acme.com — to a project. This page covers adding a hostname, proving you own it with a DNS record, and what happens after verification.
How it works
Attaching a domain is a three-step handshake: you add the hostname, FlowRunner hands you a DNS record to create, and once that record is live it verifies ownership.
Add a hostname
Add the hostname you want to use to the project's domains. FlowRunner normalizes it first — lowercasing it, trimming whitespace, and dropping any trailing dot or :port. It must be a syntactically valid public hostname: it needs at least one dot, can be at most 253 characters, and each label may contain only letters, digits, and hyphens (not starting or ending with a hyphen).
A hostname can only belong to one project at a time. If the name is already claimed, the request is rejected so two projects can never fight over the same address.
Adding a hostname requires editor access.
Create the verification record
When you add a hostname, FlowRunner generates a random token and returns the exact DNS record to create:
| Field | Value |
|---|---|
| Type | TXT |
| Name | _flowrunner.<your-hostname> |
| Value | flowrunner-verify=<token> |
For example, adding hello.acme.com gives you a TXT record named _flowrunner.hello.acme.com with a value like flowrunner-verify=3f9a.... Create that record at your DNS provider exactly as shown.
NOTE
DNS splits long TXT values into 255-character chunks. FlowRunner joins the chunks back together before comparing, so you never have to worry about how your provider stores the value.
Verify
Once the record is in place, press Verify. FlowRunner looks up the _flowrunner.<hostname> TXT record and checks that one of its values matches your token. On a match, the domain is marked verified with a timestamp.
If the record is not found yet — a fresh DNS change, or one that has not propagated — verification simply reports "not verified" and returns a hint reminding you to add the record and try again. It is not an error; DNS changes can take a few minutes to go live, so wait and retry.
TIP
If verification keeps failing, double-check that the record name is _flowrunner.<hostname> (not the bare hostname) and that the value starts with flowrunner-verify=.
After verification: serving the domain
Verification proves you control the hostname. It does not, by itself, start serving your project at that address.
Pointing the hostname's traffic at your FlowRunner deployment is an operator / edge-routing step — done at your reverse proxy, CDN, or hosting platform, not inside the app. The verified flag is the signal that a hostname is cleared to route; wiring the actual routing is part of running the deployment. See self-hosting for where that fits.
Removing a domain (also editor-only) deletes the record; you can re-add and re-verify it later if needed.