DNS, CDN, DDoS protection, edge functions — the layer in front of your site.
Cloudflare's free tier handles DNS, CDN, and DDoS protection for most production sites. For an exported InBuild project, you typically deploy the app to Vercel/Netlify/etc., then point Cloudflare at your domain for caching, security headers, and Workers if you need edge logic.
What you get
FAQ
Do I need Cloudflare if I host on Vercel?
Not for the basics — Vercel handles its own CDN and TLS. People still use Cloudflare in front of Vercel for: stricter DDoS controls, page-level caching rules, custom security headers, or to consolidate DNS with their other services.
Can I deploy an InBuild export directly to Cloudflare Pages?
Yes. Cloudflare Pages supports Next.js (via `@cloudflare/next-on-pages`). The exported `next.config.ts` may need a small tweak for the Cloudflare runtime — Cloudflare's docs walk through it.
How does Cloudflare affect SEO?
Positively — faster TTFB from the CDN, automatic Brotli compression, and HTTP/3 support all help Core Web Vitals. Just don't aggressively cache HTML for pages that need to be fresh (Cloudflare's default is to respect your origin's cache headers, which Next.js sets correctly).