Kroki vs QR & Barcode

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms633722
P95 · ms31831344
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 QR & Barcode: common questions

Which is more reliable, Kroki or QR & Barcode?

Both are neck-and-neck — Kroki and QR & Barcode each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Kroki or QR & Barcode?

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

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

Can I call Kroki and QR & Barcode from the browser?

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

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