Updated 7 min readBy The VibeDeploy team

Localhost to Live URL: Turn Your Project into a Public Link

Turn a localhost project into a shareable live HTTPS URL. Compare a temporary tunnel with permanent EU hosting, then connect your own domain and HTTPS.

Short answer

The fastest live URL depends on how long it has to last. A tunnel such as ngrok or Cloudflare Tunnel gives the app running on your machine a public HTTPS address within minutes, but only while your computer and the tunnel keep running. For a link that keeps working, build the project and upload the dist/ or build/ folder to a host: on VibeDeploy you get https://name.subsite.site in about 30 seconds.

Need a link that keeps working?

Drop your dist/ or build/ folder in and get https://yourname.subsite.site in about 30 seconds. Free for 14 days, no card. After that from EUR 4/month.

The simplest way to get a localhost site online is to deploy its built files to a static host that gives you a public HTTPS URL. If you just want the quickest answer, follow the localhost deployment steps: build your project, usually with npm run build, then upload the resulting dist/ or build/ folder. You get a live https://yourname.subsite.site URL and can add a custom domain when you are ready.

That is the short version. The rest of this page explains the real options, when each one fits, and the exact steps.

First, what "localhost" actually is

http://localhost:3000 (or :5173, or :8000) is a server running only on your own machine. Nobody else can reach it. To put it online you need one of two fundamentally different things:

  1. A tunnel that temporarily exposes your running local server to the internet.
  2. A deploy that copies your built site to a host that serves it permanently.

These solve different problems. Pick by what you actually need.

Why localhost/project or localhost/demo only opens on your computer

Any localhost/... address, whether it is localhost/project, localhost/demo, or localhost:3000, resolves to 127.0.0.1, an IP address that always means "this machine". When you open it, your browser talks to a server running on your own computer. When someone else opens the exact same link, their browser looks for that server on their machine, finds nothing, and shows "This site can't be reached". The link is not broken; it just points somewhere different for every person who clicks it.

That is why there is no trick, browser setting, or router tweak that turns a plain localhost URL into a public one. A localhost link you can actually share means one of two things: a tunnel that exposes your running machine, or a deploy that puts the files on a real host. Those are exactly the two options covered below.

Option 1: a temporary tunnel (for a quick demo)

Tunnel tools give your running localhost a temporary public address, often for a few minutes or hours. This is great for showing a teammate a work-in-progress, testing a webhook, or a quick screen-share demo. The two names you meet first are ngrok and Cloudflare Tunnel, and they make opposite trade-offs: we compare them here, including why a "Vercel tunnel" does not exist.

The catch: the URL dies when you close your laptop, the address is usually one the tool assigns (a Cloudflare Quick Tunnel picks a new one every time), and every visitor is served by your own machine. It is a demo trick, not hosting. If you want the link to keep working tomorrow, you need a real deploy.

Option 2: deploy the built site (for anything real)

Most localhost projects, including most of what AI tools build, compile down to static files: HTML, CSS, JavaScript, and assets. Once you have those built files, a static host serves them to the world. This is the right answer for a portfolio, a landing page, a client site, a side project, or an AI-generated app front-end.

The steps are the same almost everywhere:

# from your project folder
npm run build
# produces dist/ (Vite, Astro, SvelteKit static) or build/ (CRA, some others)

Then upload that output folder. With VibeDeploy:

  1. Start a free 14-day trial, no credit card.
  2. On the upload screen, drop the dist/ or build/ folder itself, or a ZIP of the files inside it.
  3. You get a live *.subsite.site URL within about 30 seconds.
  4. Open Domains, add your own domain, and point the DNS records it shows you. SSL provisions automatically, usually within 60 seconds.

If your project is plain HTML with no build step, even simpler: drop the folder with your index.html straight in.

Option 3: let an AI agent deploy it for you

If you build in an MCP-capable client like Claude, Claude Code, Cursor, or Windsurf, you can skip the manual upload entirely. Connect the VibeDeploy MCP server at https://mcp.vibedeploy.be/mcp, then ask the agent to "deploy this to VibeDeploy". The agent ships your build and replies with the live URL. The VibeDeploy MCP server setup page has the exact steps for each client, and What is MCP hosting explains how it works.

Working in a terminal? You can deploy from Claude Code after one command:

claude mcp add --transport http --scope user vibedeploy https://mcp.vibedeploy.be/mcp

