Every app gets a public web address out of the box, and you can put your apps on a domain you own. This page covers all of it: your free FlowFn address, serving an asset at the address root, a custom domain with automatic HTTPS, and a subdomain for each playground.

Your free FlowFn address

Every app claims a subdomain at creation, so your public forms, visualizers, playgrounds, and agents have a clean, branded address from day one — for example acme.flowfn.com/f/<slug>. Subdomains are unique across FlowFn, and a short list of reserved names can't be claimed. Change it any time from the app's Public hosting settings.

Serve an asset at the address root (site root)

By default assets sit under a prefix (/p/<slug>, /f/<slug>, …). Pick a site root in the app's settings to serve one asset at the bare root instead — a playground bound as the site root answers at acme.flowfn.com/, and its pages at acme.flowfn.com/<page>, with no /p/ prefix.

Custom domains

On a plan that includes custom domains, serve your app on a domain you own — app.acme.com or acme.com — with automatic HTTPS. In the app's Public hosting settings:

Enter your domain and save.
At your DNS provider, add the CNAME record shown. Because a root/apex domain (acme.com) can't take a CNAME at most providers, the panel offers two tabs:
- Other providers — add the CNAME on www (every provider allows a CNAME on a subdomain). Your site serves at www.acme.com; add a registrar redirect (acme.com → https://www.acme.com) to open the bare root too.
- Cloudflare — add the CNAME on the root @. Cloudflare flattens it, so the bare acme.com serves directly. Set the record to DNS only (grey cloud), not Proxied.
The status moves Provisioning → Active as DNS propagates and we issue the certificate — usually a few minutes. Pointing either the root or the www host activates it. We obtain and renew the TLS certificate for you.

Releasing the domain (clearing it, or deleting the app) frees it. We may release a domain that breaches our Acceptable Use Policy — for example, one used to impersonate a brand.

A subdomain for each playground

Once your app has a custom domain, your root playground serves at the domain itself (acme.com) and every other playground can take its own subdomain of it. Label a playground and it serves at <label>.acme.com — for example shop.acme.com or pricing.acme.com — at that subdomain's own root, with HTTPS issued automatically.

Open the playground, then Home page settings → Public subdomain.
Enter a label — lowercase letters, digits, and hyphens; not a reserved name (www, api, …). It has to be unique within the app.
Add the CNAME shown for <label>.your-domain.com at your DNS provider — the same target as your app domain. HTTPS is issued automatically.

The site-root playground keeps the apex and can't also take a subdomain. Each subdomain is its own independently-indexable site — turn on SEO and a sitemap for it from its Home settings. Releasing the app's custom domain clears every playground subdomain under it.

Site verification

To connect your site to Google Search Console, Bing Webmaster Tools, Yandex, Pinterest, Facebook/Meta and others, add a verification in the app's Site verification settings. Pick a provider and one of three methods:

Meta tag — paste the content value the provider gives you; FlowFn adds the <meta> tag to your site's <head>. Works for any provider (choose Custom to enter your own tag name).
HTML file — paste the token; FlowFn serves the provider's file (e.g. google<hash>.html, BingSiteAuth.xml) at your site root automatically — nothing to upload.
DNS TXT record (custom domains) — add the shown TXT record at your registrar, then press Check DNS records to confirm it's live. A *.flowfn.com subdomain can't use DNS (you don't control that DNS) — use the meta-tag or file method there.

Verification tags and files appear only on your app's subdomain and custom domain — never on flowfn.com. They also render while a page is set to no-index: verifying ownership is separate from allowing indexing.

Plan & search visibility

Custom domains and per-playground subdomains are unlocked by the same plan feature — see Billing and Plans. A site is indexable by search engines only when it's served on its own host (your app subdomain, custom domain, or a per-playground subdomain); under flowfn.com/p/<slug> a playground is always kept out of search, so your SEO never affects flowfn.com and vice-versa.