Avrea vs WarpBuild

Features at a glance

Avrea runners, cache and observability. WarpBuild runners, cache, observability and BYOC.

Hosted runner pricing

The x64 compute rate is equal across these three sizes. Cache charges and job duration can still change the total.

Avrea is pay as you go with no monthly base fee. It includes 3,000 monthly minutes in 2-vCPU equivalents, with larger runners using that allowance proportionally. Avrea pricing.

If you use WarpBuild's hosted cache, storage costs $0.20 per GB-month, plus $0.0001 per write, restore or list operation. Holding 25 GB for a month costs $5 before operations; Avrea includes 25 GB per repository. WarpBuild's snapshot runners add $0.04 per restore job and $0.025 per hour of stored snapshot. WarpBuild pricing, cache billing.

For 10,000 runner minutes on a 2-vCPU / 8-GB x64 machine, compute is $40 with either provider before free usage. Avrea includes 25 GB of cache per repository; WarpBuild's hosted cache and any snapshot or remote-builder usage add to compute. The GitHub Actions pricing guide covers how runtime, included usage and cache costs affect the bill.

Linux ARM hardware

Avrea's Linux ARM runners use Apple M5 Max hardware. A 2-vCPU / 8-GB ARM runner is $0.012/min on Avrea and $0.003/min on WarpBuild's standard Linux ARM tier. At 4 vCPU, RunsOn reports single-thread scores of 4,860 for Avrea and 1,942 for WarpBuild's standard ARM runner. Avrea pricing, WarpBuild pricing, RunsOn CPU results.

WarpBuild also offers Linux ARM on Apple Silicon. Here are two published Apple-based configurations, with their different CPU and memory allocations shown:

Avrea has the lower minute rate and higher single-thread score in this pair. The machines differ in size and chip generation; the CPU scores do not measure complete workflow duration. Runner prices, WarpBuild's Apple Silicon tier, CPU results.

macOS hardware

For macOS, Avrea lists an 8-vCPU / 24-GB M5 Max runner at $0.08/min. WarpBuild lists a 6-vCPU / 14-GB M4 Pro runner at the same rate. Those configurations have different hardware and memory, so an equal minute price does not make them equivalent machines.

CPU benchmarks

RunsOn's 14 October 2026 results show Avrea and WarpBuild within roughly 1% on both CPU tests at the matched 4-vCPU / 16-GB x64 size.

These synthetic CPU tests measure processor performance; workflow duration also depends on disk, caches and the work each step performs. RunsOn CPU results.

Actions cache benchmarks

Avrea restores the 4-GB test cache in 14 seconds in RunsOn's 4-vCPU / 16-GB x64 results. The WarpBuild runner using GitHub's cache restores it in 33 seconds; WarpBuild's own cache action is a separate result.

The test saves a 4-GB file, deletes it and restores it. It does not measure Docker builders, snapshots or complete dependency installations. RunsOn sells runners too; these vendor-published results use small samples and can change with workload and configuration. Cache results and backend details. Data: RunsOn, CC BY 4.0 and methodology; selected configurations and shortened labels.

Caching dependencies and build outputs

Avrea keeps supported Actions cache calls on the same workflow syntax. Its package proxies reuse downloaded dependencies, while integrations for tools such as Turborepo, Gradle, Bazel and sccache reuse build outputs. A warm build can then skip work whose inputs have not changed. Avrea cache, build-tool integrations.

WarpBuild's cache integration replaces actions/cache with WarpBuilds/cache. Its setup actions connect language dependency caches to the same service. This is separate from leaving the original action pointed at GitHub's storage, which is why the benchmark shows two WarpBuild rows. WarpBuild caching.

Avrea's regular cache allowance is 25 GB per repository across Actions, package and build-cache entries, with additional storage available to purchase. Entries unused for seven days are eligible for eviction. Storage and eviction.

Docker builds and persistent state

