shipapis
StarSubmit an APISubmit API

LAPIS vs Squiggle

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

APILAPISNEW—SquiggleNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
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 Squiggle: common questions

Which is more reliable, LAPIS or Squiggle?

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

Do LAPIS and Squiggle need an API key?

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

Can I call LAPIS and Squiggle from the browser?

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

Are LAPIS and Squiggle free for commercial use?

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