Findwork vs Hebrew Calendar

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms481533
P95 · ms19152016
AuthapiKeynone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified
Free tierFree tier — key may be requiredFree — limits not published
Rate limit4294967295 req/window · 4294967295 remaining · resets 0Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

Findwork vs Hebrew Calendar: common questions

Which is more reliable, Findwork or Hebrew Calendar?

Both are neck-and-neck — Findwork and Hebrew Calendar each measure 100% uptime over 90 days on our probe schedule. Reliability here is verified from our own scheduled checks; use the 30-day bars above to see which has been steadier lately.

Which is faster, Findwork or Hebrew Calendar?

Findwork has the lower median latency in our checks — Findwork responds in 481 ms versus Hebrew Calendar at 533 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 Findwork and Hebrew Calendar need an API key?

Hebrew Calendar needs no key, while Findwork requires a free API key. If you want to start calling without signup, reach for Hebrew Calendar first.

Can I call Findwork and Hebrew Calendar from the browser?

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

Are Findwork and Hebrew Calendar free for commercial use?

Findwork has unclear commercial terms, and Hebrew Calendar 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.