Engineering
Why we still build with Ruby in 2025
Why we still choose Ruby on Rails in 2025: Learn how Lago scales millions of API events with Rails, Go, and Rust, balancing developer speed, concurrency, and performance.
Engineering
Why we still choose Ruby on Rails in 2025: Learn how Lago scales millions of API events with Rails, Go, and Rust, balancing developer speed, concurrency, and performance.
Engineering
Learn how we ship fast without breaking self-hosted instances, why bridge versions matter, and why billing infra needs more care than the average SaaS stack.
Engineering
We debunk common myths about open-source software and how they drive innovation and scalability. Learn from successful companies like Hugging Face and Lago.
Engineering
We revamped our website in 3 days using Relume after we had serious latency issues with Webflow. Here's how we did it:
Engineering
When choosing tools, developers often prioritize performance, but it's rarely the deciding factor. Most opt for solutions that are "fast enough" and offer other benefits, like strong communities.
Engineering
Charging customers is complex due to overlapping components like metering, billing, invoicing, and payments. But building a robust billing engine can help you solve that.
Engineering
Scaling our open-source platform required a shift from Postgres to a hybrid stack, integrating ClickHouse for efficient event handling. Here’s how we did it!
Engineering
Being “like Stripe, but open source” isn’t enough. Explore what makes open-source companies win—transparency, extensibility, and real product advantage.
Engineering
In this blog post, Lago's co-founder Raffi gives insight on the biggest challenges Fintech companies face when building a billing engine.
Engineering
Any engineer who once had to deal with timezones will tell you: time zones can be a nightmare. Here's how we tackled it at Lago.
Engineering
ORMs, often criticized, are typically misused rather than inherently flawed. While they present challenges in visibility and performance, correct usage can mitigate these issues.
Engineering
We finally reached this milestone 180 days after opening our repo. What was our journey like?