CDNJS vs OpenQR

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms2811125
P95 · ms9362851
AuthnoneapiKey
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree and open, no keyFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

CDNJS vs OpenQR: common questions

Which is more reliable, CDNJS or OpenQR?

Both are neck-and-neck — CDNJS and OpenQR 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, CDNJS or OpenQR?

CDNJS has the lower median latency in our checks — CDNJS responds in 281 ms versus OpenQR at 1125 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 CDNJS and OpenQR need an API key?

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

Can I call CDNJS and OpenQR from the browser?

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

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