Open5e vs Traveller Map

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 licenseSRD content under OGL 1.0a; API/site MIT-licensedUnverified
Free tierFree, no API key requiredFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Open5e vs Traveller Map: common questions

Which is more reliable, Open5e or Traveller Map?

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

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

Can I call Open5e and Traveller Map from the browser?

Yes — both Open5e and Traveller Map 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 Open5e and Traveller Map free for commercial use?

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