The guide
How to vibe code
Vibe coding — building real software by directing an AI coding agent instead of typing every line — went from meme to mainstream in two years. This is the honest version of how to do it, distilled from analyzing hundreds of real products and scoring what a solo builder can and cannot replicate.
01Pick your AI coding tool
Claude Code for autonomous multi-file work in the terminal, Cursor for hands-on editing, Codex or Gemini CLI as alternatives. One subscription (~$20/mo) is enough to start — you don't need all of them.
Compare the tools →02Scope down to one core loop
The number one failure: asking for the whole product on day one. Pick the single loop that delivers the value — create a ticket, shorten a link, schedule a meeting — and cut everything else from version one.
03Write the spec before the prompt
A markdown file with your data model (tables and fields), the screens, and what "working" means. Feed it to the agent as context. Ten minutes of spec saves hours of the agent guessing wrong.
04Prompt in build-sized steps
Scaffold → data layer → core screens → auth → deploy. One step per prompt, verify each before moving on. Our app reports generate these exact step-by-step prompts for any product you want to clone.
Browse ready-made build guides →05Ship it somewhere cheap
Personal projects: SQLite (Turso) + better-auth + Cloudflare or Vercel is $0/mo. Need a real server? Railway or Fly.io from ~$5. Match infrastructure to what the project actually does — not to habit.
See all providers →06Expect the unglamorous 20%
OAuth callbacks, email deliverability, file-upload limits, timezone math. This is where vibecoding stops being magic and becomes debugging with an assistant. Budget real time for it — the honest reports on this site tell you where each product bites.
Why vibe coding works now
Frontier models solve real GitHub issues — actual bugs in actual codebases with passing test suites — at rates that were science fiction two years ago. This is SWE-bench Verified, the industry-standard coding benchmark, as of mid-2026:
% of 500 real-world software engineering tasks solved end-to-end. Sources: vals.ai, benchlm.ai (July 2026).
What can you actually vibecode? Data from 938 real products
We scored 938 SaaS products on how realistically a solo dev could vibecode a personal clone (0 = impossible, 100 = weekend build). 34% land at 60+ — a solid side project or easier. The moats that stop you are almost never the code: they're networks, compliance, and proprietary data.
7
Weekend build
315
Solid side project
428
Serious undertaking
157
Don't bother
31
Impossible
Live data from the VibeItYourself report database, refreshed hourly.
The AI coding tools, priced
| Tool | Pricing | Best for |
|---|---|---|
| Claude Code | Free tier; Pro $20/mo; Max $100+/mo; API $3/M input, $15/M output | Anthropic's agentic coding tool that lives in your terminal |
| Cursor | Free tier; Pro $20/mo | The AI code editor |
| Codex | Free tier; Go $8/mo; Plus $20/mo; Pro 5x $100/mo; Pro 20x $200/mo; API pay-as-you-go available | OpenAI's software engineering agent |
| Gemini CLI | Free tier available; Pro $19.99/mo; Ultra $99.99/mo; Pay-as-you-go API option available | Google's open-source AI agent for your terminal |
What running it costs
Hosting scales with what the project actually is — most personal clones genuinely run at $0/month:
| Scale | Database | Auth | Hosting | Monthly |
|---|---|---|---|---|
| Personal ($0/mo) | Turso / Neon free tier | better-auth | Cloudflare / Vercel free | $0 |
| Real server (~$5/mo) | Railway Postgres | better-auth | Railway / Fly.io | $5-10 |
| Growing product (~$45/mo) | Neon Launch / Supabase Pro | Clerk (10k MAU free) | Vercel Pro + workers | $40-60 |
| Enterprise-ready | PlanetScale | WorkOS SSO ($125/conn) | AWS / Fly.io multi-region | $200+ |
Full provider breakdowns with free-tier limits on the providers page.
Vibe coding FAQ
- What is vibecoding?
- Vibecoding (also written vibe coding) is building software by directing an AI coding agent in natural language — you describe features, review what it builds, and steer, instead of writing most code by hand. The term comes from Andrej Karpathy's 2025 observation that you can now 'fully give in to the vibes' and let the model write the code.
- How do you vibe code as a complete beginner?
- Start with a scoped tool like Cursor or a web builder like bolt.new or v0, clone something tiny you actually use (a link shortener, a notes page), and deploy it on a free tier. You will learn more shipping one small real thing than reading ten tutorials. The build guides on this site give you paste-ready prompts for hundreds of products.
- How much does vibecoding cost?
- Typically $0–20/month to start: an AI coding subscription (Claude Pro or Cursor Pro, ~$20) plus free-tier hosting (Cloudflare, Vercel, Turso, Neon). Our per-app reports itemize starting and ongoing costs, including estimated token usage if you prefer paying per use.
- Is it 'vibecode' or 'vibe code'?
- Both are used — 'vibe coding' as two words is the original phrasing, and 'vibecode'/'vibecoding' is the compound that stuck as the practice became a verb. Same thing either way: AI writes the code, you direct it.
- What can't you vibecode?
- Products whose value is scale, network effects, proprietary data, or regulatory moats: search engines, payment networks, banks, marketplaces. You can often vibecode a personal-use subset — our verdicts score exactly this, honestly, per product.
- How long does it take to vibecode a real app?
- A focused single-loop tool: a weekend. A solid SaaS clone for personal use: one to three weeks part-time, most of it in the last 20% (auth edge cases, deployment, polish). Anything claiming 'a full SaaS in an afternoon' is demoware.
Want the build guide for a specific product?
Drop in any SaaS — we scrape it, research the business, and hand you an honest verdict plus step-by-step vibecoding prompts.
Analyze a product