Neotimo DGFiP Mirror vs OpenRegistry
Same instrument, two spec sheets — measured, not claimed.
Neotimo DGFiP Mirror vs OpenRegistry: common questions
Which is more reliable, Neotimo DGFiP Mirror or OpenRegistry?
On our scheduled checks, Neotimo DGFiP Mirror leads on measured uptime — Neotimo DGFiP Mirror at 100% versus OpenRegistry at 98.0% 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, Neotimo DGFiP Mirror or OpenRegistry?
OpenRegistry has the lower median latency in our checks — Neotimo DGFiP Mirror responds in 524 ms versus OpenRegistry at 363 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 Neotimo DGFiP Mirror and OpenRegistry need an API key?
Neotimo DGFiP Mirror needs no key, while OpenRegistry requires a free API key. If you want to start calling without signup, reach for Neotimo DGFiP Mirror first.
Can I call Neotimo DGFiP Mirror and OpenRegistry from the browser?
Yes — both Neotimo DGFiP Mirror and OpenRegistry 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 Neotimo DGFiP Mirror and OpenRegistry free for commercial use?
Neotimo DGFiP Mirror has unclear commercial terms, and OpenRegistry 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.