Run your app with
cloud secrets.
No .env file.
Map each environment variable to an AWS SSM or Azure Key Vault path in envilder.json. One command resolves them and starts your app with the values in its environment.
Open source, with no server or SaaS in between: secrets stay in your cloud account. Need a file for a tool or CI? pull writes .env. Prefer code? SDKs for Node.js, Python and .NET.
❯ npm install -g envilderHow it works
Map once. Run it anywhere.
Map each variable once
envilder.json lists env var names and their secret paths, never the values. Pushing a secret adds its entry for you, or you can write the file by hand. Commit it and review changes in pull requests like any other code.
$ envilder --push --key=API_KEY --value=s3cret --secret-path=/my-app/prod/api-key
✓ Created envilder.json
$ envilder --push --key=DB_PASSWORD --value=pa55word --secret-path=/my-app/prod/db-password
✓ Added DB_PASSWORD to envilder.json{
"API_KEY": "/my-app/prod/api-key",
"DB_PASSWORD": "/my-app/prod/db-password"
}Run your app with exec
envilder exec resolves every mapped secret and starts your command with them in its environment. No .env file on disk, nothing to clean up, and the command never starts if a secret is missing.
$ envilder exec -- npm start
envilder: 2 secrets resolved (aws, profile=default) → npm …
> my-app@1.0.0 start
> node server.js
Listening on http://localhost:3000
$ ls -a
. .. envilder.json package.json server.jsOr load them in code
Runtime SDKs for Node.js, Python and .NET resolve the same map in-process at startup.
pip install envilderfrom envilder import Envilder, SecretProviderType
# One-liner: load secrets into os.environ
Envilder.load("envilder.json")
# Or resolve as a dict without injecting
secrets = Envilder.resolve_file("envilder.json")
# Fluent builder with provider override
secrets = (
Envilder.from_map_file("envilder.json")
.with_provider(SecretProviderType.AZURE)
.with_vault_url("https://my-vault.vault.azure.net")
.inject()
)dotnet add package Envilderusing Envilder;
var builder = WebApplication.CreateBuilder(args);
// Load secrets into IConfiguration
builder.Configuration.AddEnvilder("envilder.json");
// Register EnvilderClient in DI
builder.Services.AddEnvilder("envilder.json");
// --- Or standalone (no ASP.NET) ---
// One-liner: resolve + inject into Environment
Env.Load("envilder.json");
// Fluent builder with provider override
Env.FromMapFile("envilder.json")
.WithProvider(SecretProviderType.Azure)
.WithVaultUrl("https://my-vault.vault.azure.net")
.Inject();npm install @envilder/sdkimport { Envilder, SecretProviderType } from '@envilder/sdk';
// One-liner: resolve + inject into process.env
await Envilder.load('envilder.json');
// Or resolve as a Map without injecting
const secrets = await Envilder.resolveFile('envilder.json');
// Fluent builder with provider override
const override = await Envilder.fromMapFile('envilder.json')
.withProvider(SecretProviderType.Azure)
.withVaultUrl('https://my-vault.vault.azure.net')
.inject();Need a file? Use pull
Some tools expect a .env file, and pull writes one from the same map. Treat it as a secret. In GitHub Actions you usually need no file: the action exports the secrets to the later steps of the job.
$ envilder --map=envilder.json --envfile=.env
🪙 RESOLVING SECRETS
✓ DB_PASSWORD → ********word
✓ API_KEY → ********_key
✓ SECRET_TOKEN → ********oken
⭐ LEVEL CLEARED — 3/3 secrets loaded · .env written- uses: macalbert/envilder/github-action@v0
with:
map-file: envilder.jsonWhy Envilder?
Envilder is a resolution layer over the secret store you already run. It never stores secrets: the map file is the only thing it adds to your repo.
Secrets Stay Off Disk
exec and the SDKs put values straight into the process environment. No plaintext .env left in the project folder, in backups or in a container image.
No Server, No SaaS
Nothing to host or pay for. Envilder reads AWS SSM Parameter Store or Azure Key Vault directly with your own cloud credentials.
One Reviewed Map File
envilder.json is the single list of what each app needs, the same for local development, CI and production. Changes go through pull requests.
Native IAM and RBAC
Access is governed by AWS IAM or Azure RBAC, and CloudTrail or Azure Monitor can log it when configured. No extra auth layer.
Your cloud. Your choice.
Envilder works today with AWS SSM Parameter Store and Azure Key Vault. Choose the provider in envilder.json or with CLI flags.
AWS SSM Parameter Store
{
"$config": {
"provider": "aws",
"profile": "prod-account"
},
"DB_PASSWORD": "/my-app/prod/db-password",
"API_KEY": "/my-app/prod/api-key"
}$ envilder- ✔ Supports GetParameter with WithDecryption
- ✔ AWS Profile support for multi-account
- ✔ IAM policy-based access control
- ✔ CloudTrail access logging when configured
Azure Key Vault
{
"$config": {
"provider": "azure",
"vaultUrl": "https://my-vault.vault.azure.net"
},
"DB_PASSWORD": "my-app-prod-db-password",
"API_KEY": "my-app-prod-api-key"
}$ envilder --provider=azure --vault-url=https://my-vault.vault.azure.net --map=envilder.json --envfile=.env- ✔ Auto-normalizes secret names (slashes → hyphens)
- ✔ DefaultAzureCredential authentication
- ✔ Azure RBAC access control
- ✔ Azure Monitor access logging when configured
Need Google Cloud Secret Manager or AWS Secrets Manager? Both are on the roadmap, not available yet. View roadmap →
Frequently asked questions
What is Envilder?
Envilder is an open-source CLI, GitHub Action and set of runtime SDKs that resolves application secrets from AWS SSM Parameter Store or Azure Key Vault using one versioned JSON map file. It can run your command with those secrets in its environment, write a .env file when a tool needs one, or load them in-process.
Does Envilder store my secrets?
No. Values stay in AWS SSM Parameter Store or Azure Key Vault. envilder.json holds only variable names and secret paths, so it is safe to commit. There is no Envilder server or hosted service.
Does Envilder have an exec mode?
Yes. Since CLI v0.15.0, envilder exec -- <command> resolves the secrets in your map file and starts the command with them as environment variables, without writing a .env file. It works with AWS SSM Parameter Store and Azure Key Vault.
How is envilder exec different from a .env file?
exec resolves the secrets and passes them to your command as environment variables, so nothing is written to disk. It is fail-closed: if a secret is missing, empty or unreadable, the command does not start. The command and the processes it launches can still read the values; exec is not a sandbox.
Can I use it in CI/CD?
Yes. The GitHub Action exports the mapped secrets to the later steps of the job, runs one command with them, or writes a .env file when a tool needs one. The CLI (exec or pull) works in any CI runner that has cloud credentials.
Which secret stores are supported?
AWS SSM Parameter Store and Azure Key Vault. Google Cloud Secret Manager and AWS Secrets Manager are on the roadmap but not available yet.
How does it compare to dotenvx, Chamber or Doppler?
dotenvx encrypts .env files so they can be committed. Doppler is a hosted secrets platform. Chamber is a CLI for AWS secret stores. Envilder keeps values in the AWS SSM or Azure Key Vault you already use, adds one reviewed map file, and covers the CLI, CI and runtime SDKs with that same map.
Is it free?
Yes. Envilder is MIT-licensed. You only pay your cloud provider's usual costs for SSM Parameter Store or Key Vault.
Get started
Up and running in under a minute.
Prerequisites
- Node.js v22.12+
- Choose one cloud provider:
- AWS SSM: AWS credentials with ssm:GetParameter; add ssm:PutParameter to push secrets
- Azure Key Vault: Azure credentials with secret Get access; add Set access to push secrets
Install
Quick start
- Push a secret with npx envilder --push --key --value --secret-path: Envilder writes envilder.json for you
- Run npx envilder exec -- followed by your usual start command
- Your app starts with its secrets ✔
import os
from envilder import Envilder
Envilder.load("envilder.json")
# Secrets are now in os.environ
api_key = os.environ["API_KEY"]