DocForge vs LibreTranslate

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

Uptime · 30d
Uptime · 90d100%100%
Uptime · 30d100%100%
P50 · ms1583619
P95 · ms24851474
Authnonenone
CORSnoyes
HTTPSyesyes
Card requirednono
Commercial useunclearunclear
Data licenseUnverifiedUnverified (software is AGPL-3.0)
Free tierFree — limits not publishedFree — /languages is keyless; hosted /translate may require a key or donation
Rate limitUnpublishedUnpublished (per hosted instance)
In directory since2026-07-052026-07-05
operationalpartialdownno data

DocForge vs LibreTranslate: common questions

Which is more reliable, DocForge or LibreTranslate?

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

LibreTranslate has the lower median latency in our checks — DocForge responds in 1583 ms versus LibreTranslate at 619 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 DocForge and LibreTranslate need an API key?

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

Can I call DocForge and LibreTranslate from the browser?

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

Are DocForge and LibreTranslate free for commercial use?

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