Kroki vs PyPI

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
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

Kroki vs PyPI: common questions

Which is more reliable, Kroki or PyPI?

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

Do Kroki and PyPI need an API key?

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

Can I call Kroki and PyPI from the browser?

Yes — both Kroki and PyPI 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 Kroki and PyPI free for commercial use?

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