Product Update #36 - New app deployment flow 🔥
Check out our updated guide on how to deploy your first app with Qovery (video).
New Features
Deploy templates
You can deploy open-source projects like Strapi, Hasura, n8n, and a few others via our web console. Using templates is great to experiment with new products and try out Qovery. We'll continue to add more of them in the coming days.
Special note: Do you have an open-source project that you want to expose to our users? Contact-us.
Create an environment in one click
You can now create a staging or a dev environment directly from the web interface. Environments are convenient to develop features without breaking anything in your production environment. Remember: each git branch is an environment.
Improvements
- Delete project: finally, you can now delete a project directly from the web console.
Jobs
Feel free to let us know what you think by contacting us.
The Qovery team
.svg)
.svg)
.svg)
Suggested articles
In the 2026 regulatory landscape, manual audits are a liability. This guide explores using GitOps to generate DORA-compliant audit trails through IaC, drift detection, and automated segregation of duties. Discover how the Qovery management layer turns compliance into an architectural output, reducing manual overhead for CTOs and Senior Engineers.
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.
.webp)