Thriving 
TS One secret mapping for local dev, CI/CD, and runtime. Envilder resolves cloud secrets from your own vaults without SaaS middlemen, duplicated config, or .env drift.
https://envilder.com ↗ HEALTH ? 89 / Healthy
Thriving TS // readme
🗝️ Envilder ☁️
Why Envilder?
Your new developer joins the team. They need environment variables to run the app locally.
What happens next? Someone sends API keys over Slack. Someone else digs up a wiki page
with outdated credentials. Forty-five minutes later, their .env file is “probably correct”.
Envilder fixes this with one versioned mapping contract.
You create a JSON mapping between variable names and cloud secret paths. Envilder resolves them from AWS SSM or Azure Key Vault. The same mapping file works in local dev (CLI), CI/CD (GitHub Action), and application startup (runtime SDKs).
# Push a secret: it is stored in your cloud and mapped in envilder.json
npx envilder --key=API_KEY --value=s3cret --secret-path=/my-app/api-key
# Zero-config: uses envilder.json and .env by default
npx envilder
# Or with explicit paths
npx envilder --map=envilder.json --envfile=.env
# Or skip the file: run your app with the secrets in memory
npx envilder exec -- npm run dev
No SaaS middleman. One versioned mapping contract. Secrets stay in your cloud.
The problem
- Onboarding takes hours, not seconds. Every new developer needs someone to explain which…