Operations | Monitoring | ITSM | DevOps | Cloud

The DevOps industry has been experiencing rapid growth over the past few years. However, with this growth comes a shortage of skilled DevOps engineers who can efficiently implement and maintain the practices. Organizations are facing the challenge of finding and retaining qualified professionals, but there is a solution. Utilizing the right tools and technologies can empower organizations to overcome the DevOps talent shortage.

GitLab CI is a powerful tool for managing the software development and deployment process. It allows you to define and automate build, test, and deployment pipelines and provides features such as version control, collaboration, and continuous integration. However, while GitLab CI is an excellent tool for managing a single environment, it can have some limitations when it comes to managing multiple environments, especially dynamic environments.

Terraform is one of the most popular infrastructures as code (IaC) tools that allow users to define, configure, and deploy infrastructure resources in a safe, predictable, and repeatable manner. Using declarative configuration files, users can deploy resources across a variety of infrastructure providers, including public cloud platforms like AWS, Azure, and Google Cloud, as well as on-premises environments and third-party services.

Managing multiple environments with Terraform can be a complex and time-consuming task. An environment refers to a specific configuration or set of resources within a system, such as development, staging, or production environment. These environments often have different requirements and configurations, and managing them separately can be challenging.

We are excited to announce that Qovery now supports AWS Security Token Service (STS) for all our plans! AWS STS is a web service that enables you to request temporary, limited-privilege credentials for AWS Identity and Access Management (IAM) users or for federated users who sign in using Single Sign-On (SSO). These credentials are then used to access AWS resources and services.

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!