Crawlee vs Florida Man

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

Uptime · 30d
Uptime · 90d100%98.0%
Uptime · 30d100%96.7%
P50 · ms480255
P95 · ms1293897
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearyes
Data licenseUnverifiedMIT (repository license)
Free tierFree — limits not publishedFree — static JSON on GitHub Pages, no key
Rate limitUnpublishedUnpublished (served via GitHub Pages)
In directory since2026-07-052026-07-05
operationalpartialdownno data

Crawlee vs Florida Man: common questions

Which is more reliable, Crawlee or Florida Man?

On our scheduled checks, Crawlee leads on measured uptime — Crawlee at 100% versus Florida Man at 98.0% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Which is faster, Crawlee or Florida Man?

Florida Man has the lower median latency in our checks — Crawlee responds in 480 ms versus Florida Man at 255 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 Crawlee and Florida Man need an API key?

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

Can I call Crawlee and Florida Man from the browser?

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

Are Crawlee and Florida Man free for commercial use?

Crawlee has unclear commercial terms, and Florida Man allows commercial use on its free tier. 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.