Our Blog

At Qovery, we're thrilled to introduce a groundbreaking way for AWS users to drastically reduce their costs — by up to 60% on EC2 instances. This significant reduction is made possible through the synergy of AWS Elastic Kubernetes Service (EKS) with Karpenter, AWS's powerful autoscaler.

Romaric Philogène

CEO & Co-founder

I am thrilled to introduce to you our new billing analytics feature, now generally available to all our users. This feature is designed to empower you with insights into your Qovery usage, enabling you to monitor, control, and optimize your cloud expenses effectively.

Romaric Philogène

CEO & Co-founder

I'm thrilled to announce the availability of Qovery on the AWS Marketplace. You can now buy and benefit from Qovery right from the AWS Marketplace. Before delving into the specific advantages of purchasing Qovery through the AWS Marketplace, let's first understand what the AWS Marketplace is and why this is something you should consider when purchasing Qovery's DevOps automation software.

Romaric Philogène

CEO & Co-founder

An Internal Developer Platform (IDP) is an ecosystem that empowers developers to manage the entire application lifecycle from development to deployment autonomously. As a vital component for organizations, the implementation of an IDP often presents a ‘Build vs. Buy’ dilemma: should you construct your own IDP, tailored to your unique needs, or would it be more efficient to purchase a pre-built solution? This decision is not a trivial one, and making the right choice can significantly impact your team’s productivity and your organization’s bottom line. In this article, we will conduct a transparent analysis of both options, exploring the benefits and challenges associated with each. We aim to provide you with comprehensive insights that can guide you in making the best choice for your team.

Morgan Perry

Co-founder

I'm thrilled to unveil a suite of groundbreaking features that we've introduced over the past four months at Qovery. Our commitment to enhancing your development and deployment experience continues to be our driving force. Recently, we shared these updates during our exhilarating public demo day, which you can watch here. Let's dive into the features that are set to redefine your interaction with Qovery.

Romaric Philogène

CEO & Co-founder

Kubernetes probes are essential tools for maintaining the health and reliability of applications running in containers. Among these, the liveness probe plays a critical role in checking if an application is running correctly. If it detects any problems, Kubernetes can automatically restart the affected container, thus ensuring the application remains available without manual intervention. In this hands-on guide, we will walk through the steps to configure a simple liveness probe, along with how they work, and their importance within the Kubernetes ecosystem. By the end, you should have a comprehensive understanding of liveness probes, including how to configure them and troubleshoot common issues.

Morgan Perry

Co-founder

Explore the top CI/CD platforms to automate your development workflow. Learn why CI/CD is essential for modern software teams and discover the unique features of 10 leading tools, including Harness, GitLab, and Qovery.

Morgan Perry

Co-founder

We are thrilled to share the exciting news that Qovery's DevOps automation software has once again been recognized as a Momentum Leader for DevOps in the Winter 2024 Grid Report. This marks the third consecutive time we've received this prestigious acknowledgment, and we couldn't be more grateful for the ongoing support of our incredible community of users 🙏

Morgan Perry

Co-founder

At Qovery, we build our frontend using Nx and rely on the official nrwl/ci GitHub Actions. Our frontend requires third-party tokens during compile time, but we would like to avoid hardcoding them or using the .env file to define our tokens. The latter exposes our source code directly on GitHub, and even though it's not sensitive data, we don't want it to be easily scraped. As probably many others, we've faced issues when we dug into environment variables using this reusable workflow: https://github.com/nrwl/ci?tab=readme-ov-file#limited-secrets-support https://github.com/nrwl/ci/issues/92 https://github.com/nrwl/ci/issues/44 So, I wanted to share the lessons I learned from this experience.

Camille Tjhoa

Senior Software Engineer