shipapis
StarSubmit an APISubmit API

GitHub Project Issues vs Kroki

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

APIGitHub Project IssuesHEALTHY90KrokiHEALTHY92
Uptime · 30d
Uptime · 90d99.02%100%
Uptime · 30d98.3%100%
P50 · ms478633
P95 · ms43103183
Authnonenone
CORSnoyes
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

GitHub Project Issues vs Kroki: common questions

Which is more reliable, GitHub Project Issues or Kroki?

On our scheduled checks, Kroki leads on measured uptime — GitHub Project Issues at 99.02% versus Kroki at 100% 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, GitHub Project Issues or Kroki?

GitHub Project Issues has the lower median latency in our checks — GitHub Project Issues responds in 478 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 GitHub Project Issues and Kroki need an API key?

Neither needs a paid key — GitHub Project Issues 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 GitHub Project Issues and Kroki from the browser?

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

Are GitHub Project Issues and Kroki free for commercial use?

GitHub Project Issues 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.