Show HN: 10x cheaper GitHub Actions on your AWS account (warpbuild.com)
WarpBuild provides drop-in replacements for Github hosted runners that are faster and cheaper.
WarpBuild got its first customers from our launch on HN last year and I'm excited to show our newest offering: WarpBuild managed Github actions runners on your AWS account that are up to 90% cheaper than Github-hosted runners.
In the last couple of months, we released a ton of new capabilities to speed up your workflows and save on costs like: (1) BYOC: run Github actions in your AWS account, in ~5 mins. (2) Managed unlimited Github caches. (3) Static IPs for allowlisting. (4) Flexible runner and disk configurations. (5) Spot instances, arm64 and x86-64 runners.
This has been a top ask from our users, and this is even cheaper than self-hosting on k8s using `actions-runner-controller`, while significantly improving job queuing times. We are rather unique in the breadth and depth of the product we offer.
This is another capability that we think moves the ecosystem forward, including `action-debugger` via ssh, fast MacOS (M2 Pro) runners, CI analytics dashboards and more.
We are making CI faster and cheaper for everyone. What are your biggest pain points with CI, and more broadly the release process? I'd love to learn more.
12 comments
[ 3.2 ms ] story [ 38.2 ms ] threadYet to explore the new capabilities!
Switching from github actions default runners is exactly a one line change.
Migrating from `actions-runner-controller` with k8s or self-managed VMs could be different based on specific customizations in place. However, we have import flows for the former to directly import the custom containers used in k8s, and an AMI import is coming soon.
There shouldn't be any stack specific behavior, except with caches. We have introduced fast custom caching actions including stack specific instructions in docs [1].
[1] https://docs.warpbuild.com/cache/quickstart#ruby
hth.