01
Where the term comes from
The name was coined by Andrej Karpathy in February 2025. He described a way of working where you stop reading every line the AI writes: you say what you want, run it, look at what happens, and say what to change.
Since then the term has widened. Today people use it for any app built mostly through prompts, from a weekend prototype to a product with paying customers.
02
How it works in practice
- You describe the app: who uses it, what they do, what you need to store.
- The tool writes the code, sets up the data and shows you a running version.
- You try it, then ask for changes in plain words: move this, add that, fix this error.
- When it does what you need, you put it online, usually from the same tool.
03
The kinds of tools
Vibe coding tools fall into a few groups. Most projects use one from each of the first three.
| Kind | What it does | Examples |
|---|---|---|
| Prompt-to-app builders | Turn a description into a working app with an interface, data and hosting | Lovable, Replit, Bolt, v0, Base44 |
| AI code editors | An editor where an agent reads and changes your code with you | Cursor, Windsurf, Claude Code |
| Data and sign-in | Where the app keeps its data and its users | Supabase, Firebase, Clerk |
| Hosting | Where the app runs once it is public | Vercel, Replit, Netlify |
04
What it is good at
- Internal tools: dashboards, request forms, small CRMs, booking pages.
- First versions of a product, to show customers something real.
- Rebuilding a spreadsheet process as an app.
- Changing an app that already works: a template is a faster start than a blank prompt.
05
Where it still needs care
The AI writes code that runs, not always code that is safe. The usual problems are the same from one project to the next: pages or data open to anyone who has the link, keys left in the code, payments that trust what the browser says, and no backups.
None of this is a reason to avoid vibe coding. It is a reason to have someone who knows what to check look at the app before real customers and real money go through it.
06
Three ways to start
- Compare the tools and pick one that fits what you are building.
- Start from a template that already works and change it, instead of starting from an empty prompt.
- Hire someone who builds with these tools every day, for the whole project or only for the review before launch.
Questions
Do I need to know how to code?
Not to start. You can get a working app from prompts alone. Knowing the basics helps when something breaks, and it matters before you launch to the public.
Is vibe coding the same as no-code?
No. No-code tools give you blocks to assemble inside their platform. Vibe coding tools write real code, which you can usually take with you and host elsewhere.
Can I build a real business on a vibe-coded app?
Yes, people do. The app needs the same care as any other software before launch: access rules, payments, backups and someone responsible for fixes.
How much does it cost to start?
Most tools have a free plan and paid plans billed monthly. Prices change often, so check each tool's own page; every tool listed here links to it.