Runners
Runners execute HTTP, ping, port, and custom monitor checks. Testable-hosted runners are managed by Testable; self-hosted runners run in your own infrastructure so monitors can reach private services.
Runner Types
Testable Hosted
Testable-hosted regions are public shared runner pools. Use them to monitor public services from multiple geographic locations without operating infrastructure.
Self Hosted
Self-hosted regions let you run checks inside a VPC, private network, data center, or customer environment. Use them for internal APIs, databases, private apps, and firewall-restricted services.
Runner List
The Runners page has tabs for Testable Hosted and Self Hosted runners plus filtering by name or region. Region rows show active, free, busy, and queued runner counts, public IPs, running checks, and map location when coordinates are available.
Runner Details
Expand a region to see individual runner hosts. Details include host, public IP, running checks, vCPU usage, memory usage, version, OS, last ping, uptime, and installed browsers.
Adding Self-Hosted Runners
The Self Hosted tab includes an add runner action that opens the runner setup modal. Follow the generated instructions for your environment and keep the runner online so it can poll for checks.
Using Runners in Monitors
Non-heartbeat monitors choose one or more runner regions in the Regions panel. Plans that include location selection can add and remove regions per monitor; otherwise the organization default region is used.
Operational Guidance
- Use multiple hosted regions for public availability and latency visibility.
- Use self-hosted runners for private endpoints instead of exposing services publicly.
- Keep runner versions current so browser and runtime support remains compatible with custom scenarios.
- Monitor runner capacity by watching active, free, busy, and queued counts.
- Install browser dependencies required by Playwright, Puppeteer, or Selenium scenarios.