A secret is fetched when the request leaves. It is never in the file.
A variable's value can be secret://vault/kv/data/prod#token. At the send, Sonda asks your secret manager, puts the value in, and forgets it — nothing in the workspace, nothing in the team store, nothing in an export. For teams without a manager, Sonda Secrets seals each value under a key of its own, wrapped for the people allowed to read it.
The providers
The reference travels. The value is fetched, used and forgotten.
A variable holds a reference — secret://provider/path#field — and the reference is what a project carries and what a colleague receives. The value is resolved when the request executes, several references at once, put into the request on this computer and cached in memory for a configurable while: five minutes by default.
Wherever the value would show, it is masked. It is never written to the workspace or the team store, and an export carries the reference alone. For a value with no manager to live in, Sonda Secrets keeps it in the store, sealed under a key of its own.
VariablesOne syntax, every protocol.
secret://provider/path#field works in an HTTP request, a GraphQL call, gRPC metadata, a WebSocket header, an SSE request, an MQTT password, a Socket.IO auth payload, an MCP header, an OAuth token fetch.
Beside it, a reference in each of them, and what one send leaves on screen.
The team's own vault, inside the store.
For a value that has no manager to live in, and must still never be readable from the bucket.
Stored
An administrator stores a value and chooses its readers. A request reaches it as secret://sonda/name.
Sealed
The value gets a fresh 32-byte key of its own and is sealed with AES-256-GCM.
Wrapped
The key is wrapped separately for each chosen reader and the administrator. The file is signed.
Resealed
A new value is sealed again, under a fresh key.