LAPIS vs wger Workout

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms5241134
P95 · ms8461964
Authnonenone
CORSyesyes
HTTPSyesyes
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 wger Workout: common questions

Which is more reliable, LAPIS or wger Workout?

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

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

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

Can I call LAPIS and wger Workout from the browser?

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

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