Kroki vs PageBolt

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms633751
P95 · ms31831432
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 PageBolt: common questions

Which is more reliable, Kroki or PageBolt?

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

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

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

Can I call Kroki and PageBolt from the browser?

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

Are Kroki and PageBolt free for commercial use?

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