Cloudflare vs Tensorlake

Sandbox Benchmark Comparison · Updated October 30, 2026

Cloudflare and Tensorlake were each faster in 1 of 2 shared sandbox benchmarks.

Head to head

  • Burst TTITime to interactive · lower is better
    Cloudflare faster1.32x
    Cloudflare
    779ms
    Tensorlake
    1.03s
  • DAXTotal workload time · lower is better
    Tensorlake faster2.43x
    Cloudflare
    189.88s
    Tensorlake
    78.16s

Burst TTI

October 30, 2026

Cloudflare

100% success
Median
779ms
p95
1.21s
p99
1.36s
Cloudflare Burst TTI results

Tensorlake

100% success
Median
1.03s
p95
2.24s
p99
5.25s
Tensorlake Burst TTI results

Median time to interactive over time

77 runs · May 6, 2026 to October 30, 2026
CloudflareTensorlake

Cloudflare

100% success · October 30, 2026
Median
189.88s
Cloudflare DAX results

Tensorlake

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

Median total workload time over time

3 runs · October 16, 2026 to October 23, 2026
CloudflareTensorlake

Cost per DAX run

Cloudflare

Active CPU + provisioned memory
$0.038per run
189.88s median at $0.7200/hr

$0.000020/vCPU-s active-CPU + $0.0000025/GiB-s provisioned memory. CPU upper bound at 100% utilization. Requires $5/mo Workers Paid plan.

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 Cloudflare 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 only when both providers completed at least 50% of runs in 2 or more shared benchmarks run in the last 30 days. 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.

Cloudflare and Tensorlake were each faster in 1 of 2 shared sandbox benchmarks. In Burst TTI (October 30, 2026), Cloudflare had a median time to interactive of 779ms versus 1.03s for Tensorlake, 1.32x faster. In DAX (October 23, 2026), Tensorlake had a median total workload time of 78.16s versus 189.88s for Cloudflare, 2.43x faster.

PartnersGoogle Cloud Run