GDBrowser vs Lichess

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
Authnonenone
CORSyesyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — no API keyFree — limits not published
Rate limit150 req/window · 149 remaining · resets 1783513202Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

GDBrowser vs Lichess: common questions

Which is more reliable, GDBrowser or Lichess?

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

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

Can I call GDBrowser and Lichess from the browser?

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

GDBrowser has unclear commercial terms, and Lichess 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.