vibestacks: The Next.js Boilerplate I Wish I Had
Most boilerplates give you a folder structure. vibestacks gives you a production-ready SaaS with payments, auth, AI, and analytics pre-configured.
I've built two profitable SaaS products this past year. Both times I spent like 50+ hours setting up the same boring stuff: authentication, payments, email, error tracking, analytics. You know the drill.
Thats 50 hours I couldve spent building features customers actually pay for.
So yeah, im building vibestacks. A Next.js boilerplate that handles all the infrastructure so you can focus on your actual product.
The Problem With Most Boilerplates
Most starter templates give you a folder structure, maybe some routing, perhaps a component library if your lucky.
Then they leave you to figure out:
- Stripe webhooks - Debugging these is genuinely painful. Theres a reason whole companies exist just to help manage webhook reliability. Miss one event and your subscription state gets out of sync.
- Auth that wont get you hacked - 81% of data breaches involve weak or stolen credentials according to Verizon. Rolling your own auth is asking for trouble, but integrating it properly still takes forever.
- Email that actually lands in inbox - SPF, DKIM, DMARC, sender reputation, spam triggers... almost half of senders say avoiding spam folders is an ongoing struggle. Its way more complicated than just "send email".
- Error tracking when stuff breaks - Because it will break in production. And youll want to know before your customers tell you.
Your still spending weeks on infrastructure. Defeats the whole purpose.
What vibestacks Will Include
Building this with everything I wish I had when starting my own projects:
Authentication - BetterAuth configured with email/password, OAuth, magic links, session management. The stuff that takes forever to get right and is really easy to mess up.
Stripe Subscriptions - Including the webhook handlers. Customer portal, usage billing, all pre-configured and actually tested.
Email - Resend setup with proper authentication so your transactional emails dont end up in spam.
Everything else - Drizzle for database, Sentry for errors, PostHog for analytics, Cloudflare for security.
Building Product-Led
Heres the thing - im not going to build this in isolation and hope people buy it.
Im building vibestacks based on what founders actually need. If you use it and something is missing or broken, tell me. Want a specific integration? Let me know. The roadmap will be shaped by the people using it.
Think of it less like buying a product and more like having a technical co-founder who handles the boring infrastructure stuff so you can focus on what makes your product unique.
Why Next.js?
Its become the standard for building React apps. App router is stable and easy to use, server actions make data mutations simple, typescript catches errors before production.
Combined with Drizzle ORM and BetterAuth its a really solid stack that scales well.
The Goal
When vibestacks launches you should be able to:
- Clone the repo
- Run setup script
- Deploy to Vercel
- Start collecting payments same day
No more week long setups just to get the basics working.
Got thoughts on what youd actually want in a boilerplate? MMessage me at raman@vibestacks.dev or on LinkedIn.
Building something and stuck on infrastructure? Tell me about it. Might just become a feature.
Read more
Tailwind CSS v4: What Changed and Why It's Better
No more tailwind.config.ts. Tailwind v4 moves configuration to CSS, drops JavaScript, and ships 2x faster. Here's everything that changed.
Why We Use cn() and cva() for Component Styling
String concatenation for Tailwind classes is a mess. Here's how cn() and cva() make conditional styling clean, type-safe, and maintainable.
Stop Trusting process.env: Type-Safe Env Variables in Next.js
process.env fails silently and leaks secrets. Here's how t3-env catches missing env vars at build time, not production.