DEV Community

Aniket Maurya
Aniket Maurya

Posted on

Namespace vs Celesto CI: GitHub Actions runner pricing

I build Celesto CI. If you're comparing it with Namespace, start with two questions: which platforms do you need, and what does a minute of your actual runner configuration cost?

Namespace offers a broader compute and build platform, including Linux, Windows and macOS runners. Celesto focuses on Ubuntu Linux x64 CI with a lower published runtime rate. Both let you keep GitHub Actions.

For Linux x64 with 2 vCPU and 8 GB RAM, Namespace lists $0.006 per minute at its overage rate, versus Celesto's $0.00066667. Celesto's rate is about 89% lower. Namespace also offers a lower prepaid rate, so that is not the whole comparison.

Prices and documentation checked November 18, 2026. All prices are USD. This compares listed CPU and RAM, not identical physical hardware or measured cost per build.

The quick comparison

Namespace Celesto CI
Linux, 2 vCPU / 8 GB $0.006/min overage; $0.004/min effective prepaid $0.00066667/min, celesto-memory
Linux, 4 vCPU / 16 GB $0.012/min overage; $0.008/min effective prepaid $0.00133333/min, celesto-large
Linux, 8 vCPU / 32 GB $0.024/min overage; $0.016/min effective prepaid $0.00266667/min, celesto-xl
Monthly plan Developer $0, usage billed separately; Team $100; Business $250 No recurring CI platform subscription; runtime uses workspace credit
Included compute Team: 100,000 unit minutes; Business: 250,000, shared across CI and remote builds No recurring included-minute allowance advertised; one-time Micro trial
Platforms Linux x64 and ARM64, macOS; Windows on eligible paid plans Ubuntu 24.04 Linux x64
Setup Connect GitHub organization, create runner profile, change runs-on Install GitHub App, finish workspace setup, choose a runner label

Sources: Namespace pricing, Namespace runner setup, Celesto pricing and setup.

Namespace unit minutes are not job minutes

This is the detail worth checking before comparing bills.

Namespace prices compute in unit minutes. For Linux, the standard unit is 1 vCPU with 2 GB RAM for one minute. If you choose more memory, the larger resource requirement determines the unit count:

units = max(vCPU, RAM in GB / 2)

A 2-vCPU / 8-GB runner therefore consumes 4 unit minutes per running minute, not 2. Its published rate is $0.006/minute at the overage rate, or an effective $0.004/minute from prepaid units.

That also means Team's 100,000 included unit minutes cover 25,000 running minutes on this shape, if all those units go to these CI jobs. They do not cover 100,000 running minutes. Remote build usage draws from the same compute allowance.

Namespace's $0 Developer plan matters too. You do not need a $100 monthly subscription just to use Namespace runners.

What 10,000 Linux runner minutes cost

For the same listed 2-vCPU / 8-GB configuration:

Monthly running minutes Celesto Memory Namespace pay-per-use rate
2,000 $1.33 $12.00
10,000 $6.67 $60.00
25,000 $16.67 $150.00

These are runtime calculations, not invoice quotes. They assume equal billable runtime and exclude tax, storage, remote builds, credits, discounts and billing rounding.

At 25,000 minutes, Namespace Team is also worth considering: its $100 monthly fee includes enough units for that amount of compute on this shape, assuming no units are used elsewhere. That is lower than paying $150 at the overage rate. Team also includes other platform benefits, which may have value to your team.

Celesto's rate is about 83% below Namespace's effective prepaid rate on this shape. The comparison is not only against the higher overage rate.

One more billing detail: Namespace has a one-minute minimum and documents partial-minute rounding. Celesto includes runner preparation and cleanup in billed runtime; queue time before the machine starts is free. Do not turn test-step duration alone into a claimed bill.

Check what else is on the bill

Namespace documents remote Docker builders enabled by default on its runners. Its migration guide also calls out workflow changes, including removing docker/setup-buildx-action when using that configuration. Check this before treating a migration as nothing more than a runner-label change.

Celesto supports Docker Engine, Buildx, Compose and GitHub service containers. Its GitHub Actions cache has no separate storage charge within the documented allowance: 25 GiB per paid or promotional-credit repository, or 5 GiB on the trial. Entries expire after seven idle days. Docker layers can use BuildKit's type=gha cache within the same allowance.

Count remote build charges and storage alongside runner compute when those features are used. A rate-only comparison does not include those costs or establish which provider has the lower bill for your workload.

When I would pick each

Pick Namespace if you need a wider platform mix, including macOS, Windows or ARM, or want to evaluate its remote builders and broader compute platform alongside CI. Check plan eligibility, concurrency and storage costs for your setup.

Try Celesto if your workflows run on Linux x64 and your main goal is lowering the cost of repeated checks. At the listed configurations above, the runtime rate leaves more room for frequent builds without adding a monthly CI subscription.

For Celesto's 2-vCPU / 8-GB runner, use:

jobs:
  test:
    runs-on: celesto-memory
    steps:
      - uses: actions/checkout@v4
      - uses: actions/setup-node@v4
        with:
          node-version: '22'
      - run: npm ci
      - run: npm test
Enter fullscreen mode Exit fullscreen mode

Install the GitHub App and finish setup first. Memory uses workspace credit. Celesto's one-time $5 trial is Micro-only and expires after 30 days; it does not fund the Memory runner in this example.

The takeaway

Namespace offers a broader platform. Celesto has a lower published Linux runtime rate at these listed CPU and RAM sizes, including against Namespace's effective prepaid rate. A lower rate alone does not guarantee a lower cost per completed build: duration, billing rules, plan allowances and other services still matter.

Check the actual charges for a workflow you already run, including full billable duration and any storage or remote-build costs. Compare the total with the plan you would actually use, rather than choosing from a single headline rate.

Try Celesto CI.

Top comments (0)