RoadRunner runs PHP workers behind a Go application server. It provides HTTP serving, queues, key-value storage, logging, and other plugins through a worker architecture. The management value is also the measurement problem: a public HTTP response can identify the application while the RPC and plugin control planes remain invisible.

A ZoomEye count-only collection on November 22, 2026 found 25 matches for app="RoadRunner", 897 for title="RoadRunner", and 9,310 for http.body="RoadRunner". The body result is broad and can include documentation, project pages, or unrelated uses of the name. The application result is small but more specific.

The RPC boundary

RoadRunner documents an RPC interface for communication between PHP applications and the server, using the Goridge bridge. Plugins can expose RPC methods for logs, locks, queues, and other services. Some deployments enable an external RPC listener for development or operational control.

That changes the threat model. The public web route may be correctly authenticated while an RPC socket on another interface offers operational methods. The socket may be bound to a container network, a local address, or a management interface. Externally observed RoadRunner branding does not show which of those designs is in use.

Inspect the deployment

Start with configuration, not a scan. Record which RoadRunner plugins are enabled, whether RPC is exposed over TCP, which address and port it listens on, and what network policy reaches that listener. Separate the worker RPC path from any public HTTP listener.

Review plugin methods and their authorization. A queue or KV method can reveal job payloads, keys, or application state even when the public site has no matching endpoint. Logs passed through RPC can contain credentials or request data. The server should not treat a connection from a worker container as a substitute for a control-plane identity.

For external testing, look for a web fingerprint only as an inventory lead. Confirm whether the host runs a management listener, then test it from the network position an attacker would actually use. Do not assume that a title match means an RPC service is reachable.

Evidence and limitation

The selected query was app="RoadRunner" with sub_type=all, page 1, pagesize 1. It returned 25 index matches. The body query returned 9,310, but that number is too broad to treat as a deployment count. The title query returned 897 and may include pages that mention the project without running it.

For an internal inventory, record the RoadRunner binary or image version, plugin set, RPC configuration, and network listeners. For an external review, distinguish a product mention from a running service. The gap between those states is where operational risk often sits.

References