Why we still build with Ruby in 2026
When we started Lago, we picked Ruby on Rails for our core API. The choice was obvious because our founding team had decade of Rails experience. Rails was the fastest way we could build an API prod...
Source: DEV Community
When we started Lago, we picked Ruby on Rails for our core API. The choice was obvious because our founding team had decade of Rails experience. Rails was the fastest way we could build an API product. Today, we've receive millions of API calls a day. We've upgraded through multiple Ruby/Rails versions. Maybe that sounds silly in a world where young, Python/Go/JS-wielding entitlements have never even heard of Ruby. We do admit that we've added Go and Rust where it makes sense. But if we were starting today, in 2025, we'd still choose Rails. The boring superpower: shipping speed Nowadays, the companies championing Ruby are no longer fast-growing startups run by CEOs in their 20s. They're mature enterprises run by middle-aged dads: Shopify, Basecamp, GitHub, GitLab… they're not exactly trendy AI startups. You could deduce that Rails is outdated, but another view on that fact is that it has great longevity. When we started, we frankly chose Rails for a practical reason: We had the most ex
