👋 Maker of fine Dev/Ops tooling since 2013. @RunsOnRunsOn
Rennes, France
Joined February 2009
- Tweets2K
- Following488
- Followers409
- Likes1.9K
Pinned Tweet
New high: 5M+ runners across all @RunsOnRunsOn users. 8x to 16x cheaper than GitHub Actions on real builds.
Will quote-tweet until X stops talking about CI costs and perf and you all just try RunsOn
This quoted post is unavailable.
As for everyone in the CI / sandbox space, September and October were pretty crazy. You should try runs-on.com
RunsOn benchmarks proving useful again runs-on.com/benchmarks/githu…
> modal raises 950M series D
> launching 26M containers every day
Crazy that you need a 950M series D to do this, while @RunsOnRunsOn now routinely launches 4M+ real VMs per day with 2 people. They don't even seem to own the compute?
✅ 96% of issues resolved before customer impact.
✅ 99% of incidents detected within five minutes.
Read the full story to see how the team at @modal use Datadog to operate AI infrastructure across 20+ cloud providers, launching 26M containers every day while maintaining unified visibility across the platform: bit.ly/4eLDmrh
Cyril Rohr retweeted
oh hey! we switched all our CI from GHA to RunsOn a few weeks ago. it Just Worked™ — thanks for an amazing product
RunsOn can use spare capacity at AWS to bring your GitHub Actions costs way down. Here is how it works:
Crazy numbers for blacksmith. Currently doing a quarter of their load with @RunsOnRunsOn, and zero VC money. This is a blue ocean, for now.
@sequoia is leading our Series C at a $1B valuation.
Since January, we’ve gone from running 5M CI jobs a week to over 90M. Agents are writing an order of magnitude more code, and all of it still needs to be built and tested before it ships.
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
Cyril Rohr retweeted
As agents started opening and reviewing more of our PRs, we moved our CI to @RunsOnRunsOn.
We also built a RunsOn integration to watch it in Pydantic Logfire. @RunsOnRunsOn users get dashboards for queue times, Spot interruptions, cost per job, and runner sizing.
pydantic.io/oKz6x
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. 🧵
Cyril Rohr retweeted
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. 🧵
Cyril Rohr retweeted
Here's another reason to self-host your GitHub runners on AWS: Caching.
actions/cache is not terrible but RunsOn uses an S3 bucket to store/retrieve your cached objects so that it never leaves your account (or network).
Which means its faster, upto 2x.
Moreover, you're free of the 10GB limit GitHub has and you don't pay anything for egress since S3 VPC Endpoints are free.
So you basically get faster, unlimited cache, for pennies.
And you only need to change 1 line.
This is why it's called Magic Cache.
Get started here: runs-on.com/docs/performance…