Datasette vs RestoSignals

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms209748
P95 · ms2840748
AuthnoneapiKey
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified
Free tierFree — limits not published
Rate limitUnpublished
In directory since2026-07-052026-10-19
operationalpartialdownno data

Datasette vs RestoSignals: common questions

Which is more reliable, Datasette or RestoSignals?

Both are neck-and-neck — Datasette and RestoSignals 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, Datasette or RestoSignals?

Datasette has the lower median latency in our checks — Datasette responds in 209 ms versus RestoSignals at 748 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 Datasette and RestoSignals need an API key?

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

Can I call Datasette and RestoSignals from the browser?

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

Are Datasette and RestoSignals free for commercial use?

Datasette has unclear commercial terms, and RestoSignals 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.