runs-on.com valid

RunsOn

RunsOn runs ephemeral self-hosted GitHub Actions runners in your own AWS account: one CloudFormation or Terraform stack, no Kubernetes, any EC2 instance type per job. You pay AWS for compute and RunsOn a flat annual license.

Their llms.txt

The beginning of the file, from our validated copy saved 2026-10-26T08:26:39.779Z. Cached copy · Source on runs-on.com

# RunsOn

> RunsOn runs ephemeral self-hosted GitHub Actions runners in your own AWS account: one CloudFormation or Terraform stack, no Kubernetes, any EC2 instance type per job. You pay AWS for compute and RunsOn a flat annual license.

RunsOn has two modes. Flex lets each workflow choose its runner in the `runs-on:` label. Fleet lets a platform team publish Terraform-managed runner fleets that workflows target by name.

Moving a job to RunsOn Flex only requires changing its label:

```yaml
runs-on: runs-on=${{ github.run_id }}/runner=2cpu-linux-x64
```

Fleet jobs target a published fleet with `runs-on/fleet=<fleet>/env=<environment>`. [Job labels](https://runs-on.com/docs/runners/labels/) lists every Flex label option.

Every page below is also served as markdown: request it with `Accept: text/markdown`.

## Getting started

- [Documentation](https://runs-on.com/docs/): Everything RunsOn provides for teams running GitHub Actions on AWS, including compute, caching, observability, and security.
- [Quickstart](https://runs-on.com/quickstart/): From zero to a cached, 10x-cheaper GitHub Actions build running in your own AWS account.
- [Flex vs Fleet](https://runs-on.com/docs/flex-vs-fleet/): Choose the right RunsOn mode for your GitHub Actions runners on AWS.
- [Flex installation guide](https://runs-on.com/installation/flex/): RunsOn is the best way to run GitHub Actions in your own AWS infrastructure, and get 10x cheaper runners.
- [Fleet installation guide](https://runs-on.com/installation/fleet/): Deploy RunsOn Fleet on AWS with Terraform or OpenTofu.
- [GitHub Enterprise Server and GHE.com](https://runs-on.com/installation/github-enterprise/): Run RunsOn Flex or Fleet with GitHub Enterprise Server or GHE.com. The URL to set, actions on GHES, networking, and what differs from github.com.

## Runners

Runner types available across RunsOn Flex and Fleet - Linux, Windows, GPU - plus the capabilities you can layer on top.

- [Runner types and capabilities](https://runs-on.com/docs/runners/): Overview of the different runner types available in RunsOn - Linux, Windows, GPU - plus the capabilities you can layer on top.
- [Job labels](https://runs-on.com/docs/runners/labels/): Configure RunsOn runners with per-job runs-on labels and reusable runner definitions — CPU, GPU, RAM, instance type, volume size, sticky cache disks, and more.
- [Runner platforms - Linux, Windows, GPU](https://runs-on.com/docs/runners/platforms/): Self-host GitHub Actions runners on AWS across Linux (x64 + arm64), Windows, and GPU — for any GitHub plan. macOS is not yet supported.
- [Linux runners](https://runs-on.com/docs/runners/platforms/linux/): Native x64 and arm64 Linux runners on any EC2 instance, from Flex labels or Fleet runner definitions.
- [Windows runners](https://runs-on.com/docs/runners/platforms/windows/): Windows Server runners on EC2, from Flex labels or Fleet runner definitions.
- [GPU runners](https://runs-on.com/docs/runners/platforms/gpu/): NVIDIA and AMD GP
…

Machine-readable: GET /v1/resolve?q=runs-on.com · GET /v1/domain/runs-on.com · this page as Accept: application/json or text/markdown · MCP lookup_domain

Automatically discovered from public files. Inclusion does not imply endorsement or publisher participation.

Claim my listing on Agent Web Map for runs-on.com:
1. POST https://agentwebmap.com/v1/sites/runs-on.com/claims and keep claim_id and claim_secret private.
2. Publish the verification line "AgentWebMap verification: <token>" (token from step 1) in https://runs-on.com/llms.txt, or use the DNS, meta-tag or well-known method the response describes. This only verifies the listing; your website and domain remain yours.
3. POST https://agentwebmap.com/v1/sites/runs-on.com/verify with {"claim_id": "...", "claim_secret": "..."}.
4. Save the api_key from the answer; it manages the listing (PATCH https://agentwebmap.com/v1/sites/runs-on.com).
MCP equivalent: tools begin_ownership_claim, then verify_domain, at https://agentwebmap.com/mcp. Docs: https://agentwebmap.com/docs#verify

Corrections or removal requests: contact the directory.