qurl.link

Why it exists

LayerV’s technology does something that sounds impossible the first time you hear it. You can protect a resource with one prompt, and share things running locally, completely securely, straight from your machine. No deploy, no public URL, nothing for anyone to find. The enterprise site explains that to security teams. We needed a place where a person could just experience it.

That is qurl.link. You have made a thing. You want one other person to try it. You paste a prompt into Claude Code, and your agent does the rest. They ask, you say yes, they’re in.

The squirrel

I designed the qURL squirrel and a brand around it to communicate that magic. Cream, purple and lime. A mascot that carries your link somewhere safe. Doodles and little landscapes instead of diagrams. It had to feel nothing like security software, because the person using it is not thinking about security. They are thinking about showing their friend the thing they built.

The constraint was that it still had to be true. The playfulness sits on top of an exact product: four access modes, stable addresses, a real policy deciding who gets in. The brand makes the technology approachable; it never pretends it is simpler than it is.

Accessible to anyone using Claude

The whole site is written for someone whose only technical tool is a coding agent. The prompt points the agent at a skill file and the agent does the install, the publish and the sharing. After that you manage access by talking: “Invite Lee too.” “Who has access? Remove Sam.” “Let people ask instead.”

That meant the copy had to work for two readers at once, the person and the model paraphrasing it. One name per thing. Real command words. No step that assumes you know what a port is.

How it connects to LayerV

qurl.link is the approachable front door to the same technology that runs the enterprise platform. The two sites cross-link where someone’s intent changes, from a quick share to a team deployment, and otherwise stay out of each other’s way.