shipapis
StarSubmit an APISubmit API

Fruityvice vs LAPIS

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

APIFruityviceNEW—LAPISNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedOpen sequence data (GenBank/Nextstrain-derived); Unverified
Free tierFree — no API keyFree — no key (open instance)
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Fruityvice vs LAPIS: common questions

Which is more reliable, Fruityvice or LAPIS?

On our scheduled checks, LAPIS leads on measured uptime — Fruityvice at —% versus LAPIS 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 Fruityvice and LAPIS need an API key?

Neither needs a paid key — Fruityvice 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 Fruityvice and LAPIS from the browser?

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

Are Fruityvice and LAPIS free for commercial use?

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