Makeup vs Open Disease

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

Uptime · 30d
Uptime · 90d98.9%99.44%
Uptime · 30d96.6%100%
P50 · ms557217
P95 · ms25291159
Authnonenone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (sources vary; see project repo)
Free tierFree — limits not publishedFree — no key required
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Makeup vs Open Disease: common questions

Which is more reliable, Makeup or Open Disease?

On our scheduled checks, Open Disease leads on measured uptime — Makeup at 98.9% versus Open Disease at 99.44% 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, Makeup or Open Disease?

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

Neither needs a paid key — Makeup 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 Makeup and Open Disease from the browser?

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

Are Makeup and Open Disease free for commercial use?

Makeup 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.