Namespace vs Tensorlake

Sandbox Benchmark Comparison · Updated October 23, 2026

Namespace
Faster in
1of 1 benchmark
#20 of 31 in Sandbox Provider Rating
vs
Tensorlake
Faster in
0of 1 benchmark
#8 of 31 in Sandbox Provider Rating

Namespace was faster in the only shared sandbox benchmark.

Head to head

  • DAXTotal workload time · lower is better
    Namespace faster1.69x
    Namespace
    46.21s
    Tensorlake
    78.16s

DAX

Full leaderboard

Namespace

100% success · October 30, 2026
Median
46.21s
Namespace DAX results

Tensorlake

100% success · October 23, 2026
Median
78.16s
Tensorlake DAX results

Median total workload time over time

13 runs · July 24, 2026 to October 23, 2026
NamespaceTensorlake

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

Tensorlake

Active CPU + allocated RAM
$0.017per run
78.16s median at $0.8000/hr

$0.07/core-hr active CPU + $0.015/GB-hr RAM (on-demand rates; Pro is ~40% lower).

Source pricing page
Compare sandbox costs across all providers →
Work at Namespace or Tensorlake? 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.
Read the full methodology →Raw results on GitHub ↗

Frequently asked questions

Have another question? Email us.

Namespace was faster in the only shared sandbox benchmark. In DAX (October 23, 2026), Namespace had a median total workload time of 46.21s versus 78.16s for Tensorlake, 1.69x faster.

PartnersGoogle Cloud Run