Datasette vs OpenSanctions
Same instrument, two spec sheets — measured, not claimed.
Datasette vs OpenSanctions: common questions
Which is more reliable, Datasette or OpenSanctions?
Both are neck-and-neck — Datasette and OpenSanctions 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 OpenSanctions?
Datasette has the lower median latency in our checks — Datasette responds in 293 ms versus OpenSanctions at 387 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 OpenSanctions need an API key?
Neither needs a paid key — Datasette is callable with no signup, and OpenSanctions is callable with no signup. Both are quick to prototype with; rate limits still apply.
Can I call Datasette and OpenSanctions from the browser?
Yes — both Datasette and OpenSanctions 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 Datasette and OpenSanctions free for commercial use?
Datasette has unclear commercial terms, and OpenSanctions 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.