A hosting panel for the AI era: vibe-code it, push to GitHub, it's live.Explore →

What is vibe coding? Tools, limits and getting to production

What is vibe coding: where the term comes from, how it works, the main vibe coding tools, their limits, and how to take a vibe-coded app to production.

ZoPanel blog cover: What is vibe coding? Tools, limits and getting to production

Key takeaways

  • Vibe coding means building software by describing what you want to an AI tool in plain language and accepting or refining what it writes, often without reading the code line by line.
  • Andrej Karpathy coined the term in a post on X on 2 February 2025, and Collins Dictionary named it its Word of the Year for 2025.
  • Vibe coding tools fall into two groups: coding agents that work in your repository, such as Cursor and Claude Code, and browser app builders such as Lovable, Bolt, v0 and Replit.
  • The hard part comes after the demo: hosting, a domain, a database, secrets, security review and maintenance are still your job.

Vibe coding is building software by describing what you want to an AI tool in plain language, running what it produces, and asking for changes until it works, often without reading the code line by line. The term was coined by Andrej Karpathy in February 2025, and it now covers both browser app builders such as Lovable, Bolt, v0 and Replit and coding agents such as Cursor and Claude Code. It is a fast way to get a working prototype; turning that prototype into an app real people can rely on still takes hosting, a domain, a database, security checks and maintenance.

This guide explains where the term comes from, how vibe coding works in practice, the main types of vibe coding tools, what they are good and bad at, and the "last mile" from a demo to production.

Where does the term "vibe coding" come from?

Andrej Karpathy, a founding member of OpenAI and former director of AI at Tesla, introduced the phrase in a post on X on 2 February 2025. He described "a new kind of coding I call 'vibe coding'", where you "fully give in to the vibes, embrace exponentials, and forget that the code even exists", and he called it "not too bad for throwaway weekend projects". He talked to the AI, accepted its changes and pasted error messages back until things worked.

The phrase spread quickly. In November 2025, Collins Dictionary named "vibe coding" its Word of the Year for 2025, defining it as "an emerging software development that turns natural language into computer code using artificial intelligence".

The meaning has since widened. Developer Simon Willison argued in March 2025 that not all AI-assisted programming is vibe coding: in his definition, vibe coding is "building software with an LLM without reviewing the code it writes". If you review, test and understand every change, you are doing ordinary software development with an AI assistant. That distinction matters for what comes later in this article: the less you review, the more your hosting and processes have to protect you.

How does vibe coding work?

A typical session looks like this:

  1. Describe the goal. "A booking page for my yoga studio: a calendar, a form, confirmation emails, an admin list of bookings."
  2. The tool writes the code. It picks a stack (often React or Next.js with a database), creates the files and runs the app in a preview.
  3. You test by using it. You click around, and when something breaks you paste the error or describe what is wrong.
  4. You iterate. "Make the buttons bigger", "add a field for the phone number", "the date is wrong in Vietnam's time zone".
  5. You ship it. Either the tool's own hosting publishes it, or you push the code to GitHub and deploy it somewhere else.

The result is a normal codebase: JavaScript or TypeScript, Python, a package.json or requirements.txt, environment variables, maybe a database schema. That is good news, because it means the app can be moved, reviewed and hosted like any other software.

What are the main vibe coding tools?

There are two families. The descriptions below come from each vendor's own site at the time of writing (November 2026).

Coding agents that work in your repository

These tools run on your computer or in your editor, read an existing codebase and change it. You keep the repository and choose where it runs.

Tool How the vendor describes it
Cursor "Your coding agent for building ambitious software"; its agents can build, test and demo features for you to review, and several can run in parallel
Claude Code Anthropic's "agentic coding tool that reads your codebase, edits files, runs commands, and integrates with your development tools", available in the terminal, IDEs, a desktop app and the browser

They suit people who are comfortable with a terminal and Git, and anyone who wants the code in their own repository from the first day.

App builders in the browser

These tools start from a prompt in the browser, show a live preview and usually offer hosting with one click. They are where most non-developers start.

Tool How the vendor describes it
Lovable "A full-stack AI development platform for building, iterating on, and deploying web applications"; projects can be synced to GitHub, GitLab or Bitbucket and published to a live URL
Bolt "Create stunning apps & websites by chatting with AI"; Bolt Cloud offers hosting, databases and custom domains
v0 "An AI agent that helps anyone create real code and full-stack apps and agents", with one-click deployment on infrastructure powered by Vercel
Replit "Turn ideas into apps in minutes — no coding needed", with built-in authentication, database, hosting and monitoring

Pricing, limits and features change often in this market, so check each vendor's pricing page before you commit. What matters for this article is whether you can get the code out: Git sync or an export lets you move the app later if the built-in hosting stops fitting.

What is vibe coding good at?

  • Prototypes and demos. An idea becomes something you can click in an afternoon. That is often enough to test it with customers or investors.
  • Internal tools. A form that writes to a database, a dashboard over a spreadsheet, a small admin page for a team.
  • Landing pages and simple sites. Marketing pages, event pages, portfolios.
  • Learning. Beginners see working code for what they asked for and can study it.
  • Boring code for developers. Boilerplate, tests, migrations, small refactors, with a person reviewing the diff.

What is vibe coding bad at?

The risks grow with what the app touches: real users, personal data, payments or paid APIs.

  • Security you did not ask for. AI tools write what you describe. If you never mention access control, rate limits or input validation, they may be missing. Veracode's 2025 GenAI Code Security Report found that AI-generated code introduced risky security flaws in 45% of its tests, across more than 100 language models.
  • Secrets in the wrong place. API keys pasted into front-end code end up in every visitor's browser.
  • Code nobody understands. When a bug appears months later, someone has to read the code. If no one ever did, fixes take longer and each new prompt can break something else.
  • Data and migrations. Changing a database schema on a live app without losing data needs care that a "just make it work" prompt does not give.
  • Costs that follow usage. Platform hosting and paid AI APIs bill by usage; a popular app or a bot hammering an endpoint can raise the bill.

