On Product Hunt, I can see many people launching their products using "vibe-coding tools" like @Lovable , @bolt.new , or@Replit
I reckon many people who created something with them are usually developers who didn't have enough time for building a side idea before, but with AI, they could make it happen.
Built my app with Lovable a few months ago. Launch went fine but since then I've had three separate production issues; auth breaking, database timeouts, a webhook that silently fails. Each one took me days to figure out and I have zero engineering background.
Curious what others are doing. Are you just patching it yourself, hiring freelancers each time, or has anyone found something more ongoing? I've been wondering if a monthly retainer for this kind of support would actually be worth it or if that's just me.
I've built my product around traditional SaaS pricing (monthly tiers), but I m starting to wonder if that model is getting outdated, especially with more AI-powered and compute-heavy tools entering the market. That shift requires real architectural changes, instrumentation, metering, billing logic, and UI changes, not just pricing tweaks. It s something I m starting to seriously think about for my own product.
In particular, AI usage has real COGs (every prompt costs money), and I m seeing more platforms experimenting with usage-based models, or hybrids like SaaS base + usage + overage.
For those of you building AI or compute-intensive tools:
AI dev tools are evolving crazy fast , every few weeks there s a new must-try for vibe coders.
Some people are building full products with @ChatGPT by OpenAI and @Replit , others swear by @Cursor and @Claude by Anthropic , and a few are mixing @Lovable + @v0 by Vercel + @bolt.new to ship apps in record time.
I ve been refining my own vibe stack lately, trying to find that sweet spot between speed, control, and creativity. It made me wonder ,what does your setup look like right now?
Last year we hired a design agency to build our marketing site for @Basedash. They did an incredible job. The headline makes it sound like I'm dunking on them, but I'm not. The site was genuinely great. They built it in Framer so we could manage content ourselves, which was a completely reasonable bet at the time (and something we explicitly asked for).
I love the concept of "vibecoding", getting into the flow, using AI to build fast, and focusing purely on the product. But for a lot of developers (especially in emerging markets like Indonesia), that vibe instantly dies when it's time to deploy.
Suddenly, you are dealing with complex server setups, fighting DevOps configurations, or getting blocked because you don't have an international credit card to spin up a basic server.
Deployment shouldn't ruin the vibe. It should be just as seamless as writing the code.
I ve been spending more time vibe coding recently, and I ve started to question something I initially took for granted. Most of the conversation around vibe coding is about speed. Like how quickly you can go from idea to prototype, or how fast you can iterate. And to be fair, that part is real. The barrier to building has clearly dropped.
But the more I use these tools, the more it feels like speed isn t the limiting factor anymore.
The real constraint seems to be taste.
what do you choose to build?
what do you keep vs discard?
what actually feels right vs just working ?
what is genuinely useful vs just impressive in a demo?
AI coding tools seem to come in two main flavors: IDE-based, like @Cursor and @GitHub Copilot, and terminal-based setups, like using @Claude Code to generate commands, scripts, or entire files. Both have their fans, but which one actually helps you move faster?
Curious what flow people are sticking with long term, and where you see the most gains (or frustrations).
I might be missing some but I've been pretty much in love with @Lovable, @Cursor, @bolt.new and have been trying to use @Replit more and I honestly haven't touched @BASE44 too much but have heard good things. @chrismessina has nudged me to use @Windsurf for whenever I build another Raycast Extension! Currently I use: - @bolt.new / @Lovable - @Cursor - @Warp Curious what everyone thinks is the top one so far!
