The MacOS runners are powered by M2 Pros with 6vcpu and 14GB memory. On paper, this is comparable to the M1 powered macos-latest-xlarge runners by Github but are 25% faster and 50% cheaper, with the same tools pre-installed.

This is useful for 4 reasons: because Github runners are super slow and pricey and even more so on mac, managing mac infra is a hassle, concurrent CI runs on macs can get very expensive, and pre-installed tooling speeds up workflows.

We have teams running iOS builds on WarpBuild runners and are seeing even 70% reduction in build time, leading to 85% reduction in cost per job [1]. When compared to the intel-based runners, you’re likely to see a 3-4x speed up in job runtime.

As with all our runners, the same set of packages that you’d get on Github hosted runners are pre-configured on our macos runners so everything works out of the box with no modifications needed. The docs for our runners are here - https://docs.warpbuild.com/runners

[1] https://x.com/nickmolnar/status/1749883691306996116

Thank you HN: We launched WarpBuild on HN in 2023-Dec in the first week of having a product after pivoting to WarpBuild and got our first set of users from here. The amazingly positive response gave me confidence to double down on WarpBuild and we’ve been growing since. Some stats that I am grateful to this community for: (a) ~130 users signed up from the HN launch. (b) We’ve been growing 2-3x MoM since (c) Did ~$800 in revenue in Dec, mostly attributable to this launch.

We are on a mission to build the fastest CI cloud. I’d love your feedback on the product and thoughts on your biggest challenges with CI workflows that you’d like to see addressed.