shipapis
StarSubmit an APISubmit API

LibreTranslate vs ReportForge

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

APILibreTranslateNEW—ReportForgeNEW—
Uptime · 30d
Uptime · 90d—%—%
Uptime · 30d—%—%
P50 · ms——
P95 · ms——
Authnonenone
CORSyesno
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverified (software is AGPL-3.0)Unverified
Free tierFree — /languages is keyless; hosted /translate may require a key or donationFree — limits not published
Rate limitUnpublished (per hosted instance)Unpublished
In directory since2026-07-052026-07-05
operationalpartialdownno data

LibreTranslate vs ReportForge: common questions

Which is more reliable, LibreTranslate or ReportForge?

On our scheduled checks, ReportForge leads on measured uptime — LibreTranslate at —% versus ReportForge at —% over 90 days. These are our own probe results, not provider claims; the uptime bars above show the day-by-day record for both.

Do LibreTranslate and ReportForge need an API key?

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

Can I call LibreTranslate and ReportForge from the browser?

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

Are LibreTranslate and ReportForge free for commercial use?

LibreTranslate has unclear commercial terms, and ReportForge 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.