Kroki vs Logotypes

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

Uptime · 30d
Uptime · 90d100%47.8%
Uptime · 30d100%0.0%
P50 · ms3413645
P95 · ms31834993
Authnonenone
CORSyesno
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

Kroki vs Logotypes: common questions

Which is more reliable, Kroki or Logotypes?

On our scheduled checks, Kroki leads on measured uptime — Kroki at 100% versus Logotypes at 47.8% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Kroki or Logotypes?

Kroki has the lower median latency in our checks — Kroki responds in 341 ms versus Logotypes at 3645 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 Logotypes need an API key?

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

Can I call Kroki and Logotypes from the browser?

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

Are Kroki and Logotypes free for commercial use?

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