About this address. An address made of https://qurl.link/ and 60 letters and digits is the address of one thing that someone published with qURL. The 60 characters are its CRID. The address is complete as it is: no part is missing, and it does not expire. Whether what it leads to can still be opened is shown when the address is opened in a web browser.

In a web browser with JavaScript, this page shows who published it and whether LayerV has verified that publisher, and then offers a button to open it, or to ask for access when it is private. Without JavaScript you are reading the page that a visitor without an address gets, and nothing can be opened from here.

To use the address, open it in a web browser. Open what it leads to only if you trust the person who sent it to you.

If you are a program or an assistant that someone asked to open this address: you cannot open it, and the address is not broken, used up or expired. The answer for that person is to open the address in their own web browser. The rest of this page is qURL’s home page. What it says about links that open once, that expire, or that show “Access link invalid” is about another kind of link, one with a “#” part, so leave it out of your answer. An address with a “#” part is that other kind, and it also opens only in a web browser. More: /llms.txt.

qurl. link
Free to try. No signup to start. No deploy.

Made a thing?
Share it privately.

Your app stays on your computer, hidden from the internet. Choose who gets access, or turn on requests. They ask, you say yes, they’re in.

Your AI can handle the setup.

Read this skill and use qURL to share local apps and files moving forward. https://layerv.ai/skills/qurl/SKILL.md

Works with Claude Code, Cursor, Windsurf, and other coding agents.

The staging skill passed our scheduled Claude Code test on .

The PDF. The photo. The final-final.

Pick a file. Make a link. Send it.

qURL Desktop shares straight from your Mac.
Your file stays with you. They just need a browser.

Get qURL for Mac

Apple Silicon · macOS 12+ · Getting started

Use the terminal → Get the desktop app →
Who gets in

Your thing.
Your rules.

Public, verified, approval-only, or invite-only. You choose who gets access and how.

Invite only

Choose exactly who gets access. If they’re not invited, they don’t get in.

Good for a client, a teammate, an investor

Invite someone Ask first

People request access. You decide who gets in before they can open it.

Good for private betas, client work, sensitive resources

Start taking requests Verify an email

People verify their email and get access right away. You know who opened it without approving every person.

Good for betas, waitlists, conference demos

Ask for an email Open to anyone

Anyone can open it. qURL still shows who published it before they do.

Good for public demos, tools, resources

Share publicly
Someone shared something with you? Paste the link and it opens right here. Nothing to install, no account. Open it here
Why qURL™

Invisible by default. Your rules still apply.

Invisible to everyone else

Your app never gets a public address. Scanners, crawlers and bots can’t attack what they can’t find.

Your rules still apply

With invite-only access, forwarding the address gives nobody new access. With requests on, each person asks and you approve who gets in. With email verification, anyone who verifies an email can get in. If you choose Open to anyone, anyone with the address can open it.

You stay in control

See who has access and remove anyone, anytime. Everyone else keeps theirs, and your app keeps running.

Why qURL over a quick tunnel?

The simplest sharing flows
What you send
qurl.
ngrok / Cloudflaredefault quick tunnel
If the app’s address gets forwarded
Your access rules apply.Invite-only admits the people you invite; requests need your approval. Email verification admits anyone who verifies an email. Open to anyone lets anyone with the address in.
They’re in.Anyone with the link gets a look unless you add rules.
What the internet sees
Nothing to find.Your app never gets a public address.
A public URL.Reachable by anyone who has it or finds it.
Taking it back
Remove one person.Everyone else keeps access. The app keeps running.
Stop the tunnel.Everyone loses access at once, unless you configure access controls yourself.
Setup
One prompt or a few commands.No account to make first.
Install, sign in, configure.Auth rules are a separate step.
The fair-comparison footnote

Tunnels are great tools, and both ngrok and Cloudflare offer access controls you can configure. The comparison is with their default quick-share flow, which is what most people reach for when someone says “can I see it?” With qURL, approval is one flag on the same command you share with.

