Guide

How to put your localhost site online (for real)

You built something and it runs on localhost, but only you can see it. Here is the difference between the two ways to fix that, tunneling and real hosting, and the simplest way to get a permanent, always-on site on your own domain.

Short answer

localhost only runs on your own computer. To put it online you either tunnel to it (temporary, your machine must stay on) or host it (a permanent copy on always-on servers). For a real website on your own domain you want hosting. With VibeDeploy you upload your build output, or let your coding agent deploy over MCP, and it goes live on a real URL in minutes.

What does localhost mean?

localhost is the name your computer uses for itself (the address 127.0.0.1). When a project runs on localhost, it is served only to the machine it is running on. That is perfect while you build, but it means the site does not exist for anyone else on the internet. To share it, the files have to live somewhere people can reach.

Two ways from localhost to online: tunnel vs host

This is the distinction most guides skip, and it is the one that matters.

Tunnel (temporary)

Tools like ngrok and Cloudflare Tunnel create a public link to the server that is still running on your computer. Great for a quick demo. But the site is only up while your machine and the tunnel are running.

Host (permanent)

A host (Vercel, Netlify, VibeDeploy) runs its own copy of your site on always-on infrastructure. It stays online on a stable URL with a custom domain, whether your laptop is on or not. This is what most people actually mean by putting a site online.

ngrok vs Cloudflare Tunnel vs Vercel vs Netlify vs VibeDeploy

How the common options compare for the job of getting a local site online and keeping it there.

FeaturengrokCloudflare TunnelVercelNetlifyVibeDeploy
TypeTunnel (temporary)Tunnel (temporary)Host (permanent)Host (permanent)Host (permanent)
Stays online when your computer is offcancelcancelcheck_circlecheck_circlecheck_circle
Stable URL that does not changeYes, one assigned dev domainWith a named tunnelcheck_circlecheck_circlecheck_circle
Custom domainPay-as-you-go plan and upYes (via Cloudflare)YesYesYes, on every plan
Production-grade / always-oncancelcancelcheck_circlecheck_circlecheck_circle
Permanent URL on your own domaincancelcancelcheck_circlecheck_circlecheck_circle
Where the site is served fromYour own machineYour own machineGlobal CDN (US company)Global CDN (US company)EU (Belgium)
Best forA quick temporary demoExposing a server that keeps running locallyNext.js apps (developers)Static sites (developers)Keeping a site online on your own domain, hosted in the EU

Want the longer breakdown of when to use each? Read the full tunnel vs hosting comparison.

Put your local site online with VibeDeploy

  1. 1

    Start your 14-day VibeDeploy trial

    Create an account at vibedeploy.be. The trial needs no credit card and includes a name.subsite.site address of your choice plus one custom domain.

  2. 2

    Upload your build, or let your coding agent deploy it

    Run your build (usually npm run build) and drag the output folder, dist or build, into the dashboard; a ZIP of its files works too. Working in Claude Code, Cursor or another MCP client? Connect VibeDeploy once and the agent deploys the project for you over MCP.

  3. 3

    Get a live URL in minutes

    VibeDeploy hosts the files on always-on infrastructure and gives you a real URL at name.subsite.site with automatic HTTPS. Your computer can be off and the site stays online.

  4. 4

    Add your own domain (optional)

    Point a CNAME at VibeDeploy and add your domain in site settings. SSL provisions automatically, usually within 60 seconds.

The facts, sourced

Frequently asked questions

How do I put my localhost site online?expand_more

localhost only runs on your own computer, so no one else can reach it. To put it online you either tunnel to it (a temporary link to the server still running on your machine) or host it (a permanent copy on always-on infrastructure). For a real website on your own domain you want hosting. With VibeDeploy you upload your build output, or let your coding agent deploy over MCP, and it goes live on a real URL in minutes.

Why can't other people see my localhost?expand_more

localhost (the address 127.0.0.1) always points to the device you are on. When you open localhost on your laptop, you reach your laptop. Anyone else opening localhost reaches their own machine, not yours, so your site is invisible to them until it is hosted somewhere public.

Is ngrok the same as hosting?expand_more

No. ngrok and Cloudflare Tunnel are tunnels: they expose a server that is still running on your computer. The moment your machine or the tunnel stops, the site is gone. Hosting copies your site onto always-on servers, so it stays live independently of your laptop.

Do I need to keep my computer on?expand_more

With a tunnel like ngrok, yes, because the site actually runs on your machine. With real hosting, no. The host runs its own copy, so you can close your laptop and the site stays online.

Can my coding agent put the site online for me?expand_more

Yes, if it speaks MCP. Connect VibeDeploy once in Claude Code, Cursor, VS Code or another MCP client (the server URL is https://mcp.vibedeploy.be/mcp), sign in, and ask the agent to deploy the project. It uploads the files and replies with the live URL.

What is the easiest way to get my local site online?expand_more

If you already have a build, upload the dist or build folder to a host and add your domain. If you work in a coding agent such as Claude Code or Cursor, let it deploy over MCP instead. Either way you get a permanent, always-on URL.

My localhost app has a backend. Can that go online too?expand_more

Yes. The front end is served as static files, and a server or database (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, isolated with gVisor. Your AI deploys them through the MCP tool deploy_app. Container data is not yet included in snapshots.

My site only works on localhost:3000 (or localhost:5173). How do I put it online?expand_more

That number is just the port your development server picked: 3000 for Next.js and Node tools, 5173 for Vite, 8888 for notebooks. Ports on localhost never leave your computer, so changing or forwarding them does not publish anything. To put the site online, build the project and upload the result to a host; once deployed, visitors use your domain and the port disappears from the story.

Get your site truly online, today

Upload your build output, or let your coding agent deploy over MCP. Live on a real URL in minutes, hosted in the EU. Free for 14 days, no credit card.

Liever in het Nederlands? Localhost online zetten: de Nederlandstalige gids