runs-on.com (@RunsOnRunsOn) header
runs-on.com (@RunsOnRunsOn) profile picture

10x cheaper GitHub Actions runners. 5M+ jobs per day. Self-hosted on AWS. Competing against 10+ YC-funded companies!

→
Joined January 2024
Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)Photo by runs-on.com (@RunsOnRunsOn)
More than 7M+ GitHub Actions jobs now run every day, with up to 90% savings vs GitHub. What are you waiting for?
1
4
966
runs-on.com retweeted
Everyone trying to get CI cache speeds up, and github over here saying "nope" 🤣
1
2
3
324
runs-on.com retweeted
Caching depth and breadth is what differentiates fast runners from fast CI. We’ve been busy at @RunsOnRunsOn
1
129
runs-on.com retweeted
Running 6M+ GitHub Actions jobs per day now with runs-on.com
1
1
1
123
runs-on.com retweeted
As for everyone in the CI / sandbox space, September and October were pretty crazy. You should try runs-on.com
1
8
379
runs-on.com retweeted
New high: 5M+ runners across all @RunsOnRunsOn users. 8x to 16x cheaper than GitHub Actions on real builds.
1
2
11
1,103
Word of mouth is one of the highest driver of runs-on.com growth
1
1
116
runs-on.com retweeted
Replying to @crohr @RunsOnRunsOn
oh hey! we switched all our CI from GHA to RunsOn a few weeks ago. it Just Worked™ — thanks for an amazing product
1
2
2
127
EC2 spot instances are a very good fit for CI workloads, most of the time. runs-on.com/docs/costs/spot-…
RunsOn uses EC2 Spot capacity by default. This makes it the cheapest way to run CI workloads on cloud compute by far. But handling spot interruptions while keeping the CI green gets tricky when running thousands and thousands of jobs a day. Here's how RunsOn does it:
1
343
runs-on.com retweeted
Heavy GitHub Actions bill? Have a look at our state of actions report to identify what's costing you most. I'm deep into it every day and I still discovered a few stragglers
CI has always been invisible and is supposed to "just work". But not anymore. Since agents are shipping a lot of code, invisibility becomes a real problem until that humongous bill hits. This is why I built State of Actions. It takes all the insights and usage metrics GitHub provides (and doesn't) and brings it together in one place so that the state of your CI is fully visible BEFORE that bill hits. Our main goal with this tool has always been for a user to understand how their CI on Actions is doing without having to scramble around GitHub for answers. It's been a really fun ride iterating over and over again as the models get better to make this the best experience possible for all kinds of users - from solo devs to enterprise. So here it is, a fresher UI that helps you answer your burning questions on CI with clarity and ease: - Where do my minutes go? - How much does it actually cost? - How much am I paying for failed jobs? - What runs queue slower than others? And much more. There are core sections that give insights on Cost, Usage, Performance and Reliability and a table view to filter out the exact workflow or job you're looking for, with a further panel to drill down into them. There's a global search bar ofc if you want to quickly jump to a specific repo, workflow, job or label. Will keep refining this as we get more and more feedback, so give it a go and tell me whether this helps you grasp the state of your Actions in the way you hope or not! And ofc its free: soa.runs-on.com
1
1
3
276
The @pydantic team switched Logfire's CI to RunsOn on Sept 1. August, on GitHub, Depot and Ubicloud runners: $18.2k. September, on RunsOn: $5.7k, license and every AWS cost included. And they ran 31% more runner minutes in September. 🧵
1
2
1
6
1,861
Same GitHub Actions, same workflows. Jobs now run on fresh EC2 instances in their own AWS account: mostly Graviton, Spot wherever a retry is cheap, on-demand for the merge queue and releases. Bill Easton's write-up: pydantic.dev/articles/ai-oh-…
1
1
79
Along the way, they built a RunsOn integration in Logfire: dashboards for queue times, Spot interruptions, cost per job, and runner CPU and memory. A few lines of Terraform: runs-on.com/blog/runs-on-pyd…
1
3
417
Disks? Where we're going, we don't need disks. extras=tmpfs keeps a RunsOn runner's workspace and Docker data in RAM. PostHog's image build on 4 vCPU: 9m05s → 5m02s. GitHub's own runner takes 12m44s and costs 13 times as much. runs-on.com/blog/tmpfs-githu…
2
92
Need a predictable egress IP for CI allow lists? RunsOn supports static egress through private subnets on Linux and Windows, with Flex and Fleet. runs-on.com/docs/runners/cap…
2
67
runs-on.com retweeted
Won't make the benchmarks any faster though - runs-on.com/benchmarks/
this is an incredible use of VC money since everyone at the Jay street metro tech station in Brooklyn knows what a CI is (they raised $45 million in august)
1
4
111
runs-on.com retweeted
You should really try full tmpfs (YOLO) mode on your CI runners. Some workflows fly with it! Only possible if your provider actually lets you use high-memory instance types though... which means only RunsOn or your own bare-metal!
1
1
2
173