Deploy your v0 app: host your v0 project

Why host your v0 app on Cloudzyro

v0 is where you build. Cloudzyro is where your app lives once it's ready, with your code in your own repository:

• Every version kept. Each push or upload becomes a version you can restore in one click (5 on Launch, 10 on Boost) or download. See Versions.
• Never asleep. Sites never sleep, on the free plan too.
• Free for business. Launch is free, and you can use it for a business.
• Your own domain, free. Custom domains cost nothing extra on any plan.
• No per-seat charges. Invite your team free.
• Slowed, never cut off. A site over its monthly traffic is slowed for the rest of the month, never taken offline or charged extra.

What we build from your v0 project

v0 usually makes a Next.js app. We build it with next build and run it with next start on Node 24, so server rendering and API routes work. We look at the top of your project to work out what it is:

• An index.html goes online as it is. See HTML sites.
• A package.json with a build script, like a Vite or React app, is built and the files it makes are served.
• A Node.js app with a start script, including Next.js, runs on Node 24, or the version in engines.node or .nvmrc.

With a zip, upload the folder that holds index.html or package.json, not the folder above it. Launch takes uploads up to 100 MB and 20,000 files; Boost up to 1 GB and 50,000. See Upload files.

v0 working branches and pull requests

v0 doesn't push straight to your main branch. Its changes go to a working branch, and you merge them with a pull request. Connect your site to the main branch, and each merged pull request becomes a new version. Changes still on the working branch stay off your live site until you merge them, which gives you a moment to check them first.

Your current version stays online until the new one is ready, so a broken change never replaces a working site. To hold merges back for a while, open the site's Settings and select Pause automatic deploys. See Deploy from Git.

Environment variables in a Next.js app

Add your app's settings, like API keys and database addresses, on your site's Environment variables tab. You can paste a whole .env file. Changes apply on the next deploy; select Deploy now to build again.

In Next.js, values whose names start with NEXT_PUBLIC_ are written into the browser code when the app builds, so set them before you deploy and use them only for public values. Keep secret keys in names without the prefix, read on the server.

See Set environment variables and Host a Next.js app.

Connect a database

Sites on Cloudzyro have no permanent disk: files a site writes while it runs are cleared with each new version. So if your site keeps anything, like sign-ups, orders or bookings, keep it in a database such as Supabase or Neon.

On your site's Database tab, select Connect Supabase, sign in to Supabase and choose the project. We fill in the settings your code reads, test them and deploy. Or paste a connection string from Neon or any other provider. See Connect Supabase or Connect a database.

v0 custom domain

Every site gets a free address at <name>.cloudzyro.app, and you can add your own domain free on every plan. Add it once in the console:

1. Open your site's Domains tab and add the address visitors will use, such as www.example.com.
2. At your DNS provider, add a CNAME record for www pointing to domains.cloudzyro.app.
3. For the bare domain (example.com), add an A record pointing to 173.234.137.167. It sends visitors to www over HTTPS.
4. Wait for the domain to show Live. Certificates are automatic.

If your DNS is at Cloudflare, set the record to DNS only (the gray cloud). Point a domain at your site walks through it, and Connect a custom domain covers the details.

If a deploy fails

Your live site keeps running the previous version, and the deploy page says what went wrong in plain words, with the last lines of the build log and a fix. Select Ask your AI to fix it to copy a ready-made message you can paste into any AI tool. The usual causes:

• My change isn't live. v0 pushed it to a working branch. Merge the pull request into the branch your site uses.
• Missing files. We need an index.html or a package.json at the top of what you sent. A zip that holds one folder with everything inside is a common cause.
• Crashed on start. Often a missing environment variable or a database it can't reach. Add it on the Environment variables tab, then select Deploy now.

Fix a failed deploy explains every reason. Still stuck? Use Get help in the console or email support@cloudzyro.com.

What it costs

Every site starts on Launch, which is free and allows business use, with 100 GB of traffic a month. Boost is $20 a month per site plus tax, with more memory and CPU, priority builds, 10 versions to restore and 1 TB of traffic. Team members are free on every plan. See pricing.

Keep reading

• Host a Next.js app, step by step
• Connect Supabase and point a domain at your site
• Netlify alternatives and Vercel alternatives
• Sites & Apps: everything a site gets