qURL™ vs Self-Hosted OpenNHP
Share private apps and APIs without running your own access network.
qURL lets you share a private dashboard with a customer or give an AI agent access to one API without opening an inbound port. Send an expiring access link and revoke it when the work ends. OpenNHP is the core protocol. LayerV runs the access network for qURL, including the servers and access grants.
Start with one HTTP app. Connect it to qURL and send a link that reaches only that app. Your security team can review OpenNHP, the open-source protocol behind qURL, on GitHub. The project uses the Apache 2.0 license and implements the Cloud Security Alliance’s NHP specification. LayerV’s team co-authored the IETF Internet-Draft.
Share one app from the command line
qurl publish http://127.0.0.1:3000
qurl share <CRID>Architectural Difference
With qURL, deploy an outbound connector beside your app. LayerV operates the access network and handles app keys and access grants. Generate a connector deployment for Docker, Compose, ECS/Fargate or Kubernetes. Use the CLI, SDKs, REST API or MCP to add private access to your workflow. You can revoke one access link through the API while the other links continue to work.
If you build your own service on OpenNHP, your team operates these components:
- An always-on server: NHP-Server authenticates every knock and tells the access controller what to open. It listens on UDP 62206 by default and has to answer for every hidden app, so its availability, including multi-instance clusters, is yours to plan.
- An access controller on each protected host: NHP-AC runs as root on Linux, holds a deny-all firewall with iptables and ipset or eBPF/XDP, and opens a rule only after the server approves a knock.
- Keys for every component: generate a key pair for each server, controller and agent, exchange public keys through peer configuration files, keep clocks in sync across hosts, and rotate keys by updating every peer.
- Sign-in and grants: the server’s plugins decide who is admitted and for how long, and a custom sign-in flow is a plugin you build.
- Clients: people run the NHP-Agent daemon or an app built on the iOS, Android or browser SDK, and browsers reach the server through an NHP-Relay you also run.
Feature Comparison
| Feature | qURL | Self-Hosted OpenNHP |
|---|---|---|
| The protocol | OpenNHP is the core protocol. LayerV operates the access service. | OpenNHP, Apache-2.0, run on hosts you operate |
| What you deploy | One connector container beside each app | NHP-Server, an NHP-AC on each protected host, an NHP-Agent for each client, and NHP-Relay for browsers |
| The always-on access network | Run by LayerV | Your NHP-Server, reachable on UDP 62206 by default for every knock; clustering is yours to set up |
| Keys and identity | Handled by LayerV for each app; connector keys can be sealed to a TPM or held in a cloud KMS | A key pair per component, public keys exchanged in peer config files, rotated by updating every peer |
| Granting and revoking access | Expiring links. Revoke one through the API while the others keep working. | Server plugins decide who is admitted and for how long; custom sign-in is a plugin you build |
| Protected host | The connector uses outbound TCP 443, UDP 443 and an outbound TCP tunnel. The app needs no inbound port. | NHP-AC runs as root on Linux and manages deny-all rules with iptables and ipset, or eBPF/XDP |
| Where it runs | Generated deploys for Docker, Compose, ECS/Fargate and Kubernetes | Binaries you build with Go and make, or the project’s Docker Compose environment for testing |
| Tooling for people and agents | CLI, SDKs for Go, Python and TypeScript, REST API, MCP server and agent skill | The NHP-Agent daemon, iOS and Android SDKs, and a browser JavaScript SDK |
Which one to use
Choose qURL to
Share a dashboard with a customer, give a contractor access to one internal app, or let an AI agent call a private API. Set when access expires and revoke a link when the work ends.
Already running OpenNHP?
Try qURL with one HTTP app. Deploy the connector beside it and send an access link. LayerV operates the access network for that app.
Frequently Asked Questions
What can my security team review?
Your team can review the OpenNHP source code, the Cloud Security Alliance specification, and the IETF Internet-Draft. OpenNHP is the core protocol behind qURL, LayerV’s managed service for private access.
What does self-hosting OpenNHP involve?
Building the NHP-Server, NHP-AC and NHP-Agent, configuring each with its peers’ public keys, running the access controller as root on every protected host, and keeping the server reachable for every knock. Browser access adds an NHP-Relay. The project ships a Docker Compose environment for trying the full flow.
What do I deploy with qURL?
One connector container beside each app, on a Linux Docker host or in Compose, ECS/Fargate or Kubernetes. It needs outbound TCP 443, UDP 443 and an outbound TCP tunnel, and no inbound port. LayerV runs the access network, the keys and the grants.
What can I share privately with qURL?
HTTP apps and APIs, including MCP servers that speak HTTP. People open an access link in a browser; services and AI agents use the CLI, SDKs, REST API or MCP server.
Who maintains OpenNHP?
OpenNHP is developed in the open on GitHub as the reference implementation of the Cloud Security Alliance’s NHP specification. LayerV’s team co-authored the IETF draft, and LayerV’s CEO and CTO are among the project’s top contributors.