SLF vs GeoJS

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 — static file, no keyFree, no API key required
Rate limitUnpublishedUnpublished (no enforced limit stated)
In directory since2026-07-052026-07-05
operationalpartialdownno data

SLF vs GeoJS: common questions

Which is more reliable, SLF or GeoJS?

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

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

Can I call SLF and GeoJS from the browser?

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

SLF has unclear commercial terms, and GeoJS 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.