Vibe coding a business app: what works, what breaks and when to hire a developer
Vibe coding means describing an app in plain language and letting AI write the code. Tools like Lovable, Bolt and Replit can turn an idea into a working prototype in an afternoon. We look at what they handle well, where vibe-coded business apps break, a 10-point checklist before launch and the moment it pays to bring in a developer.
Related service: Custom software and CRM for businesses

Can you vibe code a business app? The short answer
Yes for a prototype, a landing page or an internal tool with a few trusted users. Describe what you want, and tools like Lovable, Bolt, Replit or v0 will build a working app with a database, login and hosting in hours, not weeks.
Not yet for an app that stores customer data, takes payments or has to run every day without surprises. The AI writes code that looks finished, but the parts you can't see, such as database permissions, secret keys and error handling, are where vibe-coded apps fail. Before real users and real data go in, someone who reads code should review it.
What is vibe coding?
The term comes from Andrej Karpathy, a co-founder of OpenAI, who wrote in February 2025 about a new kind of coding where you "fully give in to the vibes" and "forget that the code even exists". You describe the result, the AI writes the code, and you judge the app by clicking through it, not by reading what's underneath. By November 2025 Collins Dictionary had named it word of the year.
It spread fast. In Y Combinator's Winter 2025 batch, about a quarter of startups said 95% of their code was written by AI. Professional developers are more cautious: in the Stack Overflow 2025 survey, 84% use or plan to use AI tools, but 77% say vibe coding is not part of their work, and only 3% highly trust the accuracy of AI output.

Four tools come up in almost every conversation about vibe coding. Here's how they compare.
Lovable vs Bolt vs Replit vs v0
| Tool | Best for | Free plan | Paid plans (17 Nov 2026) |
|---|---|---|---|
| Lovable | Full web apps with a database and login, built in a chat | 5 credits a day, up to 30 a month | Pro from $25/month (100 credits), Business from $50/month |
| Bolt.new | Quick prototypes and websites in the browser | 1M tokens a month, Bolt branding | Pro $25/month (10M tokens), Teams $30 per member |
| Replit | Apps with a backend, built by an AI agent | Daily agent credits, one app that goes offline after 30 days | Core $20/month ($20 credits), Pro $100/month |
| v0 by Vercel | Interfaces and front ends for React and Next.js | 7 messages a day | Plus $30 per user/month, Business $100 per user/month |
What vibe coding is good at
Vibe coding shines when the cost of a mistake is low and speed matters most:
- Validating an idea. A clickable prototype you can show to customers or investors before you spend money on development. - Landing pages and simple websites. Content, forms and a nice layout are well within reach. - Internal tools for a small team. A dashboard over a spreadsheet, a simple tracker or a form that a few trusted colleagues use. - A detailed brief for a developer. A working prototype explains what you want better than ten pages of specification.
The common thread: no sensitive data, few users, and nothing breaks badly if the app goes down for a day.

The problems start where you can't see them: in the database, the keys and the permissions.
What breaks when you vibe code a business app
Researchers have tested AI-written code at scale, and the results are consistent. In Veracode's 2025 report, code from more than 100 language models introduced a known OWASP Top 10 weakness in 45% of tasks. The most common problems in vibe-coded apps:
- Open databases. Many tools use Supabase, where every table needs Row Level Security. Without it, as the Supabase docs put it, the table is readable and writable by anyone with access to the API. - Secret keys in the browser. API keys for payments, email or AI models end up in front-end code, where anyone can copy them and run up your bill. - Login that only works on the surface. The app hides a button from non-admins, but the server never checks who is asking. - Runaway costs. Credits burn fastest when the AI is fixing its own bugs in a loop. - No backups and no separate test environment. One wrong prompt can change live data.
Real incidents with vibe-coded apps
These are documented cases, not hypotheticals:
- Lovable, 2025. A security researcher found that 170 of 1,645 scanned Lovable apps let anyone read or change their data because of missing database rules. It was registered as CVE-2025-48757 with a severity score of 9.3 out of 10. Lovable disputes the CVE and has since added a security scan. - Escape.tech, October 2025. A scan of more than 5,600 public vibe-coded apps found over 2,000 vulnerabilities, over 400 exposed secrets and 175 cases of exposed personal data. - Replit and SaaStr, July 2025. During a code freeze, Replit's AI agent deleted the production database of SaaStr founder Jason Lemkin's test project. Replit's CEO called it unacceptable and added automatic separation of development and production databases. - Lovable, April 2026. A researcher reported that free accounts could read the code and AI chat history of other users' public projects. Lovable denied a data breach and said the exposure was limited to projects set to public.
None of this means the tools are bad. It means a generated app needs the same review as any other software before real data goes in.

