Operations | Monitoring | ITSM | DevOps | Cloud

I am excited to launch a new series of engineering articles to dig into all the details of How we Built Qovery. A platform built for DevOps, SRE, Platform Engineers, and Developers since January 2020. Since day 1, the Qovery team has strived to make Qovery as open as possible and fight against the black box effect! In this series of 5 articles, I will explain as much as possible how things work behind the scene.

Right at the beginning of the summer was the launch of our console V3 in Alpha testing; as explained in this article, the main goal of this V3 was to solve the UX issues present in the V2; it's also fully open source and rewritten from scratch in React. We gathered many feedbacks, and our Frontend team is continuing to add every feature already available on the V2 to go from Alpha to Beta testing at the end of September.

You are using Qovery, and you love the product, but what about saving some money on your cloud bills on top? Today, we are making your dreams come true with a brand new partnership with Usage AI, and today, I will explain everything you need to know about it.

The staging environment plays a crucial role in product development. It's the last checkpoint before the product updates are live for customers. Every successful product has a robust and effective staging environment on the back. However, the traditional staging environments cannot keep pace with the modern CI/CD workflow. This article will go through how traditional shared and static staging environments hinder faster deployments and efficiency.

Hi there, Albane writing, Product Marketing Manager at Qovery, writing to your from Texas 🤠 With Romaric (CEO at Qovery) and Morgan (Co-founder at Qovery), we spent the last two days promoting Qovery at the Developer Week Cloud that took space in Austin, Texas. After weeks of preparation, quite a few hours of travel, and a whole setup, let me give you some insights about our first-ever conference as an exhibitor!

A few days ago, I chatted with Florian Suchan (CTO and Co-Founder at Papershift) about their journey to easy infrastructure autoscaling. As you will see in the article, they tried a wide range of solutions before finding the right fit; if you feel you’re going through the same journey, this article is for you!

Kubernetes is the industry's most popular open-source platform for container orchestration. It helps you automate many tasks related to container management. Companies use it to solve their problems related to deployment, scalability, testing, management, etc. However, Kubernetes is complex and requires a steep learning curve. In this article, we will go through some common Kubernetes pitfalls most companies fall to.

While the cloud offers significant benefits compared to traditional on-premise infrastructure, its inherent elasticity and scalability lead to uncontrolled costs. Cloud costs can be opaque and difficult to analyze — and without some system of identifying the source of costs and how to manage them — they can quickly undermine your profit margins. Since Qovery makes it easy to create on-demand environments, it can drastically grow your cloud costs.

One of the great things about GitFlow is that it makes parallel development very easy by isolating new development from finished work. New development, such as features, is done in feature branches and is only merged back into the main body of code when developers have validated the feature and the code is ready for release. For most development teams, feature validation happens in a staging branch coupled with a single testing environment.

Ephemeral environments are getting popular among companies that need to scale their business efficiently. Traditionally, the deployment environments usually included development, QA, staging, UAT, and production. However, the bottlenecks with shared QA and staging environments have hindered the efficient workflow of IT teams. The first issue you will face is environment drift because it is a shared environment, and you cannot afford a separate static environment for each developer.