shipapis
StarSubmit an APISubmit API

LectServe vs Disify

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

APILectServeNEW—DisifyNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesyes
HTTPSnoyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limitUnpublishedUnpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LectServe vs Disify: common questions

Which is more reliable, LectServe or Disify?

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

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

Can I call LectServe and Disify from the browser?

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

Are LectServe and Disify free for commercial use?

LectServe has unclear commercial terms, and Disify 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.