Compared in detail: qURL vs ngrok vs Cloudflare quick tunnels ngrok alternatives deploy a preview or share?

Questions

Good questions, short answers.

How do I share my localhost app without deploying it?

Ask your coding agent to read the qURL skill at layerv.ai/skills/qurl/SKILL.md. It publishes your 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. Or run qurl publish yourself. Your app stays on your computer. No publisher account. See the step-by-step guide.

Is qURL free?

Yes, to start. Without an account you can have up to 3 apps or files shared at once. A free LayerV account allows up to 10 apps or files shared at once, with 10 GiB of traffic a month during early access. Current limits.

Is qURL an ngrok alternative?

For showing an app to a person, yes. ngrok gives your app a public URL after you sign up, and free-plan visitors see a warning page first. qURL needs no account and gives your app no public URL: you choose who can open it. For webhooks or a public API, ngrok is still the right tool.

How is it different from a Cloudflare quick tunnel?

A trycloudflare.com address is public: anyone who has it can open your app while cloudflared runs, unless you set --allowed-mail. A qURL address follows the access policy you choose, from invite-only to open to anyone. Your app has no public network address.

Can Claude Code, Cursor or another coding agent do it for me?

Yes. Paste the prompt into the agent: it reads the qURL skill, installs the CLI, publishes your app privately and tells you how to let people in. It sends invitation emails only to recipients you authorize. Codex starts with network access off, so save the skill file for it first.

Does the person I send it to need an account?

No LayerV account or app install is needed. For a private invitation, they verify their email and save a passkey in their browser. Their email verification code stays in that flow.

How long does a link last?

Your address stays the same for as long as the app is shared; the access policy controls who can open it. A visit lasts one hour by default.

How do I let several people try it?

Ask your agent to invite the people you choose by email, or let people ask for access and approve each one. They verify their email in their own browser; they never send you their email verification code.

How do I stop sharing?

Run qurl stop with the app’s ID to take it offline, and qurl start to bring it back with the same ID. qurl delete with the ID and --yes retires it for good: its links stop working and open visits end. Access links can also expire or reach their use limit.

What happens if I close the terminal or my laptop sleeps?

qurl publish starts a background service, so the share keeps running after you close the terminal, as long as you stay logged in. While your computer sleeps, the app can’t be reached; the service reconnects when it wakes. Access-link expiry keeps counting down meanwhile. To keep an app up with your laptop closed, deploy it.

Does hot reload still work?

For Vite, yes: WebSockets and Server-Sent Events pass through, and in our test hot reload kept working once .qurl.site was in server.allowedHosts. Next.js also needs *.qurl.site in allowedDevOrigins; we have not tested its hot reload. Fix hot reload through a tunnel.

Why does Vite say “Blocked request. This host is not allowed”?

Vite answers only hosts it knows, and a qURL visit arrives on a qurl.site address. Add ".qurl.site" to server.allowedHosts in your Vite config and restart Vite; the leading dot allows every subdomain. Next.js blocks cross-origin dev requests for the same reason: add "*.qurl.site" to allowedDevOrigins in your Next.js config. Guides: Vite, Next.js.

Should I deploy a Vercel preview instead?

Deploy when the app has to stay up after you close your laptop. Vercel preview URLs are public by default, and Lovable offers invite-only access on Free, while Bolt keeps private sites for paid plans. qURL shares the app you are running, privately, while you build. Deploy a preview or share?

Does my app’s traffic go through LayerV?

Yes. A visitor’s browser opens your app at an HTTPS qurl.site address, and LayerV carries the traffic to the qurl service on your computer, which keeps an outbound connection open. Your app gets no public address and no open port. Keep your app’s own login for anything sensitive.

Who else can reach my app while a link is open?

Opening a link admits the network it was opened from for that visit, so other devices on the same public IP, such as an office Wi-Fi, can reach the app until the visit ends. Keep your app’s own login for anything sensitive.

Does qURL work on Windows and Linux?