Avrea's persistent disks retain Docker images, layers and builder state between jobs once enabled for the repository. It also provides a BuildKit cache endpoint, so subsequent jobs can reuse earlier build outputs. Avrea Docker caching.

WarpBuild offers remote Docker builders that run the build on a separate machine with local layer storage. Builder profiles are shared across jobs, and builder time is billed separately from the GitHub runner coordinating the workflow. WarpBuild Docker builders, builder pricing.

Persistent storage is available on both platforms. The difference here is how the Docker build runs and how that compute is billed, rather than whether either provider can retain cache data.

Debugging and AI-assisted fixes

Avrea's resource metrics and searchable logs help connect a slow step or failed process to what happened inside the job. SSH access lets you inspect the running environment directly. Avrea observability, debugging.

Avrea Quality uses logs, code changes and test history to work on a fix. It runs the proposed change through the full test suite and opens a pull request when validation passes. That brings the investigation and a tested change into the same CI workflow.

WarpBuild also provides CPU, memory, disk and network telemetry, logs and runner-sizing recommendations. Its docs note that observability collects jobs longer than roughly one minute and supports exporting telemetry to your own backend. WarpBuild observability.

Running inside your own cloud account

WarpBuild BYOC manages runners in your AWS, GCP or Azure account. You choose the cloud configuration, including regions, networking and machine images. Its listed Linux platform charge is $0.002 per runner minute, with your cloud infrastructure billed in addition. BYOC setup, pricing.

Avrea runs the infrastructure for you. For services protected by IP allowlists, it offers static egress IPs at $100 per IP per month, listed with Enterprise features. A static IP solves fixed outbound addressing; it does not place the runner inside your own VPC. Avrea static IPs, pricing.

Choosing between Avrea and WarpBuild

Avrea is a strong fit when slow feedback and failed builds are the main problems: matched x64 rates, automatic Actions caching, build-tool caches and CI diagnostics, with Quality to propose validated fixes. The cache results above give a concrete reason to try it on workflows that spend time restoring dependencies.

For a requirement to run inside your own AWS, GCP or Azure account, WarpBuild offers BYOC at $0.002 per Linux runner minute plus your cloud bill. Its remote Docker builders are billed separately from the runner coordinating the job.

Common questions

Do Avrea and WarpBuild charge the same per minute?

For hosted Linux x64 runners, yes. Both list $0.004 per minute at 2 vCPU / 8 GB, $0.008 at 4 vCPU and $0.016 at 8 vCPU. The bill then depends on job duration, included usage and cache charges. Avrea includes 3,000 monthly minutes and 25 GB of cache per repository; WarpBuild bills hosted cache storage and operations separately.

Do I need to change my workflow to use Avrea's cache?

No. Supported actions/cache and setup-action calls are routed to Avrea's cache automatically when the job runs on an Avrea runner. WarpBuild's own cache requires replacing actions/cache with WarpBuilds/cache or using its setup actions; otherwise the job keeps using GitHub's cache service.

Which restores Actions caches faster?

In RunsOn's 14 October 2026 test on 4-vCPU / 16-GB x64 runners, Avrea restored a 4 GB cache in 14 seconds. WarpBuild took 33 seconds with GitHub's cache and 70 seconds with its own cache action. These are transfer tests from small samples, not complete build times.

Does Avrea offer BYOC like WarpBuild?

No. Avrea runs the infrastructure for you. For services behind IP allowlists it offers static egress IPs at $100 per IP per month on the Enterprise plan. WarpBuild BYOC places runners in your own AWS, GCP or Azure account for $0.002 per Linux runner minute plus your cloud bill.

Related reading

• Fastest GitHub Actions runners: CPU, cache and complete-build results.
• GitHub Actions caching: cache keys, build caches and persistent storage.
• Avrea vs Depot: another comparison involving remote Docker builders.
• Avrea vs Blacksmith: the same x64 minute rate, with CPU and cache benchmarks.
• Avrea vs Ubicloud: managed runners with lower list prices inside an open-source cloud.
• All runner comparisons: pricing and links to the other providers.