Kroki vs YADG

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

Uptime · 30d
Uptime · 90d100%2.9%
Uptime · 30d100%0.0%
P50 · ms6331308
P95 · ms31831359
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 YADG: common questions

Which is more reliable, Kroki or YADG?

On our scheduled checks, Kroki leads on measured uptime — Kroki at 100% versus YADG at 2.9% 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 YADG?

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

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

Can I call Kroki and YADG from the browser?

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

Are Kroki and YADG free for commercial use?

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