What is RunsOn?
RunsOn provides a fully self-hosted GitHub Actions runner solution that deploys directly into your AWS account, giving you complete control over your CI/CD infrastructure while significantly reducing costs. The platform supports any AWS instance type from 1 to 896 vCPUs, including x64, ARM64, and GPU instances, allowing you to select the optimal hardware for your specific build requirements.
With transparent pricing that shows real EC2 spot and on-demand costs per runner, RunsOn eliminates markup surprises and per-minute fees. The solution includes S3-backed caching for up to 10x faster performance than GitHub's cache for large repositories, built-in observability with per-job cost tracking, CloudWatch metrics, and OpenTelemetry traces, and requires near-zero maintenance with automatic handling of GitHub API rate limits, retries, base images, secure networking, and updates.
Features
- Cost Reduction: Cuts GitHub Actions bills by up to 90% with transparent EC2 pricing and no markup
- Instance Flexibility: Supports any AWS instance type from 1 to 896 vCPUs including x64, ARM64, and GPU instances
- S3 Caching: Provides persistent cache in your own S3 bucket with up to 10x faster performance than GitHub's cache
- Observability: Includes per-job cost tracking, CloudWatch metrics, and OpenTelemetry traces out of the box
- Easy Migration: Requires only one line change in workflow files with full compatibility for existing actions and caching
Use Cases
- Reducing CI/CD infrastructure costs for engineering teams
- Running GPU-intensive workflows and machine learning pipelines
- Optimizing build times for large code repositories
- Maintaining security compliance with self-hosted runners
- Scaling CI/CD infrastructure with custom hardware requirements
FAQs
-
How does RunsOn compare to GitHub-hosted runners?
RunsOn provides the same ephemeral runner experience but at 90% lower cost, with faster performance, and runs entirely in your AWS account with access to any AWS instance type including GPUs and ARM processors. -
What is the migration process like?
Migration is very easy - in most cases, you just replace 'runs-on: ubuntu-latest' with 'runs-on: runs-on/runner=2cpu-linux-x64' and your existing workflows, caching, and actions work without changes. -
How does RunsOn differ from Actions Runner Controller (ARC)?
ARC requires Kubernetes expertise and ongoing maintenance, while RunsOn is a managed solution that deploys with one click, requires zero maintenance, and offers better features like native image compatibility, static IPs, and integrated S3 caching. -
What security measures does RunsOn provide?
RunsOn is fully self-hosted in your AWS account, so no third-party touches your code. Runners, logs, caches, and secrets never leave your VPC, giving you full control over security. -
What support options are available?
RunsOn comes with email support, comprehensive documentation, and most issues are addressed within hours. Sponsorship license holders get priority support and a dedicated Slack Connect channel.
Related Queries
Helpful for people in the following professions
RunsOn Uptime Monitor
Average Uptime
0%
Average Response Time
0 ms
