Validate inside your network. Open no inbound ports.
The Private Runner executes HIVE Agents inside your own environment, so internal systems, private APIs and segmented networks can be validated without exposing them. It connects out to Hayrok, never in, and keeps raw evidence on your side.
runner → cloud no inbound
Reach What the Internet Can't
Internal applications and APIs
Validate services that are never exposed to the internet, as the identities that use them.
Segmented and regulated networks
Test inside zones such as cardholder or OT networks, from a runner placed in that zone.
Identity and lateral movement
Validate directory and internal attack paths from a realistic internal foothold.
Data residency requirements
Keep raw captures in your own region and storage, with only redacted results leaving.
From Approved Plan to Evidence
Every run follows the same seven steps. Select a step to see where it happens and what crosses your boundary.
Built to Pass Your Own Review
The runner is offensive tooling inside your perimeter. These properties are designed for the questions your architecture and network teams will ask.
Internal Systems, Tested From the Inside
Place a runner where it can reach the target, and Hayrok validates it with the same governance as external scopes.
Directory and identity
Validate privilege paths, weak delegation and credential exposure from an internal foothold.
Internal and private APIs
Test authorization and abuse cases on services that never face the internet.
Internal web applications
Validate intranet apps, admin consoles and line-of-business tools as real users would reach them.
Clusters and workloads
Run in-cluster scenarios against RBAC, service accounts, network policies and secrets.
Segments and lateral movement
Confirm which segments can reach which, and whether controls stop lateral movement.
Operational technology
Passive and read-only scenarios only, under a dedicated safe-mode policy agreed with your OT team.
Coverage per target type to be confirmed by Hayrok product before publishing
Run It Where Your Workloads Run
Pick a target to see the install outline. Your registration token is issued in the console and scoped to one runner.
One Outbound Rule. Nothing Inbound.
What your network team needs to allow. The runner never listens on a port.
Hostnames and ports are placeholders · final egress list to be confirmed by Hayrok engineering
You Stay in Control of the Runner
Health, updates, stopping and logs, all from the console or on the host itself.
One Runner per Segment. One Console for All.
Each scope is assigned to the runner that can reach it. Select a scope to see where it runs.
Illustrative topology · runner names and sites are examples
Use Both, Scope by Scope
Private Runner is included in Queen (Enterprise). Compare plans →
Private Runner FAQ
No. The runner opens an outbound, encrypted connection to the control plane and pulls approved work. No inbound firewall rules are required.