Simon Willison's advice in the post linked above is a good rule: vibe code freely for low-stakes projects, and be careful with anything involving security, private data or APIs that bill by usage.

What is the "last mile" problem of vibe coding?

The demo works in the preview. Getting from there to an app strangers can use is the last mile, and it is mostly not code:

Piece What you need to decide
Hosting The builder's own hosting, a platform such as Vercel, or a VPS you control
Domain Buy one and point its DNS to the host (how to point a domain to a VPS)
HTTPS A certificate that renews by itself, for example free Let's Encrypt SSL
Database Where the data lives, who can reach it, and how it is backed up
Secrets API keys in environment variables on the server, never in the repository or the browser
Security Access control, rate limits, updates, and someone checking the code: see the vibe coding security checklist
Deploys What happens when the next prompt breaks the app: a health check, a rollback, logs
Maintenance Dependency updates, server updates, monitoring, backups

Built-in hosting from an app builder handles some of this for you, and for a prototype it is the quickest path. Teams often move off it when they want a flat monthly cost, the database next to the app, several apps on one server, or data kept in a particular country.

How do you take a vibe-coded app to production?

A practical path that works for most stacks the tools produce:

  1. Get the code into Git. Sync the project to GitHub from the builder, or let your coding agent commit to a repository.
  2. Review the basics. Run through the security checklist: no secrets in the code, authentication on every private route, input validated on the server.
  3. List the environment variables. Database URL, API keys, the app's public URL. Ask your AI tool to list every variable the code reads.
  4. Make the app listen on a port from the environment. Most hosts pass PORT; hard-coded ports are a common reason a deploy fails.
  5. Choose where it runs and deploy. The step-by-step guide is how to deploy a vibe-coded app; for Lovable projects specifically, see deploy a Lovable app to a VPS, and for Bolt, v0 and Replit, deploy a Bolt, v0 or Replit app.
  6. Set up backups and monitoring before the first real user arrives.

A quick check that the app builds and starts the way a server will run it, before you choose a host:

npm ci
npm run build
PORT=3000 npm start
curl -I http://127.0.0.1:3000/

If that works on your machine, it will work on almost any host that runs Node.js.

Hosting a vibe-coded app with ZoPanel

ZoPanel is a hosting control panel you install on your own VPS. For vibe-coded apps it is one way to handle the last mile on a server you control:

  • Deploy from Git. Create a website of type Git deploy with the repository and branch. ZoPanel detects the framework (Next.js, Vite, Nuxt, SvelteKit, Django, FastAPI, Laravel and more, or a Dockerfile when nothing else matches) and proposes the build and start commands. You can also upload the project with the File Manager or SFTP instead of Git.
  • Safe releases. Each push builds a new release inside the account's CPU and memory limits. Traffic moves only after the new release answers its health check; otherwise the old one keeps running. Rollback keeps the last 5 builds.
  • The rest of the stack. Free Let's Encrypt SSL, MariaDB, PostgreSQL, MongoDB and Redis, cron jobs, email on your domain and backups, in the same panel.
  • Docs for your agent. The whole documentation is available as Markdown in llms-full.txt, so Claude Code or Cursor can prepare a repository for deployment.

The trade-offs are real: ZoPanel has no global CDN or edge network, no built-in preview deployments and no autoscaling, and you run the server yourself, including OS updates. The Free plan covers 10 websites, 10 databases and 3 hosting accounts on one server with no time limit. See hosting for vibe coding, the Git deploy guide and pricing.

Conclusion

Vibe coding is a real shift in who can build software: describe the app, iterate, and you have something working the same day. The term started as a joke about weekend projects, and that origin is a useful reminder. The code you did not read still runs, so the closer an app gets to real users and real data, the more review, safe deploys, backups and a host you understand matter. Get the code into Git early, run the security checklist, and pick hosting that fits your budget and control needs.

FAQ

What is vibe coding in simple terms?

It is making software by telling an AI tool what you want in everyday language and refining what it builds, instead of writing the code yourself. Andrej Karpathy coined the term in February 2025 for coding where you "forget that the code even exists".

Who invented the term vibe coding?

Andrej Karpathy, a founding member of OpenAI and former director of AI at Tesla, in a post on X on 2 February 2025. Collins Dictionary chose "vibe coding" as its Word of the Year for 2025.

What are the best vibe coding tools?

It depends on how technical you are. Browser app builders such as Lovable, Bolt, v0 and Replit suit non-developers and include a preview and hosting. Coding agents such as Cursor and Claude Code work inside your own repository and suit people comfortable with Git and a terminal.

Is vibe-coded software safe to use in production?

It can be, but not by default. Review authentication, keep secrets in server-side environment variables, validate input on the server and keep backups. Veracode's 2025 report found security flaws in 45% of its tests of AI-generated code, so a review step is worth the time.

Can I host a vibe-coded app on my own server?

Yes. Apps from these tools are normal codebases, usually Node.js or Python. Sync the code to GitHub, then deploy it to a VPS by hand or with a panel such as ZoPanel, which builds it, adds SSL and switches releases after a health check.

Is vibe coding the same as AI-assisted programming?

Not quite. In Simon Willison's definition, vibe coding means not reviewing the code the AI writes. A developer who reviews, tests and understands every AI change is doing AI-assisted programming.