OpenQR vs Sheetsu

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthapiKeyapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree tier — key may be required
Rate limitUnpublished90 req/window · 89 remaining
In directory since2026-07-052026-07-05
operationalpartialdownno data

OpenQR vs Sheetsu: common questions

Which is more reliable, OpenQR or Sheetsu?

On our scheduled checks, Sheetsu leads on measured uptime — OpenQR at —% versus Sheetsu 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 OpenQR and Sheetsu need an API key?

Both ask you to authenticate — OpenQR uses an API key and Sheetsu uses an API key. Each key is free to obtain; the Auth and Card-required rows above spell out the signup terms.

Can I call OpenQR and Sheetsu from the browser?

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

OpenQR has unclear commercial terms, and Sheetsu 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.