qURL™ vs Tunnelmole
Both need no signup. One gives the app a public URL.
Tunnelmole needs no signup: npx tunnelmole 3000 gives your app a random public tunnelmole.net URL that anyone with the address can open. qURL also needs no account, but gives the app no public URL: invite each person by email, or send a link from qurl share that works once and expires within 24 hours.
Tunnelmole is an open-source tunnel with a hosted service and a self-hostable server. qURL is a CLI that publishes a local app without a public route and hands out one link per recipient.
How qURL and Tunnelmole differ
Tunnelmole runs as a Node.js package or a prebuilt tmole binary and answers on a random tunnelmole.net subdomain; custom subdomains are on paid plans. The URL is public, and Tunnelmole documents no visitor access control, link expiry or single-use links. The client is MIT-licensed, and the server can be self-hosted.
qURL connects out from your machine too, but it gives the app no public address. qurl publish registers the app and prints its CRID, the app’s stable ID; qurl share turns the CRID into an access link for one recipient. Opening the link in a browser starts a session for that browser.
From a running app to a link you can send
qurl publish http://127.0.0.1:3000
qurl share <CRID>npx tunnelmole 3000qURL and Tunnelmole, side by side
| Question | qURL CLI | Tunnelmole |
|---|---|---|
| Account needed before the first URL | No. The first publish creates the device identity our test | No tunnelmole.com |
| What the URL looks like | A qurl.link access link per recipient; the app answers at r_<id>.qurl.site, a name absent from Certificate Transparency logs our test | Random tunnelmole.net subdomain that contains your IP address; custom subdomains are paid github.com |
| Who can reach it | Whoever holds the link may open it. Browser sessions are documented as browser-bound; non-browser sessions can be admitted by network address layerv.ai | Public: anyone with the URL github.com |
| Warning page shown to visitors | None our test | Not documented github.com |
| Visitor access control | Single-use access link by default; link and session lifetimes. The API's IP, country and user-agent rules do not apply to the signed links qurl share issues layerv.ai | Not documented github.com |
| Link expiry | Yes. qurl share returned a 24-hour link in our no-account test; no-account links are capped at 24 hours our test | Not documented github.com |
| Single-use links | Yes, the default for qurl share our test | Not documented github.com |
| Protocols | HTTP(S), WebSocket, SSE; no raw TCP our test | HTTP(S) github.com |
| Free-tier limits | Without an account: up to 3 active resources, with links that last up to 24 hours github.com | Not published; paid plans list custom subdomains and no tunnel timeouts dashboard.tunnelmole.com |
Which one to use
Choose qURL to
Show an app to one person, or let your coding agent share it, without the app being reachable by anyone who finds the URL. Each link works once and expires on its own.
Already using Tunnelmole?
Tunnelmole turns one command into a public URL. qURL is one command too, and the app stays private: invite the people you choose by email, or send a one-time link, so nobody who finds an address gets in.
qURL connects outbound, so you can share your app without opening an inbound port. Keep any other public routes to your app restricted. A link’s expiry controls when it can be opened; an opened session has its own duration. Explore access and revocation.
Frequently Asked Questions
Does Tunnelmole need an account?
No. npx tunnelmole 3000 gives a public URL with no signup; custom subdomains need a paid plan. qURL needs no account either, and gives no public URL.
Who can open a qURL link?
Whoever holds it, once: with no flags, qurl share prints a single-use link. The documented browser flow starts a session for that browser, which lasts 1 hour by default for an app published from the CLI; another browser on the same public IP cannot use that browser session. A script or agent that opens the link without a browser can be admitted by its network address, which other devices on that public IP may share until the session ends. Keep your app’s own sign-in for anything sensitive. A link admits whoever opens it: the API’s IP and country rules do not apply to the signed links qurl share issues.
Can my coding agent share my app with qURL?
Yes. Give Claude Code, Cursor, or Windsurf the qURL skill (https://layerv.ai/skills/qurl/SKILL.md) and ask it to share the app: it installs the qurl CLI, publishes the app privately, and gives you an address to send. The agent applies the private access rules you choose. For named recipients, give it their email addresses so it can send invitations. Recipients verify their email in the browser and save a passkey; they never send you their email verification code. The agent checks policy support before sharing and keeps the app private if the deployment cannot support it. For one person right away, ask it for a one-time link instead. Codex starts with network access off, so save the skill file for it first.
Share your app without an account
Paste one prompt into your coding agent, or install the qURL CLI and publish the app yourself. No sign-up, no API key.
New to qURL? Start at qurl.link