The team behind qURL™
Built on the OpenNHP standard we wrote.
qURL is LayerV’s product. OpenNHP is the network-hiding standard underneath it — published by the Cloud Security Alliance, progressing through the IETF, and co-authored by LayerV’s founding team. This page is the receipts.
Cloud Security Alliance
Published as a CSA Zero Trust standard.
The Cloud Security Alliance — the body that governs cloud security standards for 500+ enterprise members including AWS, Google, Microsoft, and Alibaba — has published the NHP specification as “Stealth Mode SDP for Zero Trust Network Infrastructure.”
What the specification covers
- NHP architecture: NHP-Agent, NHP-Server, NHP-AC components
- Cryptographic framework using the Noise Protocol
- Integration guidance for SDP, DNS, and FIDO
- Logging and compliance auditing requirements
- Default-deny posture aligned with Zero Trust
“Transitioning core networking technologies to a default-deny stance — one that aligns with emerging Zero Trust concepts.”
IETF Internet-Draft
Progressing through the body that runs the internet.
The Internet Engineering Task Force is the body that defined TCP/IP, HTTP, TLS, and DNS — virtually every protocol the Internet runs on. NHP is currently in the IETF standards track as draft-opennhp-ztcpp-nhp.
What the draft defines
- Protocol architecture: NHP-Agent, NHP-Server, NHP-AC, ASP
- Cryptographic framework: Noise Protocol, Curve25519, ChaCha20-Poly1305, HKDF
- Message formats: NHP-KNK, NHP-ACK, NHP-AOP, NHP-ACC
- Integration patterns: SDP, DNS, FIDO, Zero Trust policy engine
The protocol, in three beats
What we standardized.
The spec defines a single ritual: default deny, then cryptographic knock, then micro-authorized access. Scroll through one execution of it.
From spec to product
The standard is a document. LayerV is the system.
Production-hardened
The spec is a document. LayerV is the running system: a hosted access service, a connector you run beside your apps, and a public API with documented limits.
Managed infrastructure
Hosted knock and tunnel services, generated connector deployments for Docker, ECS, and Kubernetes, and key custody from TPM to attested cloud KMS. The platform that turns the standard into one API call.
Direct from the authors
We don't just implement the spec — we wrote it. Support and roadmap come from the people who define what the protocol does next.
The team that wrote the standard ships qURL.
Pilot it on one application, or try qURL free — no credit card.