Foodish vs LAPIS

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

Uptime · 30d
Uptime · 90d27.5%100%
Uptime · 30d11.7%100%
P50 · ms250524
P95 · ms760846
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (open-source)Open sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — no keyFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Foodish vs LAPIS: common questions

Which is more reliable, Foodish or LAPIS?

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

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

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

Can I call Foodish and LAPIS from the browser?

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

Are Foodish and LAPIS free for commercial use?

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