Skip to main content
← All guides

Give an external reviewer temporary access to localhost

Why qURL here

An email invitation is the strongest way in: only the address you invite gets in, after verifying that mailbox and saving a passkey, with no LayerV account, and you revoke it the moment the review ends. For a single quick look, a one-time link opens once and expires on its own.

Steps

Publish the app with qURL™ as invite-only and invite the reviewer’s email. Only that address can get in: the reviewer verifies their email and saves a passkey, with no account or install. Revoke their invitation when the review ends. For one quick look, send a one-time link from qurl share instead.

  1. Choose how the reviewer gets in

    An invitation names the person: only the invited email address can get in, after proving they control that mailbox and saving a passkey. A one-time link from qurl share is a bearer link: it opens once, for whoever holds it, so send it straight to them. For a named reviewer, follow steps 3–5. For one quick look, publish without --access in step 3 and use step 6 instead of steps 4 and 5. Both paths end with step 7. The table below the steps compares every way in.

  2. 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 --version
  3. Publish the app, invite-only

    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 share turns the CRID into an access link, and the link is what you send. Publish the origin the app listens on: qurl publish refuses a path, a query or a fragment, so the reviewer starts at / and you tell them where to go from there. Check that the reply has private: true and the invite_only policy, and keep the CRID it returns for the next steps.

    qurl publish http://127.0.0.1:3000 --access invite_only -o json
  4. Invite the reviewer

    qURL emails the invitation. The reviewer opens it in any browser, verifies their email and saves a passkey, then lands on your app. Strangers cannot ask for access, and the passkey brings the reviewer back until you remove them.

    qurl access invite <CRID> --email reviewer@example.com -o json
  5. Check that it is serving, and who is in

    qurl status shows the state you asked for and the state the service observes. The access listings show each invitation and who has access, so you never need to open anything yourself.

    qurl status <CRID>
    qurl access list_invitations <CRID> -o json
    qurl access list_grants <CRID> -o json
  6. End access

    To remove one invited reviewer, revoke their invitation with qurl access revoke_invitation, which also removes the access it granted; qurl access --help shows its arguments. qurl restart ends open sessions and keeps the app shared. qurl stop stops serving the app until qurl start. qurl delete asks you to confirm, then retires the app and every way in for good. When the review is over, stop or delete the app, because anything you later run on that port is open to whoever still has access.

    qurl restart <CRID>   # end open sessions, keep sharing
    qurl stop <CRID>      # stop serving; qurl start <CRID> resumes
    qurl delete <CRID>    # permanent; asks you to confirm

What the recipient sees

An invited reviewer opens the emailed invitation in any browser, verifies their email, saves a passkey and lands on your app, with no LayerV account or install.

More

Their passkey brings them back until you remove them. Your app’s own sign-in, if it has one, still applies. A one-time link opens straight to your app, once; opening it again shows “Access link invalid”.

Every way in, and what each one checks

Every way in, and what each one checks
Way inHow you grant itWho gets inReviewer needsEnds when
Email invitationqurl publish <app> --access invite_only, then qurl access invite <CRID> --email <address>A named recipient. Only the invited address can get in: the person proves they control that mailbox and saves a passkey. Strangers cannot ask for access. A verified mailbox is not proof of legal identity.A browser and the invited mailbox. No LayerV account.When you revoke their invitation, which also removes the access it granted, or delete the app.
Access requests you approvequrl publish <app> --access review, then qurl access approve for each requestPeople you approve. Anyone with the address can ask; they verify their email first, and nobody gets in until you approve that address.A browser and a mailbox. No LayerV account.When you revoke their access with qurl access, or delete the app.
One-time access linkqurl publish <app>, then qurl share <CRID> --ttl 4h --session-duration 2hA bearer link. It opens once, for whoever holds it, so send it straight to the person.A browser. No account and no install.The link ends after one opening or at --ttl. The session it opened ends at --session-duration, or sooner if you restart, stop or delete the app.

Sources: Agent skill, CLI README.

Link, session and path behaviour (qurl 3.6.1)

Checked on 2026-10-29. Other LayerV pages link here for these answers.

