Apps · 4 min read · Oct 25, 2026
Secrets
Passwords, keys and settings your app needs. Values live in a secure store — never in the code, the database or logs.
Declare them
List each secret by name in onvoi.yaml secrets: and in a .env.example with a comment above each one. Onvoi reads both: every name shows up in the app’s Secrets tab, empty ones with Add value.
.env.example
# The free public weather service WEATHER_API=https://api.weather.example # Your own Stripe key STRIPE_KEY=
Secrets belong to the workspace
A secret is saved once for the workspace and given to an app under the name it reads. Only workspace admins add secrets; others can connect ones an admin already added. Previews don’t get production secrets unless you choose.
Shared values vs. each installer’s own
When other teams install your app, they get the names, never your values. Two kinds:
- Shared — a value that belongs to the code itself, like a free public endpoint. Mark it shared (Secrets tab → Share with installers, or
shared: true, default: "…"in onvoi.yaml) and every installer gets it already set. - Each installer’s own — like an API key. It shows up empty for them to fill in.
Never sharedNames that look like a key, token, password or credential can never be shared — Onvoi refuses them.
You may not need a model key
For AI features use onvoi.ai.chat() — see the App SDK reference. No OpenAI or Anthropic key to collect from anyone.