Environment variables and Secrets - The Future of Qovery - Week #6
This series will reveal all the changes and features you will get in the next major release of Qovery. Let's go!
Read the previous article: Qovery goes beyond app deployment - The Future of Qovery - Week #5.
Environment variables.
You have a NodeJS app that needs a PostgreSQL database - the good practice to connect your app to the database is to use environment variables to get the host, the port, and the credentials.
With the next release of the web interface, managing environment variables will be easier than before.
The same system of "scope" will remain - meaning you will still be able to set environment variables for many applications if you need it. Four scopes exist:
- BUILT_IN: Automatically generated variables based on your configuration (e.g., requested databases) propagated to all projects, environments, and applications.
- PROJECT: Variables at the project level are shared across all environments and all applications of the project.
- ENVIRONMENT: Variables at the environment level are shared across all project applications in one given environment.
- APPLICATION: Variables available for one application in a single environment
Secrets
Now let's say that your app needs to use Stripe to bill your user. You want to keep this secret secure and immutable from any change. This is why we introduce Secret Management. Secrets are encrypted and can't be revealed and modified once they are set.
Secrets can also be scoped, overridden, and aliased.
Qovery takes care of injecting your environment variables and secrets during the build time, deployment, and runtime.
Conclusion
We spent some time improving the UX to manage environment variables - we also considered adding the Secret Management feature to avoid using sensitive data inside your app. My team and I are excited to release our next major version of Qovery. If you are interested in joining the beta in early June, let me know by contacting us on Discord.
--
See you next week -- same hour, same place 👋
Romaric from Qovery -- We are hiring
.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.
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.
Stop fighting cluster sprawl. Learn why traditional scripting and GitOps fail at scale, and discover how to achieve fleet-wide consistency without the complexity of Kubernetes Federation.
Looking to automate your Kubernetes environment in 2026? Discover the top automation tools, their weaknesses, and why scaling your infrastructure requires a unified management platform.
As the AI race shifts from hardware acquisition to GPU utilization, success is now an orchestration problem. Learn how to bridge the 84% capacity gap, eliminate "ghost" expenses, and leverage AI infrastructure copilots to maximize ROI in 2026.
.webp)