Kroki vs Piloterr

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms633635
P95 · ms31831730
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Kroki vs Piloterr: common questions

Which is more reliable, Kroki or Piloterr?

Both are neck-and-neck — Kroki and Piloterr 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, Kroki or Piloterr?

Kroki has the lower median latency in our checks — Kroki responds in 633 ms versus Piloterr at 635 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 Kroki and Piloterr need an API key?

Kroki needs no key, while Piloterr requires a free API key. If you want to start calling without signup, reach for Kroki first.

Can I call Kroki and Piloterr from the browser?

Only Kroki is browser-friendly — it returns CORS headers over HTTPS. Piloterr needs a server-side call or proxy, so factor that into which one fits a front-end project.

Are Kroki and Piloterr free for commercial use?

Kroki has unclear commercial terms, and Piloterr 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.