Open5e vs RAWG.io

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

Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms
P95 · ms
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseSRD content under OGL 1.0a; API/site MIT-licensedUnverified
Free tierFree, no API key requiredFree tier — key may be required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open5e vs RAWG.io: common questions

Which is more reliable, Open5e or RAWG.io?

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

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

Can I call Open5e and RAWG.io from the browser?

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

Are Open5e and RAWG.io free for commercial use?

Open5e has unclear commercial terms, and RAWG.io 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.