Environment Variables and Secrets
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? Separate configuration from source code and store secrets in controlled, rotatable, environment-specific systems.
What You Will Be Able to Decide
- Explain environment variables and secrets in product and business terms.
- Apply this decision: Separate configuration from source code and store secrets in controlled, rotatable, environment-specific systems.
- Recognise this material risk: credentials leak through source history, logs, shared files, or copied production configuration.
- Use this review: Ask a second operator to deploy the dashboard, find a failed request in logs, and roll back a deliberately broken release.
A founder has a working application and needs a proportionate way to run, monitor, and recover it. This lesson gives you a concrete question to take into a build brief, proposal review, or product decision.
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? The course example is A small SaaS dashboard with a public marketing site; use it to decide what evidence would justify the choice before a builder implements it.
What Does Environment Variables and Secrets Mean for Your Product?
A founder has a working application and needs a proportionate way to run, monitor, and recover it.
Use the illustrative service for this course (A small SaaS dashboard with a public marketing site) to make the choice concrete. Can the team operate this service after launch with the people, access, budget, and recovery time it actually has?
Technical term
Environment Variables and Secrets
Environment variables provide runtime configuration; secrets are sensitive values such as credentials and signing keys that require stricter handling.
How Should a Founder Use Environment Variables and Secrets?
For a small saas dashboard with a public marketing site, ask what would happen if credentials leak through source history, logs, shared files, or copied production configuration.
For this decision, the useful standard is that the team knows where the product runs, who operates it, and how service is restored after failure.
- Decision: Separate configuration from source code and store secrets in controlled, rotatable, environment-specific systems.
- Evidence to request: show that the team knows where the product runs, who operates it, and how service is restored after failure.
- Owner: name who will respond if credentials leak through source history, logs, shared files, or copied production configuration.
- Record the result in the deployment and operations plan.
- Practical review: Ask a second operator to deploy the dashboard, find a failed request in logs, and roll back a deliberately broken release.
How Do You Choose an Approach to Environment Variables and Secrets?
Can the team operate this service after launch with the people, access, budget, and recovery time it actually has? Separate configuration from source code and store secrets in controlled, rotatable, environment-specific systems.
The risk is that credentials leak through source history, logs, shared files, or copied production configuration. Compare a simpler option with the proposed one, including who will operate either choice.
- Describe the user or business outcome that must be protected.
- Identify the most credible failure and its consequence.
- Compare the simplest adequate approach with one realistic alternative.
- Set a review point for when the decision may need to change.
What Evidence Should You Accept for Environment Variables and Secrets?
What Warning Signs Should You Look For?
- The proposal does not address this risk: credentials leak through source history, logs, shared files, or copied production configuration.
- Nobody can show whether the team knows where the product runs, who operates it, and how service is restored after failure.
- The decision has no named owner or review point.
What Should You Ask a Consultant?
- What changes for the user if we choose this approach to environment variables and secrets?
- How have we reduced or accepted this risk: credentials leak through source history, logs, shared files, or copied production configuration.
- Can you demonstrate that the team knows where the product runs, who operates it, and how service is restored after failure?
- Who owns the result, and when will we reconsider it?
Key takeaway
Key Takeaway
Separate configuration from source code and store secrets in controlled, rotatable, environment-specific systems. Ask for evidence against the specific risk: credentials leak through source history, logs, shared files, or copied production configuration.