Namespace vs Vercel

Sandbox Benchmark Comparison · Updated October 30, 2026

Namespace was faster in the only shared sandbox benchmark.

Head to head

  • DAXTotal workload time · lower is better
    Namespace faster1.80x
    Namespace
    46.21s
    Vercel
    83.37s

DAX

October 30, 2026

Namespace

100% success
Median
46.21s
Namespace DAX results

Vercel

100% success
Median
83.37s
Vercel DAX results

Median total workload time over time

15 runs · July 21, 2026 to October 30, 2026
NamespaceVercel

Cost per DAX run

Namespace

Per-minute unit minutes
$0.012per run
46.21s median at $0.7200/hr

8 vCPU/16 GB shape = 8 unit-min/min at the pay-as-you-go rate of $0.0015/unit-min. Team/Business plans include prepaid minutes at an effective $0.001/unit-min ($0.48/hr). Bills in 1-minute minimums with 15-second rounding.

Source pricing page

Vercel

Active CPU + provisioned memory
$0.032per run
83.37s median at $1.3632/hr

$0.128/active-CPU-hr per vCPU + $0.0212/GB-hr provisioned memory (wall clock). CPU upper bound at 100% utilization; real bills for I/O-bound runs are lower.

Source pricing page
Compare sandbox costs across all providers →
Work at Namespace or Vercel? See where you stand every day, with full run logs, not just on benchmark Friday.Get stealth benchmarks →

Methodology

  • One workload, every provider. The same script, payload, and model hit every provider, addressed the way its own API expects. Nobody gets a tuned or special path.
  • Repeated on a schedule. Every suite runs many iterations per provider, automated on a recurring schedule, so results reflect steady state rather than one lucky request.
  • Raw results published. Every run is committed as JSON to the public benchmarks repo, next to the code that produced it. Nothing is cherry-picked or held back.
  • How this comparison is built. Each benchmark compares the two providers' medians; results within 5% count as roughly even. A comparison is published when both providers have at least one successful run in the same benchmark from the last 30 days. A benchmark only gets a verdict when both providers completed at least 50% of its runs. If a provider’s latest run of a benchmark failed, its most recent successful run from that window is used instead.

Frequently asked questions

Have another question? Email us.

Namespace was faster in the only shared sandbox benchmark. In DAX (October 30, 2026), Namespace had a median total workload time of 46.21s versus 83.37s for Vercel, 1.80x faster.

PartnersGoogle Cloud Run