Secrets
Use production secrets without committing them to your repo.
Reference credentials with secret:// values and let Adios resolve them for the build or runtime path that needs them.
The hook
Why developers care
Developers often start with .env files, then accidentally copy real keys into source, deployment manifests, screenshots, or CI logs.
How Adios handles it
- 1Create or import the secret in Adios.
- 2Reference it in adios.yaml with secret://NAME.
- 3Deploy without putting raw values in your repository.
What you get
Platform pieces that make this work.
secret:// references in runtime env config
CLI and workspace secret management
Build-time and runtime secret paths
Works with app and workflow manifests
Build path
Wire a database URL without exposing it.
Set DATABASE_URL as an Adios secret, reference it from adios.yaml, and deploy the app without writing the raw connection string into Git.
Deploy your first app on Adios.
Start with this feature, then add the rest of the platform as your app needs it.
Keep exploring
AI Coding Workspaces
Use the Adios agent inside a source-backed workspace, then inspect, edit, preview, commit, and deploy the code it creates.
Adios Deployments
Use adios.yaml and the Adios control plane to build, start, health-check, and promote app runtimes.
Managed App Hosting
Run long-lived app processes for common runtimes while Adios handles routing, logs, health, regions, and deploy state.