Deploy to Cloudflare Workers free tier: the honest guide
What the Cloudflare Workers free tier actually covers for static sites, and how to deploy to it from an app without touching a dashboard.
You can deploy a static website to Cloudflare Workers’ free tier with no credit card and no server, and this guide is honest about what that tier does and doesn’t cover. The short version: static assets — HTML, CSS, JS, images — serve from Cloudflare’s edge on the free plan, and for a portfolio, blog, docs site, or side project you’re very unlikely to hit the ceiling. ReDock, a free-while-in-alpha native macOS app, handles the build and deploy in one click and reports back with the commit hash and duration.
What the free tier actually covers
Let’s be careful here, because the free tier is real but bounded, and inventing numbers would be dishonest.
Cloudflare Workers serves static assets on its free plan. Getting started doesn’t require a card. There’s a monthly request allowance and it’s generous enough that ordinary static sites stay comfortably inside it — Cloudflare publishes the exact figures, and they can change, so check their pricing page rather than trusting a number in a blog post. The durable truth: if your site is static output served to normal traffic, the free lane fits.
What lives outside the free static lane is dynamic, per-request server logic at scale — heavy compute on every request, large persistent storage, and so on. Those touch paid Workers features. A static build doesn’t.
Deploying without a dashboard
The usual Cloudflare deploy involves Wrangler config, account IDs, and a fair amount of setup. ReDock collapses that:
- Connect your Cloudflare account once, from inside the app. The deploy docs cover the token setup.
- Build with real runtimes. ReDock runs the actual build — the same Node, Bun, or PHP it uses to run your site locally — and produces the static output. No separate CI.
- Deploy in one click. The output goes to Cloudflare Workers static assets.
- Read the honest report. You get the commit hash it built from and how long it took. A failed build says so; it doesn’t resolve to a green checkmark regardless.
No YAML, no SSH keys, no pipeline to maintain. The stacks docs list what ReDock can build.
What to deploy this way (and what not to)
Static deploys cover more than people assume: marketing sites, blogs, docs, portfolios, landing pages — anything a static site generator emits, from Astro or Next.js on down.
What doesn’t fit the free static tier directly:
- Live database queries per request. WordPress needs PHP and MySQL at request time, so it isn’t a static deploy. The workaround: run WordPress locally in ReDock as your editor, build a static front end, and deploy that. Deploy a website for free covers the headless pattern.
- Always-on dynamic apps. If every request runs server code, you’re past the static tier.
For sharing local work rather than deploying, tunnels are the right tool — see free staging environments and attaching a custom domain for the branded-URL step.
Keeping “free” honest
Two things must be free for this to add up. The hosting: Cloudflare’s static free tier, no card to start. The tooling: ReDock is free, and the build-and-deploy loop is on the free side. Shipping static output to Cloudflare doesn’t depend on a plan.
The one thing you may pay for is a domain name — a .com costs money at any registrar. Without one, your site lives on a real Workers URL: public, HTTPS, just not branded.
FAQ
What are the exact Cloudflare Workers free-tier limits?
Cloudflare publishes them and they change over time, so check their current pricing page. In durable terms: static assets serve on the free plan with a generous monthly request allowance that ordinary static sites rarely approach.
Do I need a credit card?
No. Cloudflare’s free tier for Workers static assets doesn’t require a card to get started, and ReDock connects to your account from inside the app.
Can I deploy a Next.js or Astro site this way?
Yes. ReDock builds the static output with its own runtimes and deploys it to Cloudflare Workers. WordPress needs the headless pattern — run it locally, deploy a static front end.
Ready to ship to the edge without a bill? Download ReDock to ReDock and deploy your first static site.