LAPIS vs Makeup

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%100%
P50 · ms524791
P95 · ms8462529
Authnonenone
CORSyesyes
HTTPSyesno
Card requirednono
Commercial useunclearunclear
Data licenseOpen sequence data (GenBank/Nextstrain-derived); UnverifiedUnverified
Free tierFree — no key (open instance)Free — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LAPIS vs Makeup: common questions

Which is more reliable, LAPIS or Makeup?

On our scheduled checks, LAPIS leads on measured uptime — LAPIS at 100% versus Makeup at 99.02% 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, LAPIS or Makeup?

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

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

Can I call LAPIS and Makeup from the browser?

Only LAPIS 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 LAPIS and Makeup free for commercial use?

LAPIS has unclear commercial terms, and Makeup 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.