LAPIS vs OpenLigaDB

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

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

LAPIS vs OpenLigaDB: common questions

Which is more reliable, LAPIS or OpenLigaDB?

Both are neck-and-neck — LAPIS and OpenLigaDB each measure 100% 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, LAPIS or OpenLigaDB?

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

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

Can I call LAPIS and OpenLigaDB from the browser?

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

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