GitOps-native secrets with schema validation. Define what you need in code, never worry about missing config again.
# Install and authenticate $ pip install vezor $ vezor login ✓ Authenticated successfully # Generate local .env from your schema $ vezor generate-env -e development ✓ Generated .env with 12 secrets # Validate before deploy $ vezor validate -e production ✓ All 12 required secrets present
You've got better things to do than wrestle with Vault or pay per secret.
vezor generate-env doneDefine your secrets in YAML. Commit to Git. Your schema becomes documentation that can't lie.
Catch missing secrets before deploy. PR fails if someone adds code that needs config that doesn't exist.
Define once, override per environment. Dev inherits from base, prod overrides what it needs.
Your secrets run in dedicated infrastructure. Not multi-tenant with row-level security—actual isolation.
Auto-generate passwords that flow to your database and app. No human ever sees the value.
Every read, write, and change logged. Know who accessed what and when—compliance ready.
Define what secrets your app needs. Vezor makes sure they exist.
version: 1 project: my-app base: database_url: type: connection_string required: true description: "Postgres connection" api_secret: type: password auto_generate: true length: 32 redis_url: type: url default: "redis://localhost:6379" environments: development: inherit: base production: inherit: base overrides: redis_url: required: true
New team member? The schema tells them exactly what config the app needs. No tribal knowledge required.
Connection strings, URLs, passwords—Vezor validates format before you deploy broken config.
Base config inherited everywhere. Override only what differs. One secret definition, not three billable items.
Need a random API key? Mark it auto_generate. Vezor creates it, stores it, injects it.
Unlimited secrets, unlimited projects, unlimited users. Pay for queries.
Get started in 30 seconds. No credit card required.