qURL™ vs MeshLatch
Two private links. One needs an account and a Windows PC.
MeshLatch’s MeshLink CLI turns a local web app into a private HTTPS link with an optional password and expiry, from a Windows PC signed in to a MeshLatch account, and the link lasts while MeshLink runs. qURL runs on macOS, Linux and Windows with no account, keeps sharing in the background, and adds email invitations alongside one-time links.
MeshLatch and qURL take the same approach to the same job: a private link to an app on your machine, with the secret after the # so it never reaches a server log. They differ in platforms, accounts, link lifetimes and how a named person gets in.
Share one app from the command line
qurl publish http://127.0.0.1:3000
qurl share <CRID>Architectural Difference
MeshLatch. MeshLink is a command-line client, available for Windows x64 (Linux is listed as coming soon). You connect it to a MeshLatch account with a single-use login code from the account dashboard, then run MeshLink 3000, or MeshLink --target http://127.0.0.1:8080. It prints a link of the form https://link.meshlatch.com/#MLK1…; --password adds a password and --expires sets the lifetime in seconds. Pressing Ctrl+C stops the connection and releases the link. The free plan allows 3 links a day, 1 active link, 3 viewers per link and a 30-minute expiry; Pro raises the expiry to 24 hours.
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. qurl publish installs a background service, so sharing continues after you close the terminal, and qurl access invite lets a named email address in with a passkey.
Feature Comparison
| Feature | qURL | MeshLatch |
|---|---|---|
| Platforms | macOS, Linux and Windows | Windows x64; Linux listed as coming soon |
| Account | None; without one you get up to 3 active resources, with links that last up to 24 hours | Required: the client logs in with a code from your MeshLatch account |
| Link | https://qurl.link/#… per recipient | https://link.meshlatch.com/#MLK1… |
| Link lifetime | Up to 24 hours without an account, 30 days with a free one | 30 minutes on the free plan, 24 hours on Pro |
| Single use | The default for qurl share | Not established in the checked sources; the free plan allows 3 viewers per link |
| Named recipients | Email invitations: a verified mailbox and a passkey | An optional password on the link |
| After you close the terminal | A background service keeps serving | Ctrl+C stops the connection and releases the link |
| Ending access | Revoke one invitation, or qurl stop or qurl delete | Stop MeshLink, or let the link expire |
Which one to use
Choose qURL to
Share a local app privately from a Mac, a Linux box or a PC, with no account, links that can wait a day to be opened, and email invitations for the people who come back.
Already using MeshLatch?
MeshLink gives you a private link while it runs on a signed-in Windows PC. qURL gives the same kind of link from any of your machines with no account, keeps serving in the background, and invites the people who come back by email.
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 MeshLatch need an account?
Yes. MeshLink connects to a MeshLatch account with a single-use login code from the account dashboard. qURL needs none: without an account you get up to 3 active resources, with links that last up to 24 hours.
Does MeshLatch run on macOS or Linux?
MeshLatch lists MeshLink for Windows x64, with Linux coming soon. The qURL CLI runs on macOS, Linux and Windows.
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