2022 was a year of tremendous growth for us here at Qovery. We released Qovery V3, grew our customer base, saw our platform use grow exponentially, met our target revenue, and more! Thanks to the Qovery team for their hard work, we achieved an impressive amount in 2022. It’s truly a joy to work with brilliant people who live out our daily values - humility, hard work, and customer obsession! Thanks to our customers’ faith in us, we can do what we love and continue to grow. So, thank you!

Our last Qovery Demo Day took place on a live on Tuesday, 20th of December. This event aims to give you some insights into what we did during the past month and what’s next and showcase some of our new features. This Demo Day was a bit special, as it was the last of the year, and to celebrate, we brought the entire team along to do a retrospective of the year and answer any questions you might have about our product.

I recently had the opportunity to speak with Kevin Maschtaler, the Platform and Reliability lead at Tint, about their experience with Qovery. Tint began using Qovery in early 2022 to automate their infrastructure and support their team and customer growth. In this article, we will explore Tint's journey with Qovery, including how we continue to assist them with compliance in the testing and release process and how we help them save on cloud costs through our partnerships.

The last quarter of the year is over, and even though we have plenty of news in stock for the new year, it’s time to go through our quarter retrospective. In case you missed anything, here are the essential releases of Q4!

DevOps is one of the core pillars of any organization. As the company grows, its processes also scale to absorb the new growth. Scaling DevOps is inevitable for any organization's growth. You cannot scale consistently if your DevOps processes involve a lot of manual steps and take much time to deliver new projects. A scalable DevOps means the system can expand automatically during a high workload and shrink back when the needs are reduced to normal.

In a previous article, we walked you through key steps to become a proficient DevOps: However, even experienced DevOps are still struggling in their day-to-day work for several reasons. One of the most common challenges is the fast-paced nature of the DevOps field, which requires professionals to learn and adapt to new technologies and methodologies constantly. This can be difficult for even the most experienced individuals, as it requires them to stay up-to-date with the latest developments in the field.

Becoming a proficient DevOps professional involves mastering a wide range of technical and non-technical skills, as well as gaining a deep understanding of the principles and practices of DevOps. Here are some key steps that can help you to become a proficient DevOps professional.

CI/CD is the process that ensures that code updates are deployed efficiently and reliably. However, more than simply having CI/CD pipelines is required for modern business application development needs. The problems start as soon as your team grows, but your CI/CD process does not. Static CI/CD pipelines result in an operational bottleneck and slow down your application workflow. Today, we will discuss why scaling your CI/CD is an inevitable need for your organization.

Engineering teams’ autonomy and agility are vital in achieving efficient software development. However, manual infrastructure provisioning is a major source of inefficiency and bottleneck. As the developers wait for Ops teams to provision complex infrastructure, they cannot bring the creativity, speed, and agility expected of them. This is the reason successful companies are quickly adopting self-service infrastructure.

Kubernetes is today the most well-known container scheduler used by thousands of companies. Being able to quickly and automatically scale your application is something standard nowadays. However, knowing how to do it well is another topic. In this article, we'll cover how pod autoscaling works, how it can be used, when it's exciting and not, and finally, we'll cover it with a Qovery usage we have internally.