shipapis
StarSubmit an APISubmit API

Gcore CDN vs Scrnify

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

APIGcore CDNHEALTHY96ScrnifyHEALTHY88
Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms362927
P95 · ms12211742
AuthapiKeyapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — API key may be required for productionFree tier — API key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Gcore CDN vs Scrnify: common questions

Which is more reliable, Gcore CDN or Scrnify?

Both are neck-and-neck — Gcore CDN and Scrnify 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, Gcore CDN or Scrnify?

Gcore CDN has the lower median latency in our checks — Gcore CDN responds in 362 ms versus Scrnify at 927 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 Gcore CDN and Scrnify need an API key?

Both ask you to authenticate — Gcore CDN uses an API key and Scrnify 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 Gcore CDN and Scrnify from the browser?

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

Are Gcore CDN and Scrnify free for commercial use?

Gcore CDN has unclear commercial terms, and Scrnify 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.