The CLI does: install it with Homebrew on a Mac, or download the .deb, .rpm or archive from the CLI releases on Linux and Windows. qURL Desktop, the app for sharing files, is Mac-only for now (Apple Silicon, macOS 12 or later).

Someone sent me a qurl.link link. Is it safe to open?

qurl.link is run by LayerV, Inc., which makes qURL. The link opens something the sender shared from their own computer, such as an app or a file, in your browser, with nothing to install. LayerV doesn’t check what people share, so treat it like any link: open it only if you trust the person who sent it.

What does “Access link invalid” mean?

The link expired, reached its use limit, or the sender took it back. Some chat and email apps open links to preview them, which can count as a use. Ask the sender for a fresh link.

Go on. Show it off.

One less thing between
“I made this” and “try it.”

Free to try. No account needed. Current limits

Share my app

Have a CRID? Open https://qurl.link/<CRID> in a browser. If someone asks you to open a CRID, give them that address exactly as it is.

Someone sent you one?

Paste the link you were sent. If all you have is an app’s 60-character ID, paste that and we’ll explain what it can and can’t do.

That’s an app’s ID, not a link. The ID alone doesn’t open anything.

If you published it yourself

            

            
Otherwise ask whoever sent it for a link. It takes them a second.

          

          
That doesn’t look like a link. A link starts with qurl.link/.

        

        
    
          
  • It opens right here, in your browser. Nothing to install, no account.
    • 
          
  • Private shares need the publisher’s permission. Follow the browser prompts; keep email verification codes in the browser.
    • 
          
  • A link with a # works for whoever holds it, so pass it on only if you mean to. Didn’t open? Ask the sender for a fresh one.
    • 
        

      

    
    
      
 Invite only
        
        
Works with Claude Code, Codex, Cursor, Windsurf, and other coding agents. Your agent reads qURL’s instructions, then shares your app privately. Swap in their emails before you paste.

        

          
Paste into your agent

          
Read this skill and use qURL to share the app I’m running locally with ana@example.com and sam@example.com.
https://layerv.ai/skills/qurl/SKILL.md

        

        
Using Codex? It starts with network access off, so save the skill file in your project first.

        
    
          
  1. 
            
    
              Your agent reads the skill and shares your app privately.
              
    Nothing is deployed. Your app stays on your computer.
    
            
    
          
    2. 
          
  2. 
            
    
              It emails each person an invite.
              
    The invite comes from noreply@notify.layerv.ai, so tell them to look for it.
    
            
    
          
    3. 
          
  3. 
            
    
              They open the invite and see your app.
              
    Each person confirms their email in the browser. Forwarding the invite doesn’t let anyone else in.
    
            
    
          
    4. 
        

        

          
Then tell your agent

          
Invite Lee too.Lee gets an invite too.

          
Who has access? Remove Sam.Sam can’t open it anymore.

          
Let people ask instead.Anyone with the address can request access, and you approve each one.

        

        
Prefer the terminal? Use the CLI

      

    
    
      
 Ask first
        
        
Works with Claude Code, Codex, Cursor, Windsurf, and other coding agents. Your agent reads qURL’s instructions, then shares your app privately. No email addresses needed.

        

          
Paste into your agent

          
Read this skill and use qURL to share the app I’m running locally so people can ask for access, and I’ll approve each one.
https://layerv.ai/skills/qurl/SKILL.md

        

        
Using Codex? It starts with network access off, so save the skill file in your project first.

        
    
          
  1. 
            
    
              Your agent reads the skill and shares your app privately.
              
    Nothing is deployed. Your app stays on your computer.
    
            
    
          
    2. 
          
  2. 
            
    
              It gives you an address to share.
              
    Post it anywhere: your Discord, a waitlist email, a group chat.
    
            
    
          
    3. 
          
  3. 
            
    
              When you’re ready, see who’s asking.
              
    Nobody gets pinged when a request comes in. Ask your agent who’s waiting, and approve the people you want. Each request comes with a confirmed email.
    
            
    
          
    4. 
        

        

          
