Host what v0 designedwherever you want it
v0 writes Next.js, React, TypeScript, Tailwind and shadcn/ui, and it can push all of it to GitHub. Build a static export and dplooy serves it from your own domain — no platform lock-in on either end.
Great components, your choice of host
v0 is a design tool that happens to emit real code. Nothing about that code says it has to be deployed to any particular place.
Leaving it in the v0 preview
- A preview URL that names the tool, not your product
- No domain of your own to point anyone at
- Search engines have nothing to crawl
- No visitor data you can export
- Your hosting decision gets made for you
Static-exported and hosted here
- Your own domain on Pro, or yourname.dplooy.com free
- Free SSL, global delivery, no cold starts
- Views, visitors, countries and referrers with CSV export
- robots.txt, sitemap.xml and a 25-point SEO audit
- The code stays in your GitHub account, deployable anywhere
From generated component to hosted page
Get the code out of v0
v0 can export the project to work on locally, and it can push to a GitHub repo you own — connect GitHub and open a PR from v0, then merge it. Either way what you end up with is an ordinary Next.js project you control.
Turn on static export
Add output: "export" to next.config so npm run build writes plain HTML into an out folder instead of expecting a Node server. This is the one edit that matters — without it there is nothing static to host.
Deploy the out folder — or the repo
Locally: run npm run build, then click Choose folder and pick out. Through GitHub: click Deploy from GitHub, pick the repo and branch, and confirm Set up build & deploy — we detect Next.js and pre-fill npm run build with an out output directory.
It's live, and it stays in sync
Served over HTTPS at your subdomain with free SSL. On the GitHub route, every push rebuilds and redeploys to the same URL, so merging v0's next PR is all it takes to update the live site.
Static export means no server-side features
Dplooy serves files; it does not run Node. Server actions, route handlers, middleware, on-demand image optimisation and incremental regeneration all need a running server and will not work in a static export. Client components, Tailwind, shadcn/ui and anything that fetches from an external API over HTTPS work exactly as they do in development.
What the exported site gets
Static output, but with the tooling you would expect from a hosting platform.
Your own subdomain
yourname.dplooy.com instead of a link that names somebody else's product. Point a custom domain at it on Pro.
Free SSL, always on
Every site is served over HTTPS with a certificate we manage. Nothing to buy, configure or renew.
Real analytics
Views, unique visitors, countries, referrers and devices — for the whole site, exported as CSV whenever you want it.
Findable in search
robots.txt and sitemap.xml are generated for you, and the SEO analyser scores 25 checks and tells you what to fix.
Editable after publishing
Change text, images and colours on the live page with the visual editor, on any plan. Pro adds a full in-browser code editor.
Private when you need it
Password-protect the whole site on Pro, or put an email gate in front of it and collect the addresses.
Frequently asked questions
Can I host a v0 project without touching Next.js config?
Only if the output is already static. If v0 gave you a single component you want to show off, the quicker path is to drop it into a plain Vite or HTML page and deploy that. Anything using the Next.js app router needs output: "export" before it can be served as files.
What if my project uses server actions?
Then it isn't a static site, and no static host can serve it — not just this one. Either move that logic to an external API your front end calls over HTTPS, or keep the app on a host that runs Node. Dplooy's form endpoints cover the most common case, which is a contact form that needs somewhere to POST.
Do images still work?
Yes, as long as they aren't relying on on-demand optimisation. Set images.unoptimized to true in next.config for a static export, or use plain img tags. Images you deploy alongside the site are served from the same subdomain like any other asset.
Can I add a working contact form?
Yes. Create a form endpoint in dplooy, paste its URL into your form's action attribute, and submissions land in your dashboard and in your inbox. No JavaScript, no API key, no third-party service — it's built into the platform on Plus and Pro.
Does shadcn/ui work?
Yes. shadcn/ui components are copied into your repo as ordinary React source and compiled away by the build, so by the time we serve anything they're just HTML, CSS and JS. Tailwind is the same.
Can I use my own domain?
Yes, on Pro. Connect a domain you own, add the DNS records we show you, verify, and the site answers on your address with SSL we manage and renew.
Is it free?
Yes, on the free plan: 3 hosted projects, free SSL and analytics. Free-plan sites are removed after 3 days. Plus and Pro sites stay up indefinitely, and Pro adds custom domains and password protection.
Other ways to get there
Hosting for the other AI builders
Same platform, same free plan. Whichever tool wrote the site, it ends up on an address you own.
Beautiful components deserve your domain
Create a free account, export the project, and have it live on your own address.