June 2020, What's new? Gitlab support, persistent storage, faster deployments...
Product updates
Gitlab Support
Do you use Gitlab repositories? You can now deploy your application by using Qovery. Read more...
Persistent Storage
You can enjoy attaching storage to your application and keeping your data persisted. Read more...
Web Interface
The team is working hard to make the web interface live as soon as possible. We are looking for a pixel-perfect frontend developer to join us and help us to make it live faster :) We expect to release a beta version for July 2020.
Faster deployments 🚀
Before: deploying an application with a database could lead to waiting 20 minutes.
Now: deploying an application with a database take less than 3 minutes.
We aim to make it even faster in the coming weeks. Our goal is to deploy a complete application in less than a minute.
Feedback / Roadmap
Your feedback is welcome, they help improve our product, and we'll do our best to do them. Also, do not hesitate to vote for wanted features or submit your ideas.
Community
Hasura Con' 2020
Hasura is a turnkey engine that connects your micro-services and database to generate a real-time GraphQL API. That is super cool. Hasura and Qovery is a perfect match to deploy production-ready GraphQL service in just a few seconds. That's why the Hasura team invited us to show the world what we do.
Record coming soon - in the meantime, you can read this article to know how to deploy a full-stack application with Hasura, PostgreSQL, and Angular.
Passionate developer?
Do you like to share your knowledge and your passion for the code? We are looking for two technical writers for an ambitious new project. Interested? Contact us on Discord.
Resource highlights
- Tutorial: How to deploy a full-stack application (Hasura, PostgreSQL, Angular)
- Article: A month after switching from Slack to Discord in a tech startup
- Article: Network isolation in Kubernetes
- Article: Differences between Heroku and Qovery
- Tutorial: Creating a blazing fast REST API in Rust (Part 1/2)
- Tutorial: How to deploy a Docker container
- Tutorial: How to deploy Django with PostgreSQL (Python framework)
What's next?
- Web interface: The first release of the Qovery web interface is expected for next month (July).
- Qovery Business: We plan to launch an alpha version of Qovery Business - To deploy Qovery on your Cloud account.
- Feature: Redis Support
- Feature: Memcached Support
- Feature: Support Monorepository
Vote for the subsequent development
As always, we would love to get your feedback on these updates.
That's all folks - The Qovery Team
.svg)
.svg)
.svg)
Suggested articles
Scaling your deployments to zero is only half the battle. If your cluster autoscaler does not aggressively bin-pack and terminate the underlying worker nodes, you are still paying for idle metal. True environment sleeping requires tight integration between your ingress layer and your node provisioner to actually realize FinOps savings.
The biggest mistake enterprises make when evaluating Kubernetes management platforms is confusing infrastructure provisioning with Day-2 operations. Tools like Terraform or kOps are excellent for spinning up the underlying EC2 instances and networking, but they do absolutely nothing to prevent configuration drift, automate certificate rotation, or right-size your idle workloads once the cluster is actually running.
For years, Red Hat OpenShift has been the safe choice for heavily regulated, on-premise environments. It operates as a secure fortress. But in the public cloud, that fortress acts as an expensive prison. Paying proprietary per-core licensing fees on top of your standard AWS or GCP compute bill is a redundant "middleware tax." Escaping OpenShift requires decoupling your infrastructure from your developer experience by running standard, vanilla Kubernetes paired with an agentic control plane.
Agentic Kubernetes resource reclamation is the practice of using an autonomous control plane to continuously identify, suspend, and delete idle infrastructure across a multi-cloud Kubernetes fleet. It replaces manual cleanup and reactive autoscaling with intent-based policies that act on business state, eliminating the configuration drift and cloud waste typical of unmanaged fleets.
Kubernetes focuses on container orchestration, but the reality on the ground is far less forgiving. Provisioning a single cluster is a trivial Day-1 exercise. The true operational nightmare begins on Day 2. Teams that treat multi-cloud fleets like isolated pets inevitably face crushing YAML configuration drift, runaway AWS bills, and severe scaling bottlenecks.
Rancher solved the Day-1 problem of launching clusters across disparate bare-metal environments. But in 2026, launching clusters is no longer the bottleneck. The real failure point is Day-2: managing the operational chaos, security patching, and configuration drift on top of them. Rancher is a heavy, ops-focused fleet manager that completely ignores the application developer. If your goal is developer velocity and automated FinOps, you must graduate from basic fleet management to an intent-based Kubernetes Management Platform like Qovery.
The shift from AI copilots to autonomous agents is redefining infrastructure requirements. Discover how to build secure, stateful, and compliant Agentic AI systems using Kubernetes, sandboxing, and observability while meeting EU AI Act standards
.webp)