Avrea vs Namespace

Features at a glance

Both providers offer persistent storage and build-cache integrations.

Runner pricing

At these x64 sizes, Avrea's per-minute rate matches Namespace's prepaid rate and is lower than Namespace's overage rate.

Namespace also offers a smaller-memory 2-vCPU / 4-GB shape at $0.002 prepaid or $0.003 overage per minute. Its Linux billing uses the higher of vCPU count or RAM in GB divided by two, which makes the matched 2-vCPU / 8-GB shape four compute units. Namespace pricing.

Namespace has a $0-per-month Developer plan and prepaid plans starting at $100 per month. Cache volumes and snapshots have separate usage charges and plan allowances. Plan details.

Avrea has no monthly base fee and includes 3,000 monthly minutes in 2-vCPU equivalents. Larger runners use the allowance proportionally. It includes 25 GB of cache storage per repository, with additional cache storage available to purchase. Avrea pricing, cache storage.

Avrea also offers static IPs at $100 per IP per month, listed under its Enterprise features. Static IP pricing.

For included minutes and storage costs, see our GitHub Actions pricing guide.

Compare a completed job

For a ten-minute job at the matched 2-vCPU / 8-GB size, compute costs $0.04 on Avrea, $0.04 on Namespace prepaid, or $0.06 at Namespace’s overage rate, before allowances and storage. The equal prepaid minute rate makes job duration and cache charges the main variables in that comparison.

CPU benchmarks

These are RunsOn’s 14 October 2026 results for 4-vCPU / 16-GB x64 runners.

Each row uses five runs. These CPU scores do not measure complete builds. RunsOn CPU results. Data: RunsOn, CC BY 4.0; selected rows, shortened labels.

Namespace has the higher CPU scores in this sample; Avrea restores the Actions cache faster in the test below.

Actions cache benchmarks

RunsOn's 14 October 2026 results compare actions/cache transfers of a 4 GB file. These are the 4-vCPU / 16-GB x64 results:

Avrea restores faster; Namespace saves faster. The test does not measure Namespace Cache Volumes. It uses GitHub's cache service on Namespace and Avrea's cache on Avrea. RunsOn results and exclusions.

These five-run samples measure cache transfers, not complete builds. RunsOn sells runners too. Data: RunsOn, CC BY 4.0; selected rows, shortened labels.

Caching

Avrea automatically routes supported actions/cache requests to its cache. Package proxies reuse downloads, while integrations for Turborepo, Gradle, Bazel and sccache reuse valid build outputs to skip repeated work. Persistent disks also retain Docker images, layers and builder state between jobs. Avrea caching, build-cache setup.

Namespace’s persistent-storage option is Cache Volumes. A runner gets a clone of cached data on local NVMe storage, so it can use that data without a separate cache download. You configure a cache volume on the runner profile and select what to cache through Namespace's action or directory mappings. Namespace also supports Docker image caching and custom runner images. Namespace Cache Volumes, cache action.

Namespace also configures Remote Builders for Docker by default. Its migration guide says to remove docker/setup-buildx-action if it overrides that configuration. Namespace Docker setup.

Namespace also documents native caching integrations for Bazel, Turborepo, Pants and Moonrepo. Its caching options include both persistent files and build-system integrations. Namespace build-system integrations.

Our caching guide covers cache keys and invalidation; our runner benchmark guide explains how cache reuse affects complete job times.

Docker cache configuration

Avrea's Docker cache uses either a BuildKit cache URL or persistent-disk configuration. Namespace Cache Volumes use runner profiles and directory or tool selection. Avrea Docker setup, Namespace cache action.

CI fixes and environments for coding agents

Fixing failed CI jobs

When a test fails, Avrea Quality uses the logs, code changes and test history to work on a fix. It runs the proposed change through your full test suite and opens a pull request if it passes. The PR is ready for your team to review.

Avrea’s logs and resource metrics show what happened before a process died, including whether memory use climbed. SSH access lets you inspect a job while it is still running.

Remote environments

Avrea offers sandboxes in beta. Namespace Devboxes provide development environments for running a codebase with its tests, dependencies and services. Developers and agents can configure them through an SDK, CLI or web interface, with SSH access for debugging.

Choosing between Avrea and Namespace

Avrea gives you the listed prepaid x64 rate without committing to a monthly plan, along with caches that reuse packages and build outputs. Its diagnostics help locate slow or failing steps, and Quality can turn CI evidence into a tested pull request.

For an existing Namespace workflow, Docker builder time and cache-volume and snapshot charges contribute to the total alongside runner usage.

Related reading

• Avrea pricing: current runner sizes, rates and included features.
• Avrea vs Blacksmith: CPU benchmarks, caching and AI-assisted fixes.
• Avrea vs Depot: runner costs, Docker builds and remote caches.
• Avrea vs WarpBuild: equal x64 minute rates, cache benchmarks and BYOC.
• Avrea vs Ubicloud: managed runner prices, standard and premium tiers, caching.
• All runner comparisons: including GitHub-hosted runners.