Run /mcp inside Claude Code once to sign in, then say "deploy this". For the whole path from an empty folder to a live site, follow the Claude Code terminal workflow.

This route also sidesteps a classic confusion. When Claude says it saved your site to a sandbox path, remember that /mnt/user-data/outputs/index.html is not on your computer at all, but an MCP-connected agent can deploy it from there directly.

Which one should you use?

  • Just need to show someone for five minutes? Use a tunnel.
  • Want a link that keeps working, on your own domain? Deploy the built files.
  • Building with an AI tool or coding agent? Let the agent deploy over MCP.

For most people asking "how do I get my localhost site online", option 2 is the real answer, because the point is usually a link that lasts.

For a side-by-side breakdown of tunnels, static hosts, and other approaches, see the tunnel vs hosting comparison.

Need a link that keeps working?

Drop your dist/ or build/ folder in and get https://yourname.subsite.site in about 30 seconds. Free for 14 days, no card. After that from EUR 4/month.

A note on "but my app has a backend"

A static front end, whether plain HTML or the dist/ or build/ folder of a React, Vue, Svelte or Astro project, deploys directly as in option 2. If your localhost app also runs a server (a Node or Express API, a Python app) or a database, that part needs somewhere to run as well. You have two honest choices:

  • Run it next to the site on VibeDeploy. A site can run containers beside it: your own server running your project's source, Postgres, MySQL, Redis or a worker, up to 6 services with 2 CPU and 2 GiB of memory in total, isolated with gVisor. Your AI deploys them through the MCP tool deploy_app, connected as in option 3. API keys go into the site's Settings > Secrets in the dashboard, never into the chat. Container data is not yet included in snapshots, so keep your own database exports.
  • Keep it on any server host you already use, and deploy only the front end here. A front end that calls an external API or a service like Supabase works as it is.

A tunnel is still the right tool for a short demo of the whole stack, straight from your laptop.

Why EU hosting, briefly

If your visitors are in Europe or your site touches any personal data, where it is hosted matters for GDPR. VibeDeploy serves only from Belgian data centres, with a Data Processing Agreement available on every paid plan. That is a different default from most US-based static hosts. See why GDPR matters for AI-built sites.

Cost

The 14-day trial covers one site with a custom domain, so you can take a localhost project all the way to a live HTTPS URL at no charge. After the trial, Solo is EUR 4 a month for one site with your own domain; Maker is EUR 15 a month for three sites. Prices include VAT where it applies, and both plans are flat, with no bandwidth overage bills. Compare the hosts side by side: VibeDeploy vs Vercel, vs Netlify, or vs GitHub Pages.

Next steps

Sources

Tunnel details checked on the vendors' own pages on 13 October 2026:

From the VibeDeploy team

Ship your AI-built site in minutes

VibeDeploy hosts your AI-built websites in the EU with custom domains, automatic SSL, and a 14-day free trial that gets you online today.

Deploy guides for this topic

Questions people ask

How do I make localhost public?

Either tunnel it or deploy it. A tunnel such as ngrok or Cloudflare Tunnel gives the server running on your machine a public HTTPS address, but only while your computer and the tunnel keep running. A deploy copies your built files (the dist/ or build/ folder) to a host that serves them around the clock, on its own address or on your domain.

Is there a free way to share localhost?

Yes, for short-lived sharing. A free ngrok account gets one automatically assigned dev domain, and visitors see an ngrok interstitial page first. A Cloudflare Quick Tunnel needs no account at all, but it prints a new trycloudflare.com address every time you start one. Both stop when your computer or the tunnel stops. For a link that stays up, VibeDeploy's 14-day trial covers one site with your own domain and needs no card.

Why does localhost/project only open on my computer?

Because localhost always means "this computer". Any address that starts with localhost, such as localhost/project or localhost:3000, resolves to 127.0.0.1, so every visitor's browser looks for the site on their own machine and finds nothing. To share it, use a tunnel or deploy the built files to a host.

Can I host a localhost app that has a backend?

Yes. The front end deploys as static files, and the server side (your own Node or Python server, Postgres, MySQL, Redis or a worker) can run as containers next to the site, up to 6 services with 2 CPU and 2 GiB of memory in total. Your AI sets them up through the MCP tool deploy_app. Container data is not yet included in snapshots, so keep your own database exports.

Related reading