“Vibe coding” means describing what you want in plain English and letting an AI tool build it, and it went mainstream in 2025. Tools such as Lovable, Bolt, Replit and Base44 can turn a prompt into a working website or app in an afternoon, and plenty of small business owners have used them for landing pages, booking forms and internal tools.
2026 has also produced the first large body of evidence about what these tools get wrong. Security researchers found AI-built apps leaking customer and company data at scale, and widely reported incidents showed how quickly things go wrong when nobody reviews the work. This isn't an argument against AI; we use AI tools in our own development every day. It's a practical guide to when an AI builder is good enough for a small business, and when you need a professional.
Quick answer: Use an AI website builder for prototypes, simple brochure pages, event pages and internal mock-ups that don't collect sensitive data. Hire a web developer, or have one review your AI-built site, when it stores customer data, takes payments or bookings, has logins, needs to rank on Google, or has to run reliably for years. The biggest risks with AI-built sites aren't in the design. They're in database permissions, exposed keys, missing backups and SEO.
Table of Contents
- 1. What Vibe Coding Is, and Why It Took Off
- 2. Four Real Incidents From 2025–2026
- 3. Why AI-Built Sites Fail in the Same Places
- 4. AI Builder vs Developer, Side by Side
- 5. When an AI Builder Is Enough
- 6. When You Need a Developer
- 7. Already Built With AI? A 10-Point Safety Check
- Frequently Asked Questions
1. What Vibe Coding Is, and Why It Took Off
Traditional website builders such as Wix, Squarespace and WordPress page builders give you templates to fill in. AI app builders go further: you describe a website or app, and the AI writes the code, creates a database and publishes it, often on the platform's own hosting. You refine it by chatting. For a first version the speed is remarkable, and the cost is a monthly subscription.
The catch is that the parts the AI handles out of sight, such as who can read the database, where secret keys are kept and what happens when something breaks, are exactly the parts a non-developer can't easily check. The demo works. The risks don't show until someone goes looking.
2. Four Real Incidents From 2025–2026
Moltbook, a viral AI-built social network for AI agents, left its production database open. Researchers at the cloud security firm Wiz found the database key in the site's front-end code, which is normal for its database platform, Supabase. But the access rules that should have restricted it (Row Level Security) weren't configured, so anyone could read and change the data. The exposed records included around 1.5 million API keys, tens of thousands of email addresses and private messages. Wiz disclosed the problem to Moltbook's creator, and it was fixed.
The security firm RedAccess reported finding about 380,000 publicly accessible apps and assets built with Lovable, Base44, Replit and Netlify. About 5,000 had virtually no authentication, and researchers said some exposed sensitive material such as hospital schedules, sales records and go-to-market presentations. The findings were covered by WIRED and Axios. The platforms said they weren't given enough detail to verify every finding, and some exposed apps were taken down after the report.
Researchers at Escape.tech analysed more than 5,600 publicly available apps built on vibe-coding platforms. They reported more than 2,000 vulnerabilities, over 400 exposed secrets such as API keys, and 175 instances of exposed personal data, including medical records, bank account numbers (IBANs), phone numbers and email addresses.
During a public 12-day experiment, SaaStr founder Jason Lemkin reported that Replit's AI agent deleted his app's live database during a code freeze it had been told to respect. Replit's chief executive, Amjad Masad, called the incident “unacceptable and should never be possible”.
None of this means AI tools are unusable. It shows a pattern: the AI produces something that works in a demo, while the protections that only matter when something goes wrong, or when someone tries to misuse the app, are missing.
3. Why AI-Built Sites Fail in the Same Places
- Access rules nobody set. Databases need rules about who can read and change which records. AI tools don't always set them, and the app works fine either way, until an outsider reads everything.
- Secrets in the browser. Keys for payment gateways, email services or AI APIs that end up in front-end code can be copied by anyone who opens the browser's developer tools.
- Test and live data mixed together. When one prompt can change the live database, one bad prompt can damage it.
- No backups or rollback plan. Many DIY projects have never tested restoring a backup.
- SEO blind spots. Many AI builders generate single-page JavaScript apps in which content appears only after scripts run. Google can render JavaScript, but these sites often launch without unique page titles and descriptions, proper headings, a sitemap or structured data, and they can be slow on mid-range phones.
- Ownership and lock-in. Your site may live on the platform's hosting and subdomain. Export options vary, and moving later can mean a rebuild.
- Compliance. Forms that collect names and phone numbers bring data protection duties. Under India's DPDP Rules, most obligations, including notices, consent, security safeguards and breach reporting, apply from May 2027.
4. AI Builder vs Developer, Side by Side
| Factor | AI website builder | Professional developer |
|---|---|---|
| Time to first version | Minutes to hours | Days to weeks |
| Upfront cost | Low (monthly subscription) | Higher, mostly one-time |
| Security | Only as good as what you know to ask for | Access rules, secrets and backups reviewed by someone accountable |
| SEO | Often weak by default (JavaScript-heavy pages, missing metadata) | Built for search: crawlable pages, schema markup, speed |
| Ownership | Platform-hosted; export varies | Your code, your hosting, your domain |
| Maintenance | You fix what breaks | Support plan, updates and monitoring |
| Best for | Prototypes, simple pages, internal mock-ups | Customer-facing sites, payments, logins and personal data |
5. When an AI Builder Is Enough
- A one-off event or campaign page that doesn't collect sensitive data
- A prototype to test an idea, show investors or brief a developer
- Internal tools that only use dummy or non-personal data
- A simple portfolio or “coming soon” page on a domain you own
Even then, connect your own domain, write your own page titles and descriptions, and keep a copy of the code.
6. When You Need a Developer
- The site collects personal data: enquiries, bookings, patient or student details, job applications.
- It takes payments or connects to a payment gateway, Tally, a CRM or the WhatsApp Business API.
- It has logins for customers, staff or administrators.
- You need it to rank on Google and bring in leads month after month.
- It must run reliably for years, with updates, backups and someone accountable when it breaks.
There's also a sensible middle path: build the first version with AI, then have a developer review and harden it before real customers use it. A security and SEO review costs far less than a data breach or a rebuild. If you're comparing costs, our website cost guide for Pune explains what a professional build includes, and at Web Crafters professional websites start from ₹15,000. For business systems beyond a website, see our guide to custom software vs SaaS.
7. Already Built With AI? A 10-Point Safety Check
- Is the database locked? Log out, open a private browser window and try to load another user's data or an admin page. If you can, so can anyone.
- Are secret keys hidden? Search your page source and JavaScript files for “key”, “secret” and “token”. Payment and email keys belong on a server, never in the browser.
- Do admin areas need strong logins? Use unique passwords and two-factor authentication.
- Are test and live data separate? Experiment on a copy, not on real customer records.
- Do you have backups, and have you restored one? A backup you've never restored is a hope, not a plan.
- Are forms protected from spam and abuse? Add a captcha or rate limits.
- Do you own the domain, and does the site use HTTPS?
- Can Google read your pages? In Google Search Console, use URL Inspection to view the rendered page, and give every page a unique title and description.
- Do your forms have a privacy notice and consent text? Say what you collect, why, and how people can ask you to delete it.
- Who maintains it? Name the person who updates it, monitors it and fixes it when the platform changes.
If any answer is “no” or “not sure”, get a review before you collect more customer data. Our website security guide explains the most common ways small business sites get hacked, and our website care plans cover updates, backups and monitoring. We build and review websites for businesses across Pune and Mumbai, from Wakad to Vikhroli.
Frequently Asked Questions
Can I use an AI website builder for my business website?
Yes, for simple sites such as a brochure page, an event page or a prototype, as long as you use your own domain, write the page titles and descriptions yourself and don't collect sensitive data. Once the site collects customer details, takes payments or has logins, have a developer review its security before you go live.
Are AI-generated websites bad for SEO?
Not inherently, but many AI builders create JavaScript-heavy single-page apps without unique page titles, descriptions, headings or a sitemap, which makes them harder for Google to index and rank. Check how Google renders your pages with the URL Inspection tool in Search Console, and fix the basics before you rely on the site for leads.
What is vibe coding?
Vibe coding means building software by describing what you want to an AI tool in plain language and letting it write the code, often without reading the code yourself. Tools such as Lovable, Bolt, Replit and Base44 made it popular in 2025.
Is an AI website builder cheaper than hiring a web developer?
Upfront, usually yes. But the total cost includes your time, fixing security and SEO gaps, and possibly rebuilding later if you outgrow the platform. For a business that depends on its website for leads, a professional build, from ₹15,000 at Web Crafters, often costs less over two or three years.
Can a developer fix a website I built with AI?
Usually, yes. A developer can audit the code and database rules, move secret keys to the server, set up backups, fix the SEO basics and, if needed, move the site to hosting you control. That's often quicker than starting from scratch.
Sources
- Wiz: Hacking Moltbook, the AI social network any human can control (February 2026)
- Axios: AI vibe-coding apps leak sensitive data (7 May 2026)
- Escape.tech: How we discovered over 2,000 vulnerabilities in apps built with vibe-coding platforms
- Fortune: AI coding tool Replit wiped a database and called it a catastrophic failure (23 July 2025)
Built Something With AI? Get It Checked.
We review AI-built websites and apps for security, SEO and ownership problems, and fix them, for businesses across Pune and Mumbai.



