Every project is born on a free address — <project>.weaveflowapp.com, HTTPS
included — and that address stays live when you attach your own domain. A
mistyped DNS record can never lock you out of your app.
Which record you will create
The Domains tab shows one row per public surface, and the record depends on how the project is hosted:
- A server app has two surfaces (web and api) and takes A records pointing at your box’s IP.
- A static site has one surface and takes a CNAME to Cloudflare Pages — its server only builds; nothing is served from that machine’s IP.
You do not need to work this out: the tab shows the exact record to create for your project, host and value included.
Attach it
Add the domain to the surface
Enter the domain on the surface’s row. For a static site, saving takes effect immediately — the DNS record on the Cloudflare side is created for you, no redeploy, and an apex domain automatically includes
www. For a server app, each host gets exactly the A record you create — addwwwyourself if you want it.Create the record at your DNS provider
Copy the record the tab shows into your registrar or DNS host. This is the one step that happens outside Weaveflow.
Verify
Verify reports what was actually found against what was expected — so a typo shows up as “expected X, found Y”, not a silent failure. Certificates are issued automatically once the record resolves.