LibreTranslate vs RubyGems

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

Uptime · 30d
Uptime · 90d100%99.02%
Uptime · 30d100%98.3%
P50 · ms619311
P95 · ms14741639
Authnonenone
CORSyesyes
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 RubyGems: common questions

Which is more reliable, LibreTranslate or RubyGems?

On our scheduled checks, LibreTranslate leads on measured uptime — LibreTranslate at 100% versus RubyGems at 99.02% 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, LibreTranslate or RubyGems?

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

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

Can I call LibreTranslate and RubyGems from the browser?

Yes — both LibreTranslate and RubyGems 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 LibreTranslate and RubyGems free for commercial use?

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