Link, session and path behaviour (qurl 3.6.1)
TopicBehaviourSource
Your accountNone. The first qurl publish creates a device identity. Without an account you get up to 3 active resources, with links that last up to 24 hours; a free account raises that to 10 resources and 30-day links.Agent skill
Reviewer’s account or installNone. A one-time link needs only a browser. An invited reviewer needs the invited mailbox and a passkey.Agent skill
Use limitA link from qurl share opens once. Check that the expiry line says “single use”, or single_use is true in -o json. Through the API, a link can allow more sessions.Our CLI tests
Link lifetime (--ttl)An unopened link lasts until --ttl. Without an account that is 24 hours by default and at most; with one, up to 30 days. The service may grant less than you ask, and the CLI says so on stderr. After that, the link shows “Access link invalid”.CLI README
Session lifetime (--session-duration)Starts when the link is opened: 1 hour by default, 24 hours at most. A link that expires does not end a session already open. When the session ends, new requests are refused and open streams and WebSockets are cancelled.API reference
What a session lets inThe browser that opened the link, for this one app. 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.Vibe coding FAQ
IP, country and user-agent rulesDo not apply to links from qurl share. The API’s access_policy is not evaluated on signed links, which is what qurl share issues.API reference
Pathsqurl publish takes an origin such as http://127.0.0.1:3000, never a path, query or fragment. The reviewer lands on /, and during the session every path of the app answers. Through the API, a link’s target_path opens that path and limits the session to it and the paths below it.API reference
Your app’s own sign-inStill applies. qURL passes no identity or cookie of its own to your app. The browser opens its own ….qurl.site address, while the gateway forwards Host c-<id>.qurl.site to the app with X-Forwarded-For and the other forwarding headers. A browser-origin check needs the browser’s address; a Host check sees the c-….qurl.site hostname.Our CLI tests
ProtocolsHTTP, WebSockets, Server-Sent Events and streamed responses pass through. No raw TCP, and not for webhook senders, which cannot open a link.Our CLI tests
Link previews and scannersA preview that only fetches the link never sees its secret, which follows the #. A scanner that opens it in a browser and runs its scripts can use the one opening.Agent skill
Checking who has accessqurl access list_invitations <CRID> and qurl access list_grants <CRID> show who you invited and who has access. For one-time links, with an account and API key, GET /v1/resources/<CRID>/qurls shows each link’s status (active, consumed, expired or revoked) and use_count, and GET /v1/resources/<CRID>/sessions lists open sessions.API reference
Ending accessqurl access revoke_invitation removes one invited person. qurl restart <CRID> ends open sessions and keeps sharing. qurl stop <CRID> stops serving the app until qurl start. qurl delete <CRID> retires the app and every link for good. With an account, the API revokes one link or ends sessions.CLI README
Traffic and recordsYour machine connects out; nothing listens for inbound connections. TLS ends at LayerV, which handles the decrypted traffic only to route it and keeps none of the content. LayerV sees which links were issued, opened, denied or revoked, and session metadata such as source IP. The API lists live sessions and webhooks report access events; audit export is part of the Enterprise plan.Trust

Sources: Our CLI tests, API reference, CLI README, Agent skill, Trust, Vibe coding FAQ.

Troubleshooting

Troubleshooting
If you seeDo this
The reviewer can’t find the invitationCheck qurl access list_invitations <CRID> -o json for their address, ask them to look in spam, and send it again with qurl access resend.
A one-time link fails the first time the reviewer opens itSomeone or something opened it first, such as a scanner that runs pages, or it passed its --ttl. Run qurl share again and send the new link in a direct message; the app does not need publishing again.
Show 9 more fixes
More troubleshooting
If you seeDo this
The reviewer lands on the home page, not the page to reviewThe app opens at /. Tell the reviewer the path to open, or make / redirect there for the review. With an account, a link made through the API can carry a target_path.
The reviewer is sent to http://localhost:3000The app built an absolute URL from a configured base address, so the browser went to the reviewer’s own machine. Use relative redirects for the review. A sign-in provider whose callback is registered for localhost has the same problem.
The page says “Blocked request. This host … is not allowed”The dev server refused the qurl.site hostname. Allow it as the dev-server hostname guide shows for your framework, then reload.
qurl publish says the local app is not accepting TCP connectionsStart 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.
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: lineYour 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

Does qURL check who the reviewer is, or is it a bearer link?

An invitation names the person: only the invited email address can get in, after proving they control that mailbox and saving a passkey. A one-time link from qurl share is a bearer link: it opens once, for whoever holds it, so send it straight to them.

Does the reviewer need an account or anything installed?

No. An invited reviewer needs only a browser, the invited mailbox and a passkey, with no LayerV account. A one-time link needs only a browser.

Does my app’s own login still apply?

Yes. qURL decides who reaches the app; it does not sign anyone in. It sets no cookie and adds no identity to requests, so your app asks for its own login as usual. Give the reviewer an account with only the permissions the review needs.

What happens when access expires?

An invited reviewer keeps access until you revoke their invitation or delete the app. An unopened one-time link stops working at its --ttl and shows “Access link invalid”. A session already open keeps going until its --session-duration ends; then new requests are refused and open streams and WebSockets are cancelled. To end a session sooner, run qurl restart <CRID>.

Can a link preview or security scanner use up a one-time link?

A plain link preview cannot: the secret part of the link comes after the #, and browsers and HTTP clients never send that part to a server, so a preview bot that fetches the link gets only the opening page. A scanner that opens the link in a real browser and runs its scripts can use the one opening, and the reviewer then sees “Access link invalid”. Send the link in a direct message to the reviewer, never open it yourself, and if it was used up, run qurl share again: the app does not need to be published again.

Can I send the reviewer to a specific page?

Tell them the page to open once they are in: qURL shares the whole app from its root, /. With an account, a link made through the API can carry a target_path that opens that page and limits the session to it and the pages below it.

How do I see whether the reviewer got in?

qurl access list_invitations <CRID> shows each invitation, and qurl access list_grants <CRID> shows who has access. For one-time links, with an account and API key, GET /v1/resources/<CRID>/qurls shows each link’s status (active, consumed, expired or revoked) and use_count, and GET /v1/resources/<CRID>/sessions lists open sessions. Never open a one-time link yourself to check it.

Who else can reach my app while it’s shared?

Only the people you let in. With an invitation, only the invited address gets in, with its own passkey, and strangers cannot ask for access. After a browser opens a one-time link, another browser on the same public IP cannot use its access; a script or agent that opens it without a browser is admitted by its network address instead. Keep your app’s own sign-in for anything sensitive.

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.

Publish your app now

Install the CLI, then run one command. No sign-up, no API key.

Install the CLI →

Book a pilot

Tell us what to hide. We’ll scope a pilot.

Enterprise starts with a paid pilot on one application, typically 60 to 90 days, credited in full toward year one if you convert within 60 days. After that, an annual package sized to what you protect, not per seat.