Announcing Qovery EC2: Deploy your apps on AWS for $20/m
Today, Qovery relies on an AWS EKS (Managed Kubernetes by AWS) to deploy your apps. This service costs you $220/month. Regardless that you deploy 1 or 10 applications. Our team has been working for two months on a $20/month offer to host your apps on AWS - Qovery AWS EC2. The difference? Qovery no longer spawns an AWS EC2 instance instead of an AWS EKS Kubernetes cluster. It's the perfect solution for your hobby project and testing environments.
Qovery EC2 vs EKS
The main difference between AWS EC2 and AWS EKS is the number of Availability Zones (AZ). If a network or power disruption happens on the AZ where the EC2 instance runs, your applications will no longer be available until it's solved. It's an acceptable outage for most of the development and hobby projects. We only recommend running development and hobby projects on an EC2 instance!
Here is a quick demo video of Qovery EC2👇🏻
How to get started?
Nothing easier:
1. Create a cluster
2. Choose AWS
3. Choose EC2
4. That's it! 🤩
.svg)
.svg)
.svg)
Suggested articles
Looking for a Flux CD alternative? Discover why Qovery stands out as the #1 choice. Compare features, pros, and cons of the top 10 platforms to simplify your deployment strategy and empower your team.
Heroku and AWS offer distinct benefits for startups and mid-size companies. This guide compares the differences between pricing, scalability, security, and developer experience to help you choose the right cloud platform based on your team’s needs and growth goals.
Master HIPAA compliance on Azure. Understand the Shared Responsibility Model, the critical role of the BAA, and how to configure Access Control, Encryption, and Networking. See how Qovery automates security controls for continuous compliance.
.webp)
Looking for a Portainer alternative? Discover why Qovery stands out as the #1 choice. Compare features, pros, and cons of the top platforms to simplify your deployment strategy and empower your team.
Kubernetes NGINX ingress maintainers have announced that the project will move into end-of-life mode and stop being actively maintained by March 2026. Parts of the NGINX Kubernetes ecosystem are already deprecated or archived.
.webp)