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
Kubernetes success is determined by Day 2 execution, not Day 1 deployment. While migration is a bounded project, maintenance is an infinite loop that often consumes 40% of senior engineering capacity. To protect margins and velocity, enterprises must transition from manual toil to agentic automation that handles scaling, security, and cost.
Day-0 is planning, Day-1 is deployment, and Day-2 is the infinite lifecycle of maintenance. While Day-0/1 are foundational, Day-2 is where enterprise operational debt accumulates. At fleet scale (1,000+ clusters), managing these differences manually is impossible, requiring agentic automation to maintain stability and eliminate toil.
A multi-cluster Kubernetes architecture distributes application workloads across geographically separated clusters rather than a single environment. This strategy strictly isolates failure domains, ensures regional data compliance, and guarantees global high availability, but demands centralized Day-2 control to prevent exponential cloud costs and operational sprawl.
Stop overpaying for Kubernetes observability. Learn how in-cluster monitoring and AI-driven troubleshooting with Qovery Observe can eliminate APM ingestion fees, reduce SRE bottlenecks, and make your cloud costs predictable.
Kubernetes multi-cluster management is the Day-2 operational practice of orchestrating applications, security, and configurations across geographically distributed clusters. Because native Kubernetes was designed for single-cluster orchestration, enterprise platform teams must implement a centralized control plane to prevent configuration drift and manage a global fleet without scaling manual toil.
Achieving zero-downtime deployments on Kubernetes requires more than running multiple pods. It demands a standardized architecture utilizing Pod Disruption Budgets (PDBs), precise liveness and readiness probes, pod anti-affinity, and graceful termination handling. At an enterprise scale, these configurations must be enforced via a centralized control plane to prevent catastrophic configuration drift.
.webp)