Launched February 20, 2024
RunsOn

RunsOn

Shockingly cheaper CI

SubscriptionWorkflow automationDevOpsCI26,774 impressions#4 of its week

RunsOn accelerates your GitHub Action workflows by running them on high-performance AWS machines, at a fraction of your current costs. * 10x cheaper, 30% faster * no concurrency limit * any machine type, even GPUs * x64 and ARM64 * fully compatible with GitHub runners * runs in your own AWS account * autoscales with load * supports custom images

RunsOn runs GitHub Actions jobs on on-demand AWS EC2 instances, cutting CI cost and latency.

for
Engineering teams that self-host CI on AWS and use GitHub Actions.
pricing
paid · free trial
license
MIT
runs-on/runs-on 1.3k 51updated a month ago
works withGitHub ActionsCloudFormationTerraform

Key features

6 features of RunsOn
  • Dynamic instance selection — Specify CPU, RAM, architecture or GPU in a label and RunsOn launches the matching EC2 spot or on-demand instance.
  • Fast job startup — Typical 30 s from queued to running; warm pools can reduce latency to under 6 s.
  • Unlimited machine types — Any EC2 instance type, including x64, ARM64 and GPU, can be used per job.
  • S3-backed caching — Add extras=s3-cache to use an unlimited S3 bucket in your VPC for cache storage.
  • Nested virtualization — KVM for Linux and Hyper-V for Windows enable Android emulators, VM-based e2e tests and Windows containers.
  • Per-job isolation — Each job runs on a fresh VM that is terminated when the job finishes, keeping data private.

Use cases

  • Run large-scale test suites on high-CPU spot instances to reduce cost
  • Execute GPU-intensive builds or ML training within CI pipelines
  • Use ARM64 instances for cross-architecture testing without extra hardware
  • Run Docker-in-Docker or nested VM workloads that need full VM access

RunsOn pricing

  • Starter€300/ year/year< 50k runners/month · Flat annual fee · Email support · All public binaries & AMIs
  • Enterprise€3,600/ year/year> 500k runners/month · Priority support · Private Slack Connect · Source-code access
  • Free (non-commercial)freeRunsOn Flex & Fleet · All public binaries & AMIs · Community support

RunsOn vs alternatives

RunsOnFluent CIBuildShipDaytonaDevzero
Best forCheap, scalable CI on AWSTypeScript-defined CI pipelinesVisual backend creationOn-demand dev environmentsRelease automation
PricingPaidFreeFreeFreeSubscription
DevHunt upvotes3215811833985
LaunchedFeb 2024Jan 2024Jan 2023May 2024Apr 2024
  • RunsOn vs Fluent CI: Fluent CI lets you write pipelines in TypeScript but runs on its own hosted infrastructure, not on your AWS account.
  • RunsOn vs BuildShip: BuildShip provides a visual backend builder and AI assistance, not a low-cost EC2-based CI runner.
  • RunsOn vs Daytona: Daytona creates dev environments on any infra, focusing on development rather than CI job execution.
  • RunsOn vs Devzero: Devzero automates releases but does not replace GitHub Actions runners with spot EC2 instances.

RunsOn FAQ

Will my existing GitHub Actions workflows break?+

No. The runner images are ported from GitHub’s own templates, so actions, cache steps and secrets work unchanged; you only change the label.

How fast does a job start?+

About 30 seconds from queued to running on a fresh instance; warm pools can bring it under 6 seconds.

Does Docker work inside the runners?+

Yes. Each job gets a full VM, so Docker, Docker-in-Docker and Compose behave as on any EC2 instance.

Is it safe to run inside my AWS account?+

Each job runs on a fresh EC2 instance that is destroyed after the job; code, secrets and caches never leave your account.

What does RunsOn charge beyond the license?+

Only your AWS bill for the spot/on-demand instances, S3 cache bucket and EBS volumes; RunsOn adds no compute markup.

What happens if spot capacity is unavailable?+

RunsOn falls back to on-demand with a 2–3 s launch penalty and retries interrupted jobs once on-demand by default.

Summarized by DevHunt from runs-on.com · Sep 27, 2026. Details may change; check the official site.