--- title: "RunsOn vs StarSling: GitHub Actions runners" description: "Compare RunsOn and StarSling GitHub Actions runners: where jobs run, how runners are selected and billed, OS coverage, caching and optimization PRs." url: https://starsling.dev/compare/runs-on canonicalUrl: https://starsling.dev/compare/runs-on --- # StarSling vs RunsOn runners for GitHub Actions - [How StarSling works](https://starsling.dev/) [Comparisons](https://starsling.dev/compare) / StarSling vs RunsOn runners for GitHub Actions Last updated: 2026-09-27 StarSling is AI-native CI for GitHub Actions: drop-in Ubuntu runners plus agents that open optimization PRs for your workflows. RunsOn launches ephemeral EC2 runners inside your own AWS account, picked per job by a runs-on label, under a flat annual license with the compute on your AWS bill. StarSling runs managed Ubuntu runners for you, billed per minute, and adds AI agents that open workflow optimization PRs. Choose around where you want the compute to live and how you want to improve the workflow. For new accounts, AI-powered optimization PRs are only available to customers on paid plans and are not enabled by default. ## Table of contents - [Head to head](#head-to-head) - [How RunsOn runners work](#how-runson-runners-work) - [RunsOn licensing and billing](#runson-licensing-and-billing) - [Try StarSling on one Linux workflow](#try-starsling-on-one-linux-workflow) - [Workflow optimization you can inspect](#workflow-optimization-you-can-inspect) - [Best fit](#best-fit) - [Sources](#sources) - [References](#references) ## Head to head | Category | StarSling | RunsOn | |---|---|---| | Where runners run | On StarSling-managed runners. Install the StarSling GitHub App and change the `runs-on` label. | On ephemeral EC2 instances in your own AWS account, deployed from a CloudFormation template or Terraform module, with a GitHub App on your organization. | | Selecting a runner | Yes, swap `ubuntu-latest` for `starsling-ubuntu-24.04`. | A `runs-on` label that describes the instance, such as `runs-on=${{ github.run_id }}/runner=2cpu-linux-x64`, with constraints for CPU count, instance family and image. | | Billing model | Usage-based per-minute, from $0.004/min (2 vCPU) to $0.128/min (64 vCPU); queue time never billed; no seat fees. | A flat annual license per legal entity. EC2 compute, the S3 cache bucket and EBS volumes are billed by AWS to your own account. | | Operating systems | Ubuntu 24.04 Linux runners. | Linux x64 and arm64, Windows, and GPU instances. | | Caching | Keep GitHub Actions cache steps for the initial trial. AI optimization PRs can improve cache keys, dependency installs and build steps. | An `extras=s3-cache` label option backs `actions/cache` with an S3 bucket in your account, and Docker layer caching is built in. | | Capacity | 5th Gen AMD EPYC; 2-64 vCPU; unlimited concurrency. | Spot instances first with on-demand fallback, and warm pools for faster job starts. | ## How RunsOn runners work RunsOn deploys into your AWS account from a CloudFormation template or its Terraform module, which brings up the VPC, cache bucket, IAM roles and scheduler together. A GitHub App on your organization registers an ephemeral runner when a job asks for one, and the instance ends with the job. A job selects its machine through the `runs-on` label, which RunsOn treats as a query: constraints such as CPU count, instance family and image are resolved when the instance launches. RunsOn tries spot capacity first and falls back to on-demand. ## RunsOn licensing and billing RunsOn charges a flat annual license per legal entity, covering the GitHub organizations and AWS accounts you own or control. The EC2 instances, S3 cache bucket and EBS volumes are billed by AWS to your account, with compute billed per second. A free license covers nonprofit, open-source, educational and personal non-commercial projects. StarSling bills per runner minute, from $0.004/min (2 vCPU) to $0.128/min (64 vCPU), with queue time never billed and no seat fees. Use the [GitHub Actions pricing guide](/github-actions-pricing) to model your own workload, and [Self-hosted GitHub Actions runners](/self-hosted-github-runners) for the cost of running runners in your own cloud. ## Try StarSling on one Linux workflow Choose a representative Ubuntu job with a clear success condition. Keep the same commit, tests and build outputs across the comparison, and record queue time separately from execution time. - Install the StarSling GitHub App for the trial repository, then choose a label from [StarSling runner sizes](/products/runners). The default `starsling-ubuntu-24.04` selects 4 vCPU; match the size to the RunsOn instance you are comparing. - Prepare a small workflow PR. Where the job uses RunsOn label options such as `extras=s3-cache`, restore GitHub Actions caching in the same PR. Preserve required check names, permissions and test commands. - Run repeated cold-cache and warm-cache trials. Compare completed work, error rate, queue time, execution time and the full cost: the runner minutes on one side, the license plus the AWS bill on the other. - Keep the original workflow revision available. Roll back the trial by reverting the runner label and any cache edits together. ## Workflow optimization you can inspect Read the public [Mastra optimization PRs and results](/customers/mastra) and [Better Auth case study](/customers/better-auth) to see changes to real workflows, the measured windows and the work behind each result. Use those examples to identify a testable improvement in your own pipeline. For new accounts, AI-powered optimization PRs are only available to customers on paid plans and are not enabled by default. ## Best fit **Choose StarSling if:** Teams running Ubuntu GitHub Actions jobs who want managed runners and reviewable PRs that improve the workflow's caching, installs and test execution. For new accounts, AI-powered optimization PRs are only available to customers on paid plans and are not enabled by default. **Choose RunsOn if:** Teams that want runners inside their own AWS account, with compute on their AWS bill and a choice of EC2 instance per job, including Windows and GPU instances. ## FAQ ### What does runs-on do in a GitHub Actions workflow? `runs-on:` is the workflow key that selects the runner a job runs on, by label. RunsOn reads it as a query for an EC2 instance, and a StarSling job uses it to select `starsling-ubuntu-24.04`. ### Can I move from RunsOn to StarSling by changing runs-on? Start with an Ubuntu job and a StarSling label. If the workflow uses RunsOn label options such as `extras=s3-cache`, restore GitHub Actions caching in the same trial PR. Test the resulting workflow and keep the original revision for rollback. ### How should I compare RunsOn, Ubicloud and StarSling? Start with where the compute should run, the operating systems you need and how each one bills, then run the same job on matched resources. This page covers RunsOn; [StarSling vs Ubicloud runners for GitHub Actions](/compare/ubicloud) covers Ubicloud. Measure runtime and total cost across repeated cold-cache and warm-cache runs before choosing. ### Does installing StarSling enable AI optimization PRs? For new accounts, AI-powered optimization PRs are only available to customers on paid plans and are not enabled by default. ## Sources - [RunsOn: self-hosted GitHub Actions runners on AWS](https://runs-on.com/), read 2026-09-28 - [RunsOn pricing](https://runs-on.com/pricing/), read 2026-09-28 ## Other comparisons - [StarSling vs GitHub Actions](https://starsling.dev/compare/github-actions) - [StarSling vs Depot for GitHub Actions](https://starsling.dev/compare/depot) - [StarSling vs Blacksmith runners for GitHub Actions](https://starsling.dev/compare/blacksmith) - [StarSling vs WarpBuild](https://starsling.dev/compare/warpbuild) - [Buildkite vs GitHub Actions: where StarSling fits](https://starsling.dev/compare/buildkite) - [StarSling vs Namespace runners for GitHub Actions](https://starsling.dev/compare/namespace) - [StarSling vs Ubicloud runners for GitHub Actions](https://starsling.dev/compare/ubicloud) - [Compare GitHub Actions runners and CI platforms: StarSling vs GitHub-hosted, Depot, Blacksmith, WarpBuild, Buildkite, and Namespace](https://starsling.dev/compare) ## References - [StarSling Runners are now generally available](https://starsling.dev/blog/starsling-runners-are-now-generally-available) - [Launch YC: StarSling Runners - Self-Driving CI](https://www.ycombinator.com/launches/R7B-starsling-runners-self-driving-ci) - [StarSling docs](https://docs.starsling.dev) - [ci-speedup skill source (open source, MIT)](https://github.com/starslingdev/skills) - [ci-score skill source (open source, MIT)](https://github.com/starslingdev/skills/tree/main/skills/ci-score) - [ci-secure skill source (open source, MIT)](https://github.com/starslingdev/skills/tree/main/skills/ci-secure) - [What is AI-native CI?](https://starsling.dev/ai-native-ci) - [All StarSling comparisons](https://starsling.dev/compare) - [GitHub Actions alternatives](https://starsling.dev/github-actions-alternatives) - [GitHub Actions pricing](https://starsling.dev/github-actions-pricing) - [Self-hosted GitHub Actions runners](https://starsling.dev/self-hosted-github-runners) - [Benchmark on your own workflows](https://docs.starsling.dev/performance/benchmarks) - [Migration guide](https://docs.starsling.dev/configuration/migration-guide) - [Runner label reference](https://docs.starsling.dev/configuration/label-reference) - [Runner instance types](https://docs.starsling.dev/runners/instance-types) - [Install the /ci-speedup skill to fix slow GitHub Actions](https://starsling.dev/skills/ci-speedup) - [Install the /ci-score skill to improve your GitHub Actions setup](https://starsling.dev/skills/ci-score) - [Install the /ci-secure skill to close critical attack vectors in GitHub Actions](https://starsling.dev/skills/ci-secure)