API key management for developers
API keys show up in two places: the third-party keys your app calls, and the automation keys your tools use to reach your secrets vault. Both need careful handling.
Application API keys belong in the vault
Stripe, OpenAI, and cloud credentials your app uses should be stored as encrypted secrets per environment — not hardcoded and not committed.
STRIPE_SECRET_KEY=sk_test_your_key_here
OPENAI_API_KEY=your_openai_key_hereAutomation keys for CLI and CI
EANVI API keys authenticate non-interactive access for the CLI and pipelines. Create them in settings, store them in your CI secret store, and revoke them when a pipeline is retired.
Rotation without folklore
When rotating a vendor key: create the new key at the provider, update the secret in EANVI, redeploy or pull, then revoke the old provider key. Version history helps if you need to roll back quickly.
Related resources
Try EANVI
Create a workspace, import a .env, and pull secrets from the CLI.