Our Blog

Ephemeral environments are essential, but most teams overlook the backend. Here’s why buying, not building, is the smarter choice.

Mélanie Dallé

Senior Marketing Manager

Traditional programming is built around well-defined inputs and deterministic logic. Developers write functions that take structured inputs, apply a predefined set of operations, and return a structured output. This model works well when the input space is predictable, but it struggles with problems where inputs are ambiguous, unstructured, or constantly evolving.

Romaric Philogène

CEO & Co-founder

Infrastructure management is critical for companies building and scaling applications. Traditional managed services (MSPs) handle these tasks externally but often come with high costs, slow execution, and limited flexibility. For teams needing control, speed, and efficiency, DevOps automation platforms might offer a much better alternative. Let's compare these two approaches to identify the best option in terms of simplicity, developer experience (DX), time efficiency, operational and financial costs, and support.

Morgan Perry

Co-founder

TL;DR: We discovered the hard way that when backtrace is enabled, the anyhow library is capturing a backtrace on every error. Only when printing this error in debug format!(”err: {:?}”, error) backtrace’s symbols are resolved to human-friendly names, thus leading to a significant memory increase for your application. If you need backtrace only on panic, you must set two environment variables, RUST_BACKTRACE=1, and RUST_LIB_BACKTRACE=0, to avoid the issue.

Romain Gérard

Staff Software Engineer

At Qovery, we allow our users to spin up Kubernetes clusters on AWS, GCP, and Scaleway in 5 minutes. Recently, we began offering Karpenter as a node auto-scaler option when creating an EKS cluster - a feature that can be enabled with just one click.

Pierre Gerbelot-Barillon

Software Engineer

As we wrap up 2024, we are proud of everything we’ve accomplished together. This year was all about listening to our users, solving real problems, and continuing to build the tools you need to move fast without the headaches of DevOps complexity. From launching new features to expanding partnerships and empowering teams worldwide, 2024 was packed with milestones. None of this would have been possible without you, our amazing community. Let’s take a moment to reflect on what made 2024 so special.

Romaric Philogène

CEO & Co-founder

At Qovery, we are closely following the development of EKS Auto Mode, a new feature from AWS designed to simplify Kubernetes management by automating various foundational components. While we recognize the effort AWS has put into this, our initial evaluation shows that EKS Auto Mode is still in its early stages and does not yet offer sufficient value to be a strong consideration for our users.

Pierre Mavro

CTO & Co-founder

For scaling businesses, transitioning from PaaS (Platform as a Service) to IaaS (Infrastructure as a Service) is less about a choice and more about necessity. Staying on PaaS too long can result in skyrocketing costs, limited flexibility, and performance bottlenecks - challenges that only grow as your workloads and team scale. This guide breaks down the essential steps for a successful migration to cloud providers like AWS, GCP or Azure, highlighting common pitfalls, and offers best practices to help you navigate the transition effectively.

Morgan Perry

Co-founder

Last week, I had the incredible opportunity to attend AWS re:Invent 2024 in Las Vegas with Pierre (CTO), Morgan (CRO), and Alessandro (Lead PM) from the Qovery team. Re:Invent brought together over 60,000 cloud enthusiasts, and being part of it was both exhilarating and inspiring. For me, this wasn’t just about pitching our product; it was about sharing our passion for solving real-world problems, meeting amazing people, and embracing the energy of this global cloud community. Here are the lessons I learned from re:Invent.

Romaric Philogène

CEO & Co-founder