Steps
Replace npx localtunnel --port 3000 or lt --port 3000 with qurl publish http://127.0.0.1:3000, then run qurl share <CRID> for each person. Like localtunnel, qURL needs no account, but the app gets no public loca.lt URL and recipients meet no tunnel password page. Each link opens once and expires on its own.
Map your localtunnel commands
localtunnel forwards anyone who requests a random loca.lt subdomain to your app while the client stays connected; --subdomain asks for a name but does not guarantee it.
qurl publishtakes the app’s full local address and gives it no public URL, andqurl sharemakes a link for one recipient. There is no subdomain to choose: the link is the way in.# localtunnel # qURL npx localtunnel --port 3000 # qurl publish http://127.0.0.1:3000 lt --port 3000 # qurl publish http://127.0.0.1:3000 # qurl share <CRID> (one link per person) lt --port 3000 --subdomain myapp # no counterpart: no public name stop the lt client # qurl stop <CRID>, or qurl delete <CRID>Install the qURL CLI
On macOS, install it with Homebrew. On Linux and Windows, download the package for your platform from the latest release; the CLI page lists each one. Nothing asks you to sign up.
brew install layervai/tap/qurl qurl --versionVite: allow qurl.site before sharing
For a Vite app, add .qurl.site beside .loca.lt in server.allowedHosts. Merge this setting into your existing config. Vite reloads config changes; restart it if needed before sharing. Skip this step for other dev servers.
// vite.config.js (merge into your existing config) export default { server: { allowedHosts: ['.qurl.site'] }, }Publish the app
The first publish creates this device’s identity, starts a background service that keeps serving after you close the terminal (while you stay logged in), and prints the app’s CRID, its stable ID. The Access row says who can open the app: a plain publish makes it private from qurl 3.4.1 on.
qurl shareturns the CRID into an access link, and the link is what you send.qurl publish http://127.0.0.1:3000Published Target: http://127.0.0.1:3000 Access: private — only you and the people you allow can open it Status: serving CRID: ae4jqpd7eaoslq7jinmjv4yikgzmcxgpjfsuobiniqnko32lpw743ivbeyha
Create a link for each person
qurl shareprints an access link (https://qurl.link/#…). On a terminal, the lines below it say who published the resource and when the link expires, for example “Expires in 1d (single use)”. A publisher LayerV has verified is shown as verified by LayerV; any other name is marked UNVERIFIED. With no flags the link can be opened once and expires within 24 hours. If the expiry line does not say “single use”, don’t send the link. Add --ttl 1h for a shorter window.qurl share <CRID>Send the link to one person
Send it in a direct message, not a public channel: whoever opens it first uses it. Avoid email and apps that preview links, because a scanner that runs the page could use its one opening. Don’t open it yourself to check it, for the same reason. Run
qurl shareagain whenever you need a fresh link.Next.js: allow the recipient’s browser hostname
For Next.js, replace a previous *.loca.lt allowedDevOrigins entry with the exact qURL browser hostname in QURL_DEV_ORIGIN_HOST after the recipient opens their link and sends you its browser hostname. Do not open their single-use link yourself: they keep the page open while you restart next dev, then reload the same page. Never trust all qurl.site origins: that also trusts other publishers’ pages. Use the same exact hostname for Server Actions as described in the Next.js fix guide under Related Resources. Your app stays on this computer; nothing listens on your network. Skip this step for other dev servers.
// next.config.js module.exports = { allowedDevOrigins: process.env.NODE_ENV === 'development' && process.env.QURL_DEV_ORIGIN_HOST ? [process.env.QURL_DEV_ORIGIN_HOST] : [], }
What the recipient sees
The recipient clicks the link and lands on your app at an address like https://r_….qurl.site/.
More
There is no reminder page asking for a tunnel password, and no sign-up or install. Their session lasts 1 hour by default, and your app’s own login still applies if it has one.
Troubleshooting
| If you see | Do this |
|---|---|
| A webhook sender, such as Stripe or GitHub, can’t reach the app | Webhook senders call a fixed URL and never open a link, so give that one callback its own endpoint and keep the rest of the app private behind qURL. People and agents still reach the app through their link. |
| qurl publish says the local app is not accepting TCP connections | Start the app first and check that curl works on the same address. qurl publish connects to localhost as 127.0.0.1, so if your app listens only on IPv6 (on macOS or Linux, lsof -iTCP -sTCP:LISTEN -nP shows [::1]), publish 'http://[::1]:PORT' instead, or start the dev server with --host 127.0.0.1 and publish that address. Neither requires listening on your LAN. Keep the quotes: zsh treats the brackets as a pattern. |
Show 5 more fixes
| If you see | Do this |
|---|---|
| The recipient sees “Access link invalid” | The link was already used or has expired. Run qurl share again and send the new link. |
| The recipient sees “Resource not found” | The resource was deleted after the link was made. Publish the app again, then run qurl share and send the new link. |
| publish rejects http://127.0.0.1 with “only HTTPS URLs are allowed”, asks you to log in, or prints no Access: line | Your qURL CLI is out of date. On macOS run brew update, then brew upgrade qurl; elsewhere install the latest release. After updating, qurl --version prints 3.4.1 or later, and every publish is private by default. |
| publish says this Linux session “can’t reach a systemd user manager” | You are in a container or sandbox without a user service manager. Run qurl publish with --foreground; sharing lasts as long as that process runs. Container and CI setup → |
| publish says “Quota Exceeded” with “protected resource limit reached”, or “Your qURL account has reached a plan limit” | You can see this without an account: a device with no account can keep up to 3 active resources, with links that last up to 24 hours. Run qurl list --status active, then qurl delete <CRID> for any you no longer need (it asks you to confirm; --yes skips that). qurl stop keeps the resource, so it does not free a slot. |
Frequently Asked Questions
What changes for the people I share with?
With localtunnel, anyone who has the loca.lt URL can reach the app while the client is connected, and its maintainer says browser visitors meet a reminder page that asks for a tunnel password: the public IP address of the machine running the tunnel. With qURL, each person gets their own link, which opens once and expires within 24 hours, and lands on the app with no page in front.
Does qURL need Node.js like localtunnel?
No. The qURL CLI is a single install from Homebrew on macOS or a release package on Linux and Windows, and it serves any local HTTP app, whatever it is written in.
Does my computer have to stay on?
Yes. The app is served from your machine, so the machine and the app must be running and connected. The background service reconnects after sleep, but the app is unavailable while the machine is asleep.
Who else can reach my app while the link is open?
Opening the link starts a session for that browser, which lasts 1 hour by default. After a browser opens it, another browser on the same public IP cannot use its access. A script or agent that opens the link without a browser is admitted by its network address instead, which other devices on that public IP share until the session ends. A link admits whoever opens it: the API’s IP and country rules do not apply to the signed links qurl share issues. Keep your app’s own sign-in for anything sensitive.
How do I stop sharing?
Run qurl stop <CRID> to pause serving the app, and qurl start <CRID> to resume it; a stopped app still counts toward your resource limit. qurl delete <CRID> removes the resource for good after asking you to confirm; its CRID can never be shared again.