GDBrowser vs Lichess
Same instrument, two spec sheets — measured, not claimed.
GDBrowser vs Lichess: common questions
Which is more reliable, GDBrowser or Lichess?
Both are neck-and-neck — GDBrowser and Lichess each measure 99.02% 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, GDBrowser or Lichess?
GDBrowser has the lower median latency in our checks — GDBrowser responds in 209 ms versus Lichess at 436 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 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.