If you've been following the vibecoding space, you know how quickly this community has grown. After spending the last 6 months deep in the vibecoding world, I wanted to share what I've learned and give back to the community that's taught me so much.

The Journey So Far

Over the last 6 months, I've built over 20 different applications using AI-assisted development. One of them, glenn-explore, unexpectedly went viral and had over 90,000 people try it out. That experience taught me a lot about scaling, hosting, and what really matters when building for real users.

Taking a Different Path

While most vibecoders seem to go with the typical Vercel + Supabase combo, I decided to take a different route. I've been self-hosting a .NET backend with SQLite on a $5 DigitalOcean droplet, and honestly? It's worked amazingly well. There's something really satisfying about going back to the “primitives” and understanding how everything fits together.

My current stack: .NET Backend (self-hosted), Next.js (self-hosted), and Postgres (Supabase). Claude 4 is absolutely incredible with C#, and the established patterns just make projects scale so much better over time.

The Template Experiment

Here's where it gets interesting. I've been playing around with MCPs and created an integration with a kanban tool I use. It works so well that I decided to try an experiment: let Claude Opus plan an entire starter template, then have Sonnet implement it.

The process was simple but effective:

1. 1. Opus created all the tasks and broke everything down
2. 2. Sonnet implemented each task step by step
3. 3. I could literally leave at night, come back the next day, and the LLM could just check the kanban to see where it left off

This structured approach where the LLM both creates tasks AND implements them has been game-changing for me.

What's in the Template

The result is a 100% vibecoded starter template that includes everything you need to build a modern web application:

• • Authentication - ASP.NET Core Identity + JWT + OTP
• • Email - Resend integration
• • File Upload - Cloudflare R2
• • LLM Integration - OpenRouter
• • Real-time - SignalR/WebSockets
• • Analytics - Metrics & monitoring
• • Modern UI - Next.js 15 + React 19 + shadcn/ui
• • Background Jobs - Hangfire integration

Repository: https://github.com/WilliamAvHolmberg/vibecodementor

Is it perfect? Absolutely not. There are definitely bugs and things that need attention before going live. But it's a solid foundation that I've been using as my starting point for every new project.

Building in Public

I decided to open-source this because I genuinely believe you learn so much more by building in public. I want to create a space where we can all share our vibecoding approaches and learn from each other.

Some questions I'd love to hear your thoughts on:

• • What's your go-to vibecoding stack?
• • Have you tried the LLM → kanban → LLM workflow?
• • What features would you want to see in a starter template?
• • Any thoughts on self-hosting vs. managed services for vibecoding?