Coffee vs Open Disease

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

Uptime · 30d
Uptime · 90d99.02%99.02%
Uptime · 30d98.3%98.3%
P50 · ms698451
P95 · ms28261226
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree — no API keyFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Coffee vs Open Disease: common questions

Which is more reliable, Coffee or Open Disease?

Both are neck-and-neck — Coffee and Open Disease 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, Coffee or Open Disease?

Open Disease has the lower median latency in our checks — Coffee responds in 698 ms versus Open Disease at 451 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 Coffee and Open Disease need an API key?

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

Can I call Coffee and Open Disease from the browser?

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

Are Coffee and Open Disease free for commercial use?

Coffee has unclear commercial terms, and Open Disease 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.