Design Partner Program
PLATFORM · PRIVATE RUNNER

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.

HAYROK CLOUD · CONTROL PLANE
Reasoning and planningSelects scenarios for each scope
GovernancePolicy, scope and approval gates
Validation and Risk EngineJudges outcomes, scores risk
Evidence FabricRedacted records and audit trail
YOUR NETWORKrunner-prod-01 · connected
Private RunnerExecutes approved actions · enforces scope and limits · redacts before upload
10.20.0.0/16Internal services
api.internalPrivate APIs
corp.localDirectory
vpc-prodPrivate cloud
Raw evidence store (optional)stays local
WHEN TO USE IT

Reach What the Internet Can't

01

Internal applications and APIs

Validate services that are never exposed to the internet, as the identities that use them.

02

Segmented and regulated networks

Test inside zones such as cardholder or OT networks, from a runner placed in that zone.

03

Identity and lateral movement

Validate directory and internal attack paths from a realistic internal foothold.

04

Data residency requirements

Keep raw captures in your own region and storage, with only redacted results leaving.

HOW A RUN WORKS

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.

Local scope check STEP 3 / 7
Before any action, the runner checks targets, limits and time windows against its own copy of the approved scope.
CONTROL PLANE Hayrok cloud
RUNNER Inside your network
TARGETS Your systems
CROSSES BOUNDARY Nothing. Out-of-scope actions are refused locally.
SECURITY MODEL

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.

Outbound-only connection The runner initiates an encrypted connection out. No listening ports, no inbound firewall changes.
Local scope enforcement Approved scope and limits are checked on the runner too, so out-of-scope actions are refused locally.
Redaction before upload Sensitive fields are masked on the runner before anything leaves your network.
Local evidence option Keep raw captures in your own storage; the control plane holds only references and redacted results.
Scoped, revocable identity Each runner has its own credentials. Revoke one from the console and it stops immediately.
Signed images and updates Images are signed, and you decide whether updates apply automatically or after approval.
WHAT IT REACHES

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.

IDENTITY

Directory and identity

Validate privilege paths, weak delegation and credential exposure from an internal foothold.

Active DirectoryLDAPKerberos
APIS

Internal and private APIs

Test authorization and abuse cases on services that never face the internet.

RESTGraphQLgRPC
APPS

Internal web applications

Validate intranet apps, admin consoles and line-of-business tools as real users would reach them.

SSO appsAdmin panels
KUBERNETES

Clusters and workloads

Run in-cluster scenarios against RBAC, service accounts, network policies and secrets.

RBACPodsSecrets
NETWORK

Segments and lateral movement

Confirm which segments can reach which, and whether controls stop lateral movement.

SMBRDPSegmentation
OT

Operational technology

Passive and read-only scenarios only, under a dedicated safe-mode policy agreed with your OT team.

Read-onlySafe mode

Coverage per target type to be confirmed by Hayrok product before publishing

DEPLOYMENT

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.

NETWORK Outbound HTTPS to the Hayrok control plane; no inbound rules
PROXY Works through an authenticated outbound proxy
RESOURCES Sized to your scope; guidance provided at onboarding
UPDATES Signed images; you choose automatic or approved updates
# 1. Pull the runner image
docker pull <registry>/hayrok/private-runner:<version>

# 2. Start it with a one-time registration token
docker run -d --name hayrok-runner \
  -e HAYROK_RUNNER_TOKEN=<token-from-console> \
  -e HAYROK_RUNNER_NAME=runner-prod-01 \
  --restart unless-stopped \
  <registry>/hayrok/private-runner:<version>
Best for a single segment or a quick evaluation.
NETWORK AND EGRESS

One Outbound Rule. Nothing Inbound.

What your network team needs to allow. The runner never listens on a port.

DIRECTION
DESTINATION
PORT
PURPOSE
Outbound
<control-plane-host>
443/TCP
Encrypted control channel: pulls approved plans, sends results and heartbeats.
Outbound
<registry-host>
443/TCP
Pulls signed runner images and updates. Can be mirrored to your own registry.
Internal
In-scope targets
Per scenario
Test traffic to approved targets only, inside your network.
Internal
Your DNS and NTP
53 · 123
Name resolution and accurate timestamps for evidence.
Inbound
None
—
No listening ports. No inbound firewall rules.
Proxies Supports an authenticated outbound HTTP(S) proxy for all control-plane and registry traffic.
TLS inspection Certificate pinning on the control channel means it should be excluded from TLS inspection.
Air-gapped options Mirror images to an internal registry. Fully offline operation is not confirmed.

Hostnames and ports are placeholders · final egress list to be confirmed by Hayrok engineering

OPERATIONS

You Stay in Control of the Runner

Health, updates, stopping and logs, all from the console or on the host itself.

HEALTH Heartbeat and statusEach runner reports health, version and current run to the console. Missed heartbeats raise an alert.
UPDATES Signed, on your termsChoose automatic updates or approve each version. Images are signed and verified before they start.
KILL SWITCH Pause, revoke or stop locallyPause all activity from the console, revoke a runner's credentials, or stop the service on the host.
LOGS Local logs you can forwardRunner and audit logs are written locally in structured form for forwarding to your SIEM.
runner-prod-01 Online
VERSION <version> · signed
HEARTBEAT 2 s ago
CURRENT RUN run-4821 · step 4 of 7
SCOPES corp-internal, api-internal
09:41:12 heartbeat ok 09:41:10 run-4821 executing in scope corp-internal
MULTI-RUNNER, MULTI-SITE

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.

runner-hq-01 Online
Headquarters · corporate network Directory, internal web apps and file services. → runs corp-internal
runner-k8s-prod Online
Production cluster · eu-west In-cluster services, service accounts and private APIs. api-internal, k8s-prod
runner-pci-01 Online
Cardholder data zone Placed inside the segment so tests never cross the boundary. pci-segment
runner-plant-02 Online
Plant network · site 2 Passive and read-only scenarios under OT safe-mode policy. ot-site-2
Scope-to-runner assignment Each scope names the runner that can reach it. Plans never route through another segment.
Per-runner identity Every runner has its own credentials, so one can be revoked without affecting the rest.
Region-local evidence Point each runner at a local evidence store in its own region to meet residency rules.

Illustrative topology · runner names and sites are examples

HOSTED OR PRIVATE

Use Both, Scope by Scope

ASPECT
Hosted runners
Private Runner
Reaches
Internet-facing assets and cloud APIs
Internal networks, private APIs and segmented zones
Network changes
Allow-list Hayrok egress addresses
Outbound HTTPS only; no inbound rules
Raw evidence
Stored in Evidence Fabric, redacted
Optionally kept in your own storage
Operations
Fully managed by Hayrok
You host it; Hayrok ships signed updates
Governance
Same gates, approvals and limits
Same, plus local scope enforcement
Best for
External exposure and SaaS
Internal, regulated and residency-bound scopes

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.

Review the runner with your network team.

Get the architecture overview and a walkthrough with a Hayrok engineer before you install anything.

Request the architecture review →