Skip to content

Urth tests service behavior from the networks that matter

Urth is a probing service for synthetic monitoring and continuous verification. A synthetic probe sends a controlled request or runs a script to test service behavior. It can check whether a service responds, how long a request takes, and whether a sequence of actions produces the expected result.

Urth coordinates these checks through an API control server. You run the Workers, which are the processes that execute probes. Place them in private networks or external locations that represent the service paths you need to test. Workers connect outward to the control plane to collect jobs and report results. You do not need to expose a private service to the control server.

Measure outcomes, then use the evidence

An available host does not prove that a customer can use a service. A probe can test DNS resolution, connection establishment, an HTTP response, or a browser workflow. Results help you find failures and compare behavior across network locations. Use that evidence to investigate, verify changes, and decide what to repair. Urth supplies measurement; your engineering process decides the action.

For example, a service can respond quickly from its own VPC while customers in another region experience slow requests. Probes from both locations make the difference visible. They do not reproduce every customer's device, access network, or workload.

You operate the probers

You are responsible for deploying, authorizing, and managing your probers. In Urth, a Runner is a logical job channel. A Worker is a process that joins that channel and executes jobs. Register a Runner in your account and authorize it for each project it serves. Then start Workers with its enrollment credential. Creating a Runner or granting project access does not start a Worker.

You provide compute, network routes, DNS, certificates, target credentials, and any required script or browser runtimes. You also manage restarts, upgrades, capacity, and credential revocation. Project authorization permits work in Urth; it does not grant access to the target infrastructure.

Choose your next step

Early preview

Urth is under active development and is not production-ready. The public preview can reset data without notice. No availability commitment is made. Features and APIs can change. Do not upload production data, credentials, or secrets to the public preview. Scenario schedules are stored and validated, but recurring execution is not implemented. Trigger runs manually.

Urth is a free tool with publicly available source. Check the license for the version you use. See Licensing for project terms.