Skip to main content

Celesto CI / Compare

Celesto vs Namespace

Both Celesto and Namespace offer pay-as-you-go Linux runners. At 2 vCPU and 4 GB, Celesto costs $0.0005/minute; Namespace lists $0.002/minute prepaid or $0.003/minute pay as you go. Namespace also offers macOS, Windows, ARM, and persistent cache volumes.

List rates before allowances and credits; checked November 1, 2026. Sources and assumptions

Same 2 vCPU · 4 GB runner
4×Linux runtime per dollar
75% less per minute · $0.0005 vs $0.002
Monthly plans
Optional on both
Namespace Developer is pay as you go. Its $100/month Team plan includes 100,000 unit minutes.
2 vCPU · 4 GB
$0.0005/min
Namespace lists $0.002/min prepaid or $0.003/min pay as you go/overage. Equal runtime, before credits and storage.

What your Linux runtime costs on Namespace and Celesto.

Pick a monthly runtime and a runner size.

Runtime per month

Enter a whole number from 0 to 10,000,000.

Runner size

Lower is better

Celesto Standard2 vCPU · 4 GB$10.00
Namespace2 vCPU · 4 GB$40.00

List-price difference before allowances: $30.00 per month.

Namespace runner prices at matching CPU and RAM.

Published Namespace Linux x64 sizes with an exact CPU and memory match in the Celesto catalog.

Per-minute Linux x64 runner prices in USD, matched by CPU and memory
HardwareCelestoNamespaceCI per dollar
2 vCPU · 4 GB$0.0005/min$0.002/min4×75% less
2 vCPU · 8 GB$0.00067/min$0.004/min6×83% less
4 vCPU · 16 GB$0.0013/min$0.008/min6×83% less
8 vCPU · 32 GB$0.0027/min$0.016/min6×83% less

Lower Linux runtime rates, with dependency caching included.

A check marks whoever has the edge on that line.

Pricing

2 vCPU · 4 GB Linux
Celesto$0.0005/min Has the edge
Namespace$0.002/min prepaid; $0.003/min pay as you go/overage
Monthly plan required
CelestoNo; runtime uses workspace credit
NamespaceNo; Developer is pay as you go. Team is $100/month and Business $250/month
Billing basis
CelestoComputer runtime, including preparation and cleanup
NamespaceUnit minutes based on CPU, memory, and platform; one-minute minimum

Workloads and caching

Linux x64 GitHub Actions
CelestoUbuntu 24.04, up to 8 vCPU / 32 GB
NamespaceCustomizable Linux AMD64 runner profiles, larger shapes available Has the edge
Additional platforms
CelestoLinux x64
NamespaceLinux ARM64, Windows, macOS, Linux on Apple Silicon Has the edge
Dependency caching
CelestoExisting actions/cache and setup action caches; up to 25 GiB per paid repo included
NamespacePersistent Cache Volumes; framework integrations and storage charges vary by plan
Docker layer reuse
CelestoBuildKit type=gha, included in cache allowance; local image store starts fresh
NamespaceRemote Docker builders and cache integrations Has the edge
Logs and results
CelestoGitHub Actions
NamespaceGitHub Actions, plus Namespace observability Has the edge

Use Celesto for Linux jobs; keep Namespace for other platforms or persistent caches.

Choose Celesto if

  • Your Linux jobs exceed included allowances and you want a lower per-minute rate
  • You want to preserve compatible actions/cache steps
  • Your jobs fit Linux x64 and the 8 vCPU / 32 GB ceiling
  • Your agent-driven pull requests create variable CI demand

Stay on Namespace if

  • You need macOS, Windows, ARM, or larger runner shapes
  • Persistent cache volumes or remote Docker builders matter to your workload
  • You want Namespace’s wider build and developer environment platform

Move Namespace Linux jobs to Celesto.

Install the GitHub App, then swap the runner label. Keep compatible workflow steps and cache configuration; logs stay in GitHub Actions. Celesto stores caches separately, so expect an initial cache miss.

Runner label
1# Before
2runs-on: namespace-profile-linux-2x4
3
4# After
5runs-on: celesto-standard

Namespace pricing, caching, and migration questions.

At equal Linux runtime, Celesto Standard is $0.0005/minute for 2 vCPU and 4 GB, compared with Namespace’s $0.002 prepaid or $0.003 pay-as-you-go/overage rate. That is 75% below the prepaid compute rate. Actual bills depend on runtime, plan utilization, storage, and credits; this is not a measured speed comparison.

Linux usage is max(vCPU count, RAM in GB divided by two) unit minutes per wall-clock minute. A 2 vCPU / 4 GB runner uses two units; 2 vCPU / 8 GB uses four. Windows and macOS have additional platform multipliers. Our price table uses Namespace’s published Linux prepaid rates.

Yes. GitHub Actions chooses runners per job. Move compatible Linux x64 jobs to Celesto while retaining Namespace for platforms, larger shapes, or specialized caching. Namespace-specific cache actions and remote builder configuration may need changes.

Linux x64 jobs include actions/cache and setup-node/setup-python caching without changes to compatible cache steps. Cache storage has no separate charge. Default per-repository limits are 5 GiB on trial and promotional credit and 25 GiB on paid credit; caches expire after 7 idle days. CI runtime consumes workspace credit.

Docker Engine, Buildx, and Compose are preinstalled. Docker builds, Compose workflows, and GitHub service containers are verified. Validate Docker actions and whole-job containers before migrating. Docker’s explicit --cpus flag failed the documented preflight.

Yes. Use docker/setup-buildx-action with docker/build-push-action, cache-from: type=gha, and cache-to: type=gha,mode=max. Build layers persist in Celesto’s cache service and share the dependency cache’s per-repository storage allowance and 7-day idle expiry, with no separate storage fee. Each runner’s local Docker image store still starts fresh; docker pull and docker run images are not cached by this feature.

Sources and assumptions

Namespace pricing and capabilities checked November 1, 2026. Sources, including current Celesto CI documentation: Namespace pricing and unit minutes · Namespace GitHub Actions and caching · Celesto CI dependency caching · Celesto CI Docker and services. Celesto prices come from the current runner catalog. Rates compare list prices, not measured job speed. Namespace is a trademark of its owner; Celesto is not affiliated with it.

Compare one Linux workflow before moving the rest.

Run the same commit with cold and warm caches on both providers. Compare job duration and billed runtime, then use the CI setup steps to configure the remaining jobs.

Install Celesto CI