⚡️ Blazing fast builds
- Native x64 & ARM64 runners
- At least 30% faster than GitHub-hosted
- Windows & GPU support
- Optimized boot time under 30s
- 200k+
- daily jobs
- Zero
- k8s headaches
- 90%
- cost savings
Self-hosted GitHub Actions runners made simple
Trusted by 300+ companies of all sectors and sizes.
Deploy directly into your AWS account.
Deploy directly into your AWS account.
Enterprise-grade runners without the complexity
💰 Maximum cost savings
- Up to 90% cheaper with AWS Spot instances
- Across multiple AZs
- Automatic fallback to on-demand
- Use your existing AWS credits
📈 Scales with your needs
- Hundreds of concurrent jobs at once
- 200k+ daily jobs across users
- Multi-AZ for high availability
- Only limited by your AWS quotas
✨ Supercharged caching
- VPC-local S3 cache backend
- Up to 5x faster transfers
- Unlimited storage for caching
🔒 Enterprise-ready
- VPC peering for private resources
- Static IPs for firewall rules
- Custom images & SSH access
☸️ Complete control
- 100% self-hosted in your AWS account
- No third-party dependencies
- Full audit capabilities
🛡️ Secure
- Real EC2 VMs for complete isolation
- Ephemeral, recycled after each job
- Regularly maintained and patched
- Security taken seriously
Faster build times, shocking cost savings
Easy to setup. 85% cheaper than GitHub Actions.
-
Maxime Laurenty, Head of Infrastructure at Spinergie
Our main repository saw an average decrease in CI runtime of 35%. Another repository could fully utilize 16 threads, which dropped its runtime by 75%.
-
Timo Schäfer, Software Engineer at Wikando
Simple pricing that makes sense
One flat license fee. Pay AWS directly for EC2. That’s it.
Free for non-commercial use • 300€/year for commercial use
✓ No per-minute charges
✓ No middleman markup
✓ Use your AWS credits
Some users report $30k+ monthly savings compared to GitHub-hosted runners.
Perfectly right-size your runners, with dynamic runner configuration
Forget rigid runner configurations. Specify RAM, CPU, GPU, DISK size, instance type, static IP support, and more at runtime:
runs-on: ubuntu-latest # ⤵️ replace withA compatible 2-CPU x64 runner:
runs-on: - runs-on=${{ github.run_id }} - runner=2cpu-linux-x64A 2-CPU ARM64 runner:
runs-on: - runs-on=${{ github.run_id }} - runner=2cpu-linux-arm64A 16-CPU x64 runner with a custom image:
runs-on: - runs-on=${{ github.run_id }} - family=c7a+c7i - cpu=16 - image=custom-image-x64c7gd instance (950GB of NVMe local storage), using Ubuntu24 for ARM64:
runs-on: - runs-on=${{ github.run_id }} - family=c7gd.4xlarge - image=ubuntu24-full-arm64A runner with a static egress IP, and SSH disabled:
runs-on: - runs-on=${{ github.run_id }} - runner=2cpu-linux-x64 - private=true - ssh=falseA runner targetting a specific environment:
runs-on: - runs-on=${{ github.run_id }} - runner=2cpu-linux-x64 - env=stagingDeploy in 10 minutes
Available in 10 AWS regions. Install now or watch the demo:
Join companies that get faster CI, at lower cost
I've been testing Kubernetes with ARC: more complex, each runner takes ~25 seconds to boot (on an existing node), far less attractive than the simplicity of RunsOn.
-
Tim Petricola, Software Engineer at Alan
Less than 10 min to test, install and use the product. You can finetune any workflow (CPU, RAM, machine type/size..) depending on your needs. The cache download speed is blazing fast thanks to amazon s3 endpoint. Pricing is transparent, pay only what you use with no overage.
-
Christopher Brookes, SRE at Choose
With RunsOn, we have increased CI/CD performance and reliability at a fraction of the cost of official or private hosted runners – it's a no-brainer for any DevOps team using GitHub actions at scale.
-
Oliver Günther, DevOps Team at OpenProject
We've just started using self hosted runners, and we were looking into possible solutions, including running them in Kubernetes, but then we found RunsOn: it's definitely what we needed! The fact that instances are compatible with the github hosted runners made the transition very smooth.
-
Michele Sorcinelli, Site Reliability Engineer at Citizens Advice UK
Low maintenance
RunsOn comes as a CloudFormation stack that you install in your own AWS account (10 regions supported). One-click install, one-click upgrades.
The server receives workflow events from GitHub Action, and launches ephemeral EC2 instances to fulfill the workflow job requirements (see architecture).
No need to manage a Kubernetes cluster with Action Runner Controller (ARC), or deploy complicated, half-maintained stacks.
Observable
RunsOn automatically publishes metrics for consumed minutes across repository, workflows, runner types, and result (success, failure).
Can be used to monitor the most expensive workflows, detect anomalies, and gain insights into failure rates of your workflows.
Scalable
If you are concerned about scalability, some users are running many thousands of jobs EVERY HOUR, without any issues:
10x cheaper, for 10 minutes of work
You can always switch back to official runners at any time.
Get started →
FAQ
Is RunsOn for me?
Most likely YES: If you spend more than $100/month on GitHub Actions, or find yourself constantly babysitting your own self-hosted runners, then you will definitely get a meaningful return on investment by switching to RunsOn. You also get access to custom ARM runners and GPUs, irrespective of your GitHub plan, even on the free tier.
Is this better than Action Runner Controller (ARC)?
If you are already heavily invested into Kubernetes, then ARC might not be too much work for you to setup and operate. However, RunsOn is much simpler to install, requires zero maintenance, and has a much better feature set than ARC: flexible runner types, 1-1 compatible images, integrated caching, real VMs, static IPs, fast boot times.
Is this better than the Philips Terraform AWS GitHub Runner?
Philips Terraform module is entirely Open-Source and free, contrary to RunsOn where you pay a small license fee for commercial use (non-commercial use is free). The terraform module is harder to setup and operate, and has a more limited feature set: no image compatibility with GitHub, slower boot times in ephemeral mode, fixed runner types, no integrated caching, hard to debug failure modes due to extensive use of lambdas.
Is this better than [other 3rd-party provider]?
There are great 3rd-party providers for self-hosted GitHub Actions runners (benchmarked here). However they are 3rd-parties, so you must be aware of the security implications of using them. RunsOn is fully self-hosted, does not depend on third-parties, has the best pricing, and features you won’t find over there at the same price point (unlimited concurrency, SSH access, static IPs, fast and consistent boot times, the widest choice of instance types, etc).
What about security?
RunsOn is fully self-hosted, and does not depend on third-parties. You can deploy it in your own AWS account, and have a look at our dedicated security page for more details.
Learn more
Features A recap of some of the best features and use cases for RunsOn.
Architecture Simple, performant, low-maintenance: learn about the architecture of RunsOn.
Pricing 10x cheaper, 30% faster CI/CD for GitHub Actions. ROI measured in days.
Calculator Estimate the cost of running your GitHub Actions workflows on self-hosted runners on AWS with RunsOn.
Testimonials Feedback from customers using RunsOn.
Security No third-party, fully ephemeral runners, in your own infrastructure. Take self-hosted runner security seriously.
Changelog Keep up with the latest features and improvements for RunsOn.
About The story behind yet another (but battle-tested!) self-hosted GitHub Actions runner.