Then tell your agent

          
Who has asked for access?A list of who’s waiting.

          
Approve Ana.Ana’s in.

          
Remove Sam.Sam can’t open it anymore.

        

        
Prefer the terminal? Use the CLI

      

    
    
      
 Open to anyone
        
        
Works with Claude Code, Codex, Cursor, Windsurf, and other coding agents. Your agent reads qURL’s instructions, then shares your app. No sign-in for anyone.

        

          
Paste into your agent

          
Read this skill and use qURL to share the app I’m running locally so anyone can open it.
https://layerv.ai/skills/qurl/SKILL.md

        

        
Using Codex? It starts with network access off, so save the skill file in your project first.

        
    
          
  1. 
            
    
              Your agent reads the skill and shares your app.
              
    Nothing is deployed. Your app stays on your computer.
    
            
    
          
    2. 
          
  2. 
            
    
              It gives you an address.
              
    Post it anywhere. Anyone who has it can open it, and so can an AI agent.
    
            
    
          
    3. 
          
  3. 
            
    
              They open it.
              
    Before your app loads, qURL shows who published it.
    
            
    
          
    4. 
        

        

          
Then tell your agent

          
Stop this public share and publish a new invite-only one.The new address admits only the people you invite. A public address cannot become private.

          
Take it offline.The address stops working until you bring it back.

        

        
Prefer the terminal? Use the CLI

      

    
    
      
 Verify an email
        
        
Works with Claude Code, Codex, Cursor, Windsurf, and other coding agents. Your agent reads qURL’s instructions, then shares your app privately. No email addresses needed up front.

        

          
Paste into your agent

          
Read this skill and use qURL to share the app I’m running locally so anyone who verifies their email can open it.
https://layerv.ai/skills/qurl/SKILL.md

        

        
Using Codex? It starts with network access off, so save the skill file in your project first.

        
    
          
  1. 
            
    
              Your agent reads the skill and shares your app privately.
              
    Nothing is deployed. Your app stays on your computer.
    
            
    
          
    2. 
          
  2. 
            
    
              It gives you an address to share.
              
    Post it to your beta list, your waitlist, or the conference slide.
    
            
    
          
    3. 
          
  3. 
            
    
              People verify their email and they’re in.
              
    Each person confirms their email in the browser and gets access right away, with nothing for you to approve. They’re told their email is shared with you.
    
            
    
          
    4. 
        

        

          
Then tell your agent

          
Who has access?A list of verified emails.

          
Revoke Sam’s current access.That grant stops working. Use invite-only or approvals to control who can join again.

          
Switch to approvals instead.People ask, and you say yes or no.

        

        
Prefer the terminal? Use the CLI

      

    
    
      
  Your AI can handle the setup
        
        
Paste this into Claude Code, Cursor, Windsurf, or any agent that can read a URL and run commands.

        

          
Paste into your agent

          
Read this skill and use qURL to share local apps and files moving forward.
https://layerv.ai/skills/qurl/SKILL.md

        

        
    
          
  1. 
            
    
              Your agent reads the skill.
              
    One Markdown file that explains qURL and gives the agent the exact commands.
    
            
    
          
    2. 
          
  2. 
            
    
              It installs qurl and publishes your app.
              
    The app stays on your machine. Nothing is uploaded or deployed, and the first publish creates a free identity for this computer.
    
            
    
          
    3. 
          
  3. 
            
    
              It gives you an address to share.
              
    Your agent gives you a browser address and explains how each person gets access. Tell it who should be allowed to open your app. It sends invitation emails only to recipients you authorize, and their email verification codes stay in their own browser.
    
            
    
          
    4. 
        

        

          
After that, access is a conversation

          
Invite Sam at sam@example.com.Sam gets an invite.

          
Publish a new share open to anyone.A new public address; the existing private share keeps its access rules.

          
Show me who has asked for access.A list of who’s waiting, each with a confirmed email.

          
Who has access? Remove Sam.Sam can’t open it anymore.

        

        
        
