Neon vs ngrokAI Gateway Benchmark Comparison

Neon
Faster in 1 of 2
vs
ngrok
Faster in 1 of 2

Neon and ngrok were each faster in 1 of 2 shared AI gateway benchmarks.

Shared benchmarks
2
Last run
October 30, 2026
Want the full run details?Sign up free →

Scorecard

Median of each benchmark's primary metric; lower is better. Medians within 5% count as roughly even, and a benchmark gets no speed verdict when either provider completed fewer than 50% of runs.

BenchmarkNeonngrokResultRatio
OpenAI
Cold end-to-end latency · Run October 30, 2026
830ms
100% success
753ms
100% success
ngrok faster
1.10x
Kimi
Cold end-to-end latency · Run October 30, 2026
947ms
100% success
1862ms
100% success
Neon faster
1.97x

OpenAI

Run October 30, 2026

Time for a cold request routed through the gateway to GPT-5.4 Mini to return its complete response.

Cold end-to-end latency

Neon

100% success
Median
830ms
P95
989ms
P99
1022ms
Neon OpenAI results →

ngrok

100% success
Median
753ms
P95
1290ms
P99
1373ms
ngrok OpenAI results →

ngrok had a 1.10x lower median cold end-to-end latency (753ms vs 830ms for Neon).

Median cold end-to-end latency over time

10 runs from August 21, 2026 to October 30, 2026.

Neonngrok
View the full OpenAI leaderboard →

Kimi

Run October 30, 2026

Time for a cold request routed through the gateway to Kimi K3 to return its complete response.

Cold end-to-end latency

Neon

100% success
Median
947ms
P95
1665ms
P99
2312ms
Neon Kimi results →

ngrok

100% success
Median
1862ms
P95
2942ms
P99
3909ms
ngrok Kimi results →

Neon had a 1.97x lower median cold end-to-end latency (947ms vs 1862ms for ngrok).

Median cold end-to-end latency over time

10 runs from August 28, 2026 to October 30, 2026.

Neonngrok
View the full Kimi leaderboard →

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 the latency benchmark on at least two of the same model families reliably: at least 50% success for each provider, in benchmark runs from the last 30 days.

Frequently asked questions

Have another question? Email us.

Neon and ngrok were each faster in 1 of 2 shared AI gateway benchmarks. In OpenAI (October 30, 2026), ngrok had a median cold end-to-end latency of 753ms versus 830ms for Neon, 1.10x faster. In Kimi (October 30, 2026), Neon had a median cold end-to-end latency of 947ms versus 1862ms for ngrok, 1.97x faster.

PartnersGoogle Cloud Run