Vercel templates on Cloudflare

Vercel templates, rebuilt for Cloudflare.

57 of Vercel's templates, ported to Cloudflare Workers. A build creates a repository you own, provisions what the app needs with Terraform, and deploys it to stage and prod on every merge to main.

57 templates4–20 min to live13 also use Supabase

What changes in the port

On VercelOn CloudflareSee it in
Next.js on VercelOpenNext builds the app into one Worker with Static Assets; the data cache sits in R2 and revalidation in Durable Objects.Next.js Commerce
Astro, Nuxt, SvelteKitEach framework's own Cloudflare adapter or preset builds one Worker with Static Assets.Astro boilerplate
Vercel BlobAn R2 bucket per environment, provisioned by Terraform.Blob starter
RedisA Workers KV namespace per environment.Redis starter
TursoA D1 database per environment, its tables created by a migration.Turso starter
PostgresA Supabase project per environment, reached through Cloudflare Hyperdrive.Postgres + Drizzle
Cron JobsA Cron Trigger on the Worker that runs the template's own routes.Cron Jobs
Edge MiddlewareRoutes on one Hono Worker, with request.cf for geolocation and the Rate Limiting binding.Edge Middleware

Questions

Can a Vercel template run on Cloudflare?

Yes. Next.js templates run on Cloudflare Workers through OpenNext; Astro, Nuxt and SvelteKit templates use their framework's own Cloudflare adapter; the API templates run on a Worker. Every template on this page has been ported and builds from a pinned tag.

What does a build give me?

A GitHub repository you own with the template's app, the Terraform for what it needs, and CI that plans every pull request and deploys stage and prod on every merge to main. It goes live in 4 to 20 minutes.

What does it cost?

None of these needs a paid Orunbase plan. Cloudflare, and Supabase for the 13 templates that use it, bill you directly for what the app uses. See pricing.