Why I Built This Most Next.js templates either: * Work great on Vercel but nowhere else * Sacrifice features for platform compatibility * Require extensive modifications for each deployment target
I needed something that could deploy to Cloudflare Workers (for $5/month projects) or AWS (for enterprise clients) with the same feature set as Vercel deployments.
Key Features Core SaaS Stack: * Authentication (Better Auth) * Payments (Stripe) * Database (Drizzle ORM) * Email (Resend) * File storage (S3/R2) * Blog & docs (FumaDocs) * i18n support * GDPR-compliant analytics
Deployment Options: * Vercel: Standard deployment * Cloudflare Workers: Uses OpenNext + D1/KV/R2 integration * AWS: SST-based deployment with RDS/Lambda/CloudFront * Containers: Railway, Fly.io, etc.
Technical Highlights * OpenNext Integration: Compatible Node.js API support on Cloudflare Workers * SST for AWS: One-command infrastructure deployment * AI-Friendly Stack: Next.js 15, Tailwind CSS v4, Shadcn UI * Multi-theme Support: Easy color scheme switching * SEO Optimized: 100/100 Google PageSpeed score
The Cloudflare Workers version uses D1 for database, KV for caching/ISR, and R2 for storage - all within the $5/month Worker Standard plan. The AWS version leverages RDS Proxy, Lambda, and CloudFront with proper security configurations for enterprise deployments.
Links
* Website: https://nextdevkit.com * Vercel Demo: https://demo.nextdevkit.com * Workers Demo: https://workers.nextdevkit.com * AWS Demo: https://aws.nextdevkit.com * Documentation: https://nextdevkit.com/docs
Built this because I was tired of rebuilding the same infrastructure for every project. Would love feedback from the HN community on the deployment approach and feature set!