Built by us. Trusted by them.
We are the engineers behind hoop. Identity tools decide who connects; we build what governs everything after: every query inspected, every command evaluated, every response masked, at the protocol layer. The engineering and security teams below trust it with that job.
The gap between the door and the room.
Every security stack we met solved the same problem: who gets in. Authentication, authorization, identity federation. Once the session opened, the controls stopped.
Engineers queried production databases and saw raw PII. AI agents ran kubectl commands at machine speed with no review. The data crossed the wire unprotected. We built hoop to close that gap.
- MIT licenseOpen source from day one
- CNCF memberCloud Native Computing Foundation
- SOC 2 Type IIAudited and certified
How we think about security.
Protocol layer, not application layer.
Security that depends on application changes gets skipped. The gateway sits at the wire protocol level. No SDKs to install, no code to change, no plugins to maintain. It works with the tools your team already uses.
We ship in the open.
The gateway that reads, judges and masks your data is open source under the MIT license, at hoophq/hoop.
It parses your wire protocols, inspects your queries and masks your data. Code that touches your most sensitive data should be code you can read, audit and contribute to. Read the source on GitHub
We run hoop on hoop. Every session our own team runs goes through the same gateway, the same guardrails, the same audit trail. The product we sell is the product we depend on. See pricing
See it on your stack.
A 30-minute session with the engineering team. Bring your architecture diagram and your hard questions. No slides. No sales pitch.