Celesto vs Namespace
Celesto gives you 4× the Linux runtime per dollar at matching 2 vCPU and 4 GB, even against Namespace’s lower prepaid rate. Keep GitHub Actions and skip a monthly compute commitment.
List rates before allowances and credits; checked November 1, 2026. Sources and assumptions
- Same 2 vCPU · 4 GB runner
- 4×more CI per dollar
- 75% less per minute · $0.0005 vs $0.002
- Monthly compute commitment
- None
- Celesto uses prepaid workspace credit without a monthly plan. Namespace Team is $100/month with 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.
Compare list runtime costs.
Pick a monthly runtime and a runner size.
List runtime costs before allowances, credits, plan fees, or add-ons, assuming equal runtime. The table uses Namespace’s lower prepaid Linux prices, not its 1.5× higher pay-as-you-go/overage rates. Team costs $100/month for 100,000 unit minutes, Business $250 for 250,000. A 2 vCPU / 4 GB Linux runner consumes two unit minutes per wall-clock minute. Storage and remote builds have their own pricing. Equal CPU and RAM do not establish equal hardware or job duration. These are not predicted bills or measured job performance. Sources and checked date.
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.
Prices by runner size.
Published Namespace Linux x64 sizes with an exact CPU and memory match in the Celesto catalog.
| Hardware | Celesto | Namespace | CI per dollar |
|---|---|---|---|
| 2 vCPU · 4 GB | $0.0005/min | $0.002/min | 4×75% less |
| 2 vCPU · 8 GB | $0.00067/min | $0.004/min | 6×83% less |
| 4 vCPU · 16 GB | $0.0013/min | $0.008/min | 6×83% less |
| 8 vCPU · 32 GB | $0.0027/min | $0.016/min | 6×83% less |
Lower Linux runtime rates, with dependency caching included.
A check marks whoever has the edge on that line.
| Feature | Celesto | Namespace |
|---|---|---|
| Pricing | ||
| 2 vCPU · 4 GB Linux | $0.0005/min(Celesto has the edge) | $0.002/min prepaid; $0.003/min pay as you go/overage |
| Compute commitment | No monthly plan fee(Celesto has the edge) | Developer pay as you go; Team $100/month, Business $250/month |
| Billing basis | Computer runtime, including preparation and cleanup | Unit minutes based on CPU, memory, and platform; one-minute minimum |
| Workloads and caching | ||
| Linux x64 GitHub Actions | Ubuntu 24.04, up to 8 vCPU / 32 GB | Customizable Linux AMD64 runner profiles, larger shapes available(Namespace has the edge) |
| Additional platforms | Linux x64 | Linux ARM64, Windows, macOS, Linux on Apple Silicon(Namespace has the edge) |
| Dependency caching | Existing actions/cache and setup action caches; up to 25 GiB per paid repo included | Persistent Cache Volumes; framework integrations and storage charges vary by plan |
| Docker layer reuse | Registry caches or portable archives; local layers do not persist | Remote Docker builders and cache integrations(Namespace has the edge) |
| Logs and results | GitHub Actions | GitHub Actions, plus Namespace observability(Namespace has the edge) |
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
- Compute commitment
- CelestoNo monthly plan fee Has the edge
- NamespaceDeveloper pay as you go; Team $100/month, 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
- CelestoRegistry caches or portable archives; local layers do not persist
- NamespaceRemote Docker builders and cache integrations Has the edge
- Logs and results
- CelestoGitHub Actions
- NamespaceGitHub Actions, plus Namespace observability Has the edge
Spend less on Linux jobs; keep specialized builds where they fit.
Choose Celesto if
- You want lower Linux list rates without a monthly compute commitment
- 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
Switch in one line.
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: [self-hosted, celesto-standard]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.
No. Each job starts fresh. Use registry caches or portable archives through actions/cache to reuse layers. Direct BuildKit type=gha,version=2 cache export failed the documented preflight.
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.