ReDock + Cloudflare

The internet, routed to your computer.

When a site goes live, a Cloudflare tunnel carries the traffic to the site running on your computer; nothing is copied anywhere. When you deploy a headless build, it goes to Cloudflare's edge with a token scoped to exactly that.

Free · works with Cloudflare as Cloudflare · official marks, interoperability only
What ReDock does with it

The network behind your links.

Share links name.redock.xyz and quick links are tunnels. Stop sharing and the address goes dark; the site keeps running.
One-click deploy Built headless sites push to Cloudflare; hash and duration reported; custom domain attached from the app.
Scoped tokens, stored by your system ReDock asks for a token with exact permissions and keeps it in your system credential store.
Plainly

ReDock uses Cloudflare's network; it is not a Cloudflare product and makes no uptime claim beyond what your connection gives it.

Build it in an afternoon

Your own domain on a local site

Three steps, one window, receipts for the parts the agent did.

  1. 01Sharing → Named link → claim a name.
  2. 02Custom domain → add the two DNS records the app shows you.
  3. 03Wait for the green pill; open your domain; it is your computer answering.
ReDock

Calm ships tonight.

Download ReDock, berth your first site, and watch the AI work, receipts and all. Five minutes, no terminal.

Free · macOS and Windows · your sites stay on your machine