Our Blog

Explore how ephemeral environments help development teams scale efficiently. This strategic guide for CTOs covers key benefits, technical insights, and practical steps to boost deployment speed, reduce costs, and streamline testing.

Mélanie Dallé

Senior Marketing Manager

Over the last three months, we’ve focused on solving three core challenges our users face: delivering faster, improving resiliency, and gaining tighter control over cloud infrastructure. Today, we’re excited to share the new features we rolled out in Q1 2025 - all built to help teams ship faster, with more confidence, and lower operational overhead.

Romaric Philogène

CEO & Co-founder

The Qovery CLI gives developers full control of their infrastructure from the terminal. Whether you're deploying apps, managing environments, or debugging issues, these commands will save you time and clicks.

Romaric Philogène

CEO & Co-founder

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

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