AutoKaam Playbook

Cloudflare Pages, the Empire Static Hosting I Have Never Regretted

Free static hosting, fast global edge, and the autokaam.com deploy backbone.

Last reviewed:

The operator take

Every static empire site sits on Cloudflare Pages. Autokaam.com, papersadda.com, recontraceai, calcnook, kaam-tracker landing, the lot. Free hosting, free SSL, global CDN, GitHub-driven deploys, custom domains for free, unlimited bandwidth at the entry tier. It is the most asymmetric deal in static hosting in 2026.

The pattern: push to main on GitHub, GitHub Actions builds (Next.js static export for autokaam, Eleventy for kaam-tracker landing, plain HTML for some), and a final step deploys via wrangler-action or the Pages REST API. SSL via Cloudflare CA. Custom domain via the same Cloudflare zone (the registrar pricing is also competitive).

What I deliberately do not use: Vercel. The reason is the same as Coolify; Vercel pricing scales with image optimization counts and edge function invocations, both of which can spike unpredictably. Cloudflare Pages does not meter the equivalent. The image optimization on Pages is weaker than Vercel's, but I have never needed it (autokaam ships pre-rendered Satori OG cards as static PNGs, no transform needed).

The trade-off I accepted is that the build runtime is less generous than Vercel's. A Pages build is capped at 20 minutes; long Next.js exports of larger sites can brush against this. The empire workaround is to keep the static export's pre-rendering work on a self-hosted CI runner (or in Coolify) and only do the upload from Pages. Fine.

The 2026 thing to watch is Cloudflare's continued integration of Pages with Workers (now under one Workers Platform). The empire pattern is converging on "Pages for static, Workers for dynamic, R2 for storage", all on Cloudflare, all under one bill.

The Indian-operator angle: Cloudflare's support for Indian regulatory requirements (the data localization rules that bit Vercel and other US-only vendors) is the cleanest in the global CDN tier. Plus the registrar pricing for .in domains and the DNS-level WAF (which I run on autokaam.com to block scrapers) makes this a genuine empire moat.

If you are starting a static site in 2026 and reaching for Vercel out of habit, you are paying a tax that buys you nothing the empire has missed.

Why it matters in 2026

Static sites remain the cheapest, fastest, and most secure way to ship marketing pages, blogs, and small apps. Cloudflare's edge is materially faster than the competition for India-region traffic, and the pricing model does not punish you for having visitors. The 2025-26 static-site comeback (Astro, Next.js export, fresh Hugo activity) is partly because of this.

Cost in INR

Free at entry; Pro from Rs 2,000/mo (only needed for advanced WAF / analytics)

Use when

  • +Marketing sites, blogs, documentation
  • +Static-export Next.js / Astro / Eleventy sites
  • +JAMstack apps with API calls to Workers or external endpoints
  • +When SSR is not strictly required

Skip when

  • xHeavy SSR with per-request server logic (Workers wins, or self-host)
  • xApps requiring database access at request time without an edge tier
  • xWhen build time consistently exceeds 20 minutes

Alternatives I would consider