Edge setup without Cloudflare

Overview

If you don't use Cloudflare you don't need a worker. RenderBeam runs an edge of its own at *.edge.renderbeam.com that does the same bot detection, caching, and origin pass-through.

How it works

1. You CNAME your domain (or a www. subdomain) to yourdomain.edge.renderbeam.com.
2. Our edge terminates TLS, looks up your project by hostname, and:
   - bot → serves the cached pre-rendered HTML (or renders fresh on miss)
   - human → passes through to your real origin
3. Fail-open: if anything goes wrong, traffic falls through to your origin.

The dashboard detects Vercel and Netlify automatically and posts the required JSON to their respective APIs to set up the host header — you only need to add the CNAME.

Vercel

1. Project → Settings → Domains → add your domain.
2. When Vercel asks for the CNAME target, enter yourdomain.edge.renderbeam.com.
3. In the RenderBeam dashboard, paste your Vercel deploy URL as the origin URL so we know where to fetch un-rendered content.

Netlify

1. Site configuration → Domain management → add custom domain.
2. CNAME target: yourdomain.edge.renderbeam.com.
3. Set your Netlify site URL as the origin in the RenderBeam dashboard.

Other platforms

Anywhere you control DNS works:

1. Add a CNAME from your apex (or www.) to yourdomain.edge.renderbeam.com.
2. Set the origin URL in the dashboard to the URL where your real origin lives (e.g. myapp.fly.dev).
3. We handle TLS at the edge.

Verify

curl -A "Googlebot" -I https://yourdomain.com

You should see X-Cache-Status and X-Rendered-By: RenderBeam. A normal browser request will pass through to your origin unchanged.