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.

We at Qovery are excited to announce that G2 has named Qovery as a Summer 2022 High Performer in the following categories: Continuous Deployment / Environment as a Service. G2 is the world’s largest tech marketplace. The High Performer Award recognizes companies with high customer satisfaction ratings relative to their market presence.

Today, It's a sad day for thousands of developers that were able to host their applications for free on Heroku. Heroku (acquired by Salesforce) announced that they discontinue their free tier to focus on "mission critical" businesses. Heroku has undoubtedly changed how developers deploy their applications in the cloud - but now, what are the valid alternatives? Here is a list of the top 3 best Heroku alternatives.

2 months ago, I discovered Nixpacks - an alternative to Buildpacks to build a final container image that simply works. I’ve tried it with multiple projects, and the promise is very good. I feel it is less black magic than Buildpacks and easily extensible. In this article, I will share my feedback on the pros and the cons of this emerging project. Let's go!

Since the start of Qovery in 2019, a lot has evolved, the team got bigger, the product grew, a lot of new features were developed, and it’s now time for the pricing to change as well, but don’t worry, I’m not about to tell you that we are increasing our prices because of inflation, we’re just changing our approach in terms of pricing model and let me explain to you how this switch is going to remove plenty of stress from your shoulder!