Pubto Alternative: qURL™ vs Pubto
A public address behind a password, or no public address at all.
Pubto publishes a local app, file or folder to a temporary address after you create an account, and its security docs treat that address as public, protected by a password, a short duration and revocation. qURL needs no account and gives the app no public address: each person gets an email invitation or a link that opens once.
Pubto is a desktop app with a pubto CLI, from Vertex AI LLC, that publishes what runs on your computer through its relay. qURL is a CLI that publishes a local app with no public route and lets in the people you choose. Both suit a developer handing a preview to someone outside the team.
Share one app from the command line
qurl publish http://127.0.0.1:3000
qurl share <CRID>Architectural Difference
Pubto. You install the desktop app and sign in: Pubto requires an account before publishing. pubto publish --port 3000 publishes an app, and --file, --dir and --website publish a file, a folder or a static site; --duration sets how long the endpoint lasts. Each endpoint has its own password, expiry, address rotation, quota and revoke controls, and pubto stop or pubto delete with the endpoint ID ends it. Pubto’s security page treats the address as public and names passwords, application authentication, short duration, usage limits and prompt revocation as the actual access boundary.
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. For a named recipient, qurl access invite sends an email invitation: the person verifies that mailbox and saves a passkey, so there is no shared password to pass along.
Pubto alternative: Pubto gives your app a public pubto.dev address; qURL keeps it on 127.0.0.1 and lets in only the people you invite.
A Pubto public preview
- Pubto Desktop, after you sign in, publishes your app to a public pubto.dev address.
- Anyone who has the address can open it; a password is a Pro feature.
- The address works until its duration ends: at most 2 hours on the free plan, 24 on Pro.
Your app through a qURL access link
- Run your app on 127.0.0.1:3000.
- Publish it with qurl publish http://127.0.0.1:3000.
- Invite people by email with qurl access invite: only they get in.
One client, one preview
A client outside your team needs to review the app on port 3000 of your machine.
| Step | qURL | Pubto |
|---|---|---|
| Before the first share | Install the qurl CLI; no account | Install the desktop app and sign in to a Pubto account |
| Publish | qurl publish http://127.0.0.1:3000 --access invite_only | pubto publish --port 3000 --duration 2h, with a password for sensitive content |
| Let the client in | qurl access invite <CRID> --email <address>; qURL emails the invitation | Send the address and, separately, the password |
| What the client does | Opens the invitation, verifies the mailbox and saves a passkey | Opens the address and enters the password |
| Someone else gets the address | They cannot open the app or ask for access | They reach the password prompt; the address is public |
| End access | qurl access revoke_invitation for that client; qurl stop or qurl delete for everyone | pubto stop or pubto delete <endpoint-id>, or let --duration run out |
Feature Comparison
| Feature | qURL | Pubto |
|---|---|---|
| Account to publish | None; without one you get up to 3 active resources, with links that last up to 24 hours | Required before publishing |
| Install | The qurl CLI on macOS, Linux or Windows | The Pubto desktop app, which includes the pubto CLI |
| Public address | None: the app opens only for the people and devices you allow | Yes; Pubto’s security docs treat it as public |
| Who gets in | An invited mailbox with a passkey, or whoever opens a one-time link first | Anyone with the address, past the password if you set one |
| Expiry | Each link at --ttl; each session at --session-duration, up to 24 hours | Per endpoint, with --duration |
| Single-use links | The default for qurl share | Not established in the checked sources; usage limits are listed |
| Ending access | Revoke one invitation, or qurl stop or qurl delete | Stop, delete or rotate the endpoint’s address |
| What it shares | Any HTTP app or API, with WebSockets and Server-Sent Events; files and folders through a local file server | Apps, APIs, files, folders, static sites and TCP |
| Price | Free without an account; free accounts raise the limits | Pro plans and traffic packs; a free tier is not stated |
Which one to use
Choose qURL to
Share a preview with a client without an account of your own and without a public address for anyone to find: invite their email, or send a link that opens once and expires on its own.
Share a local app without signing up →
Already sharing with Pubto?
Pubto gives each endpoint a public address and relies on a password and a short duration to protect it. With qURL there is no public address to protect: publish the app, invite each person by email or send a link that opens once, and revoke one person without changing anyone else’s access.
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 Pubto need an account?
Yes. Pubto’s getting-started guide says it requires an account before publishing. qURL publishes without one: the first qurl publish creates the device identity, and without an account you get up to 3 active resources, with links that last up to 24 hours.
Is a Pubto address private?
Pubto’s security page treats the address as public: passwords, application authentication, short duration, usage limits and prompt revocation are the access boundary. A qURL app has no public address: it opens only for invited people and for whoever holds a one-time link.
Can both share a file or folder?
Pubto has --file and --dir. With qURL, serve the folder on 127.0.0.1 with a static file server and publish that address; the recipient downloads during their session, and nothing is uploaded.
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