/ SONDA · ENTERPRISE

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.

8 PROVIDERS RESOLVED AT SEND 5-MINUTE MEMORY CACHE A KEY PER SECRET

The providers

VaultHashiCorp Vault with a token or AppRole, a namespace, KV v1 and v2.
CloudsAWS Secrets Manager. Azure Key Vault. Google Secret Manager.
Services1Password Connect. Doppler. Infisical.
YoursAny HTTP endpoint that answers JSON.
Sondasecret://sonda/name — the team's own vault, in the store.
/ ONE VALUE, ONE SEND

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.

Variables
/ HOW IT RESOLVES

One 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.

# secret://provider/path#field — wherever a value goes HTTP Authorization: Bearer secret://vault/kv/data/prod#token GraphQL the same header, on the call gRPC metadata authorization: secret://vault/kv/data/prod#token WebSocket X-Api-Key: secret://aws/prod/api#key SSE X-Api-Key: secret://aws/prod/api#key MQTT password secret://vault/kv/data/broker#password Socket.IO auth { "token": "secret://sonda/socket-token" } MCP Authorization: Bearer secret://op/Engineering/MCP OAuth client secret secret://azure/payments-oauth # one send GET https://api.example.com/orders 200 142 ms Authorization: Bearer •••••••• # masked wherever it shows 1 reference · vault · in memory for the cache window, 5 min # the project keeps the reference — never the value
At send onlyResolved when the request executes, several references at once. Never written to the workspace or the team store.
In memoryCached for a configurable while — five minutes by default — and cleared by hand with Clear cached secrets.
MaskedA resolved value is masked wherever it would show. The reference, not the value, is what a project carries and what a colleague receives.
Shared managersThe owner can publish a manager's address and method to the organization's catalog, so every division resolves against the same Vault without anyone typing it twice.
/ SONDA SECRETS

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.

Never shownThe window never receives the plaintext; it is put into the request on this computer at the send and nowhere else. Access to the repository alone decrypts nothing.
Logged"Uses a team secret" is an activity trigger administrators can be mailed about, batched over five minutes.
/ LOCKFLARE SONDA

Every secret manager, in the free edition.

Secrets, listed →