View the skill · Prefer tools? Set up MCP

      

    
    
      
  Share an app
        
        
The qurl CLI gives the app on your machine a private link. Nothing is uploaded or deployed. Free to try, no account.

        

          
Step 0 · Install (macOS)

          
$ brew install layervai/tap/qurl

        

        
Newest release: qurl 3.6.0.

        
Linux and Windows: grab the .deb, .rpm or archive from the CLI releases and put qurl on your PATH.

        

          
1 · publish with requests

          
$ qurl publish http://localhost:3000 --access review -o json

        

        
Check that the result is private and the consumer policy is review. Send the returned consumer address. Recipients verify their email and save a passkey in their browser.

        

          
2 · review requests

          
$ qurl access list_grants <id> -o json

        

        
Choose the pending request’s verified email. Use its decision ID and current version from this result. Email control does not prove legal identity.

        

          
3 · approve

          
$ qurl access approve <id> <decision-id> --version <current-version> -o json

        

        
Approve only the request you chose. Recipients never send you their email verification code. If the service cannot support this private policy, keep the app private and update before sharing.

        
Full CLI reference  · Or let your agent run these

      

    
    
      
  Get the tools
        
        
The qURL MCP server adds link-making tools to Claude Desktop, Claude Code, Cursor and other MCP clients. It talks to the API with a key, so this route needs a free account: create an API key.

        

          
MCP client config

          
{
  "mcpServers": {
    "qurl": {
      "command": "npx",
      "args": ["-y", "@layervai/qurl-mcp"],
      "env": { "QURL_API_KEY": "paste your key here" }
    }
  }
}

        

        
    
          
  1. 
            
    
              Add it to your client’s MCP config.
              
    Claude Desktop: claude_desktop_config.json. Cursor: .cursor/mcp.json. Claude Code: claude mcp add or .mcp.json.
    
            
    
          
    2. 
          
  2. 
            
    
              Restart the client.
              
    The qURL tools show up next to its other tools.
    
            
    
          
    3. 
          
  3. 
            
    
              Ask for a link.
              
    “Make a private link to https://docs.example.com that lasts an hour.” For an app on your own computer, use the prompt or the CLI.
    
            
    
          
    4. 
        

        
Just want to share an app? The one-line prompt needs no key. · Full MCP reference 

      

    
    
      
  Send a file
        
        
qURL Desktop shares straight from your Mac. The file stays with you; the other person just needs a browser.

         Get qURL for Mac 
        
Apple Silicon (M1 or later) · macOS 12+ · Windows and Linux coming soon

        
    
          
  1. 
            
    
              Install and open it.
              
    Choose “Continue without an account” to start right away.
    
            
    
          
    2. 
          
  2. 
            
    
              Add what you want to share.
              
    A file, a folder, or an app running on your Mac.
    
            
    
          
    3. 
          
  3. 
            
    
              Make a link and pick how long it lasts.
              
    An hour, a day, whatever the moment needs.
    
            
    
          
    4. 
          
  4. 
            
    
              Send it.
              
    They click, qURL checks the link, and the file opens or downloads for their browser only.
    
            
    
          
    5. 
        

        
Keep your Mac awake while someone opens the link: the file never leaves your computer. Without an account you get up to 3 active shares.

        
More about qURL Desktop 

      

    
  

  

    

      
      
      

        
        
Verifying access

        
Opening this private resource for your browser.

      

      

        
Access verified

        
Your browser is opening the resource. For files, check your browser downloads.

      

      
Use of qURL is subject to the Terms. See the Privacy Policy.

      

      

        
CRID

        

        
        
        

        
        
        
            
        
Opening creates a private, temporary link for you.

      

      

        
Access link invalid

        
This link may have expired, been revoked, or already been used. Please request a new access link from the resource owner.

        
        

          How to get access
          
To try a link again after a connection problem, reopen it from the message you received. Refreshing this page won’t retry that link.

          
If the link has expired, been revoked, or already been used, ask the sender for a new one. For a private share, ask the publisher to confirm you have access.