Attach a custom domain to a free Cloudflare deploy, from an app, not a dashboard

You can put your own domain in front of a free Cloudflare Workers deploy without wading through a DNS dashboard. ReDock — a free-while-in-alpha native macOS app — attaches a custom domain to your deployed site from inside the app, and the free tier includes one custom domain attached at a time. Your site still serves from Cloudflare’s free static tier; the domain just gives it a branded address instead of a Workers URL.

Why the dashboard route is a pain

Attaching a domain to an edge deploy normally means: log into your registrar, find DNS settings, add or edit records, get the target exactly right, then wait and hope propagation went the way you expected. One typo in a CNAME and you’re debugging why the site resolves to nothing.

ReDock moves that into the app. After you deploy to Cloudflare Workers, you attach the domain in-app, and ReDock handles the wiring against your connected Cloudflare account. You’re not hand-editing records in a separate tab and guessing.

The in-app flow

Assuming you’ve already deployed — see deploy a website for free if not — here’s the domain step:

Deploy the site to Cloudflare Workers. You get a real, public, HTTPS Workers URL immediately. The deploy docs cover the connect-and-ship loop.
Attach your domain in-app. Point ReDock at the domain you own and it configures the attachment through your Cloudflare account.
Serve from the branded address. Once it’s live, visitors reach your site at your own domain over HTTPS, still on Cloudflare’s free static tier.

The build itself doesn’t change — ReDock builds with its own runtimes and reports the commit hash and duration, domain or not.

What the free tier includes — precisely

Here’s the honest boundary so nothing surprises you:

One custom domain attached at a time on ReDock’s free early-access tier. You can attach a domain, and if you want to move it to a different site later, you detach and reattach — one live attachment at a time.
The domain itself isn’t free. You buy the name from a registrar; a .com costs money everywhere. ReDock attaching it is free; owning it isn’t. Without a domain, your site simply lives on its Workers URL — real and public, just not branded.
Hosting stays on the free static tier. Attaching a domain doesn’t push you into a paid plan. Cloudflare serves your static assets on the free tier regardless of the address. The honest Cloudflare free-tier guide covers where that tier’s edges are.

When you don’t need a custom domain yet

A custom domain is for finished, public sites you want branded. Plenty of work doesn’t need one:

Sharing in-progress work? Use a tunnel instead of deploying. Show a client a WIP site covers QuickShare, which gives you a real redock.xyz URL with zero DNS.
Just need it live and free? The default Workers URL is already public and HTTPS. Add the domain when the project is ready to wear its own name.

The stacks docs list what ReDock builds and deploys, so you know your framework is covered before you get to the domain step.

FAQ

How many custom domains can I attach for free?

One at a time on ReDock’s free early-access tier. You can detach and reattach to move it between sites, but one live attachment is included free.

Does attaching a domain cost me the free hosting tier?

No. Your site keeps serving static assets from Cloudflare’s free tier. The domain changes the address, not the plan. You do pay a registrar for the domain name itself.

Do I have to edit DNS records myself?

No. ReDock attaches the domain from inside the app against your connected Cloudflare account, so you’re not hand-editing CNAME or A records in a dashboard.

Ready to give a free deploy its own name? Download ReDock to ReDock and attach your domain in-app.