From .test to the edge: one-click Cloudflare deploys
Local sites are drafts. Here's how ReDock turns a running local build into a Cloudflare deployment with your own domain attached, without leaving the app.
A local site is a draft. At some point it has to leave your machine — and that’s historically where the terminal came back: tokens in dotfiles, CLI installs, DNS spelunking.
ReDock folds the whole exit lane into the app, on Cloudflare rails.
Connect once, calmly
Connecting your Cloudflare account happens with a prefilled token template — the app sends you to Cloudflare with exactly the scopes it needs (and none it doesn’t), you approve, paste once, and the token lives in your macOS Keychain, not a config file.
Deploy in one verb
For a static or built site, Deploy means: ReDock runs your build pipeline on its own runtimes, pushes the output to Cloudflare, and reports the deployment with the commit hash it came from — deploy 8aa2e9e ✓ · 12s. If the build fails, you see the real log, not a spinner.
Your domain, attached in-app
The last mile is the domain. ReDock can attach a custom domain to the deployment from inside the app — and until you’re ready for that, every site can hold a redock.xyz subdomain or an unlisted QuickShare URL for client previews.
Free tier ships with unlimited QuickShare, three named subdomains, and one custom domain at a time. The pricing section has the current shape.