Hoppscotch vs Kroki

Same instrument, two spec sheets — measured, not claimed.

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms552633
P95 · ms25193183
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Hoppscotch vs Kroki: common questions

Which is more reliable, Hoppscotch or Kroki?

Both are neck-and-neck — Hoppscotch and Kroki each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Hoppscotch or Kroki?

Hoppscotch has the lower median latency in our checks — Hoppscotch responds in 552 ms versus Kroki at 633 ms (P50). Tail latency (P95) is in the table above; for most workloads the median is the number that shapes how the API feels.

Do Hoppscotch and Kroki need an API key?

Neither needs a paid key — Hoppscotch is callable with no signup, and Kroki is callable with no signup. Both are quick to prototype with; rate limits still apply.

Can I call Hoppscotch and Kroki from the browser?

Yes — both Hoppscotch and Kroki send CORS headers over HTTPS, so front-end code can fetch either directly with no backend proxy. That makes them easy to swap in a client-side app while you compare responses.

Are Hoppscotch and Kroki free for commercial use?

Hoppscotch has unclear commercial terms, and Kroki has unclear commercial terms. We track service terms and the data license as separate fields — see the Commercial use and Data license rows above, and confirm both before shipping either in a paid product.