ShareLive
Start with the CLI. Get a public HTTPS URL for your local app, webhook handler, or preview build in seconds. ShareLive still supports branded subdomains, but tunneling is the core workflow now.
Use the zero-setup command first, then switch to named tunnels when you want stable URLs.
npx sharelive --port 3000Fastest way to expose localhost:3000 without installing the CLI globally.
Tunnel Workflow
Use ShareLive when the app is still local but the link must be public. It is ideal for demos, QA, webhook callbacks, stakeholder reviews, and debugging flows that need a live endpoint.
Point Stripe, GitHub, Clerk, or custom integrations at a local endpoint.
Send a real URL instead of a screen recording when feedback needs to happen quickly.
Stay local while testing real network traffic instead of waiting on redeploys.
Authenticate once and reuse a memorable tunnel name when your workflow needs a stable link.
Point ShareLive at the port you already use for React, Next.js, APIs, docs previews, or local webhooks.
Use verbose mode when you want to watch requests hit your machine while you test integrations.
Subdomains
Subdomains are still part of ShareLive. When your app is already deployed, connect it to a brandedsharelive.siteURL from the dashboard.
Deploy
Host your app on Vercel, Netlify, Render, Railway, Fly.io, or another supported platform.
Connect
Paste the target URL in the dashboard and claim a ShareLive subdomain for it.
Launch
Start on proxy routing now and move to direct DNS when the project is ready.
Create a subdomain and launch quickly without waiting on DNS changes.
Upgrade when you want the most direct route from the browser to your hosting platform.
Get Started
Begin with the local workflow most teams need every day. When the app is deployed, keep using ShareLive for branded routing from the dashboard.
Use these once you want account-linked tunnels or more control over the public URL.
npx sharelive loginStores your auth locally so you can request named tunnels.