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
Static delivery pipelines are becoming a bottleneck. The best CI/CD tools for Kubernetes are those that move beyond simple code builds to provide total environment orchestration and developer self-service.
The Broadcom acquisition of VMware has sent shockwaves through the enterprise world, with many organizations facing license cost increases of 2x to 5x. If you are looking to escape rising TCO and rigid subscription bundles, these are the top vSphere alternatives for a modern hybrid cloud.
Is the "Heroku Tax" draining your budget? Compare Heroku vs. Kubernetes in 2026. Learn how to solve complex orchestration challenges, like queue-based autoscaling and microservice sprawl, without the DevOps toil.
Is the EKS operational burden outweighing its benefits? Learn how to migrate from EKS to ECS, the technical trade-offs of AWS-native orchestration, and how to get ECS-level simplicity without losing Kubernetes power.
Is the "Kubernetes Tax" killing your team’s velocity? Compare Docker vs. Kubernetes in 2026 and discover how to get production-grade orchestration with the "Git Push" simplicity of Docker, without the operational toil.
Discover how Qovery bridges the gap between developers and infrastructure with a "security by design" approach. From federated identities and unique encryption keys to real-time audit logs and SOC2 Type 2 certification - see how we protect your data while eliminating vendor lock-in.
.webp)