Before you invite real users, go through this list. Each point takes minutes to check.
Checklist: 10 things to check before launch
- Row Level Security is on for every table, and each rule says who may read and write which rows.
- No secret keys in the front end. Payment, email and AI keys live only on the server.
- The server checks permissions, not just the interface. Try opening an admin page or API call as an ordinary user.
- Passwords and login go through a proven service, never a home-made one.
- Every form is validated on the server, including length, format and file uploads.
- Backups run automatically, and you have tried restoring one.
- Development and production are separate, so experiments never touch live data.
- Spending limits are set for AI credits, hosting and every paid API.
- Errors are logged and someone gets an alert when the app fails.
- You own the code. It sits in your own GitHub repository, so you can move to another host or developer at any time.
Privacy rules still apply to vibe-coded apps
An app built in an afternoon is still bound by the same law as any other: GDPR in the EU and UK, the CCPA in California, PIPEDA in Canada and the Privacy Act in Australia. If the app stores customer names, emails or payments, you need to know where the data is hosted, who can access it and how you would delete it on request. The tool's terms of service matter too, because some plans allow the vendor to use your project data to train AI models. We cover the same question for ChatGPT in Is ChatGPT safe for business?

So when is it time to stop prompting and call someone who reads code?
When to hire a developer
Bring in a developer when at least one of these is true:
- Real customer data or payments are going into the app. - The app is becoming part of daily operations, so downtime costs money. - It has to connect to other systems, such as your CRM, accounting software or online store, in ways the tool doesn't support out of the box. - Each new prompt breaks something that used to work, and credits are going into fixes rather than features. - You are raising money, and investors will ask who owns the code and how secure it is.
You don't have to throw the prototype away. In most cases it's the best possible brief. A developer can review it, fix the risky parts and keep the code you already have, or rebuild the core properly and keep your design and flows. If you're weighing a bigger system, our guide Custom software vs SaaS helps with that decision.
How GBdix can help
At GBdix we build MVPs and custom internal systems, and we also take over prototypes made in Lovable, Bolt, Replit or v0.
- Prototype review. We go through the code, database rules and keys and tell you what is safe, what isn't and what to fix first. - Making it production-ready. Security, backups, a separate test environment, payments and connections to your other tools. - Building it properly from the start. If the idea has outgrown the prototype, we build the MVP as code you own, with your prototype as the brief.
See our MVP for startups page or, for tools your team uses every day, custom internal systems. Not sure where your app stands? Message us and we'll tell you honestly whether it needs a developer at all.
Vibe coding: frequently asked questions
What is vibe coding?
Can I build a real business app with vibe coding?
Is vibe coding safe?
Which is the best vibe coding tool for a business app?
How much does vibe coding cost?
Do I own the code from a vibe coding tool?
Will vibe coding replace developers?
Who can turn my vibe-coded prototype into a production app?
Sources
- Term: Andrej Karpathy on X, February 2025, Collins word of the year 2025 (CNN)
- Adoption: TechCrunch, Y Combinator W25, Stack Overflow Developer Survey 2025
- Security: Veracode 2025 GenAI Code Security Report, NVD, CVE-2025-48757, Escape.tech scan, Wiz, risks in vibe-coded apps, The Register on Lovable, Gizmodo on Replit
- Checklist: Supabase Row Level Security, OWASP Top 10:2025
- Pricing: Lovable, Bolt, Replit, v0

Built a prototype with AI? Let's make it production-ready
Send us your prototype or your idea. We'll tell you what is ready for real users, what needs fixing first and whether it makes sense to keep building on it.
Source: GBdix · Published 17 November 2026






