Bootprint vs SHARE

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

Uptime · 30d
Uptime · 90d100%98.9%
Uptime · 30d100%96.6%
P50 · ms70261
P95 · ms6993119
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree — limits not publishedFree — limits not published
Rate limit60 req/window · 58 remaining · resets 1792038689Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Bootprint vs SHARE: common questions

Which is more reliable, Bootprint or SHARE?

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

Bootprint has the lower median latency in our checks — Bootprint responds in 70 ms versus SHARE at 261 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 Bootprint and SHARE need an API key?

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

Can I call Bootprint and SHARE from the browser?

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

Are Bootprint and SHARE free for commercial use?

Bootprint has unclear commercial terms, and SHARE 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.