Choose its intelligence
Run on your provider account
Keep model usage on the provider relationship your organization already controls.
Bring your own provider key; it is stored write-only and envelope-encrypted.
What this changes for your team.
Organization administrators can add a provider key without making its plaintext readable again through the product API. Yekar.AI encrypts it under an organization data key, itself wrapped by the deployment master key, and decrypts it only when the provider call needs it.
How it works in practice.
- 01
An organization administrator enters the key for a supported provider.
- 02
The API stores encrypted material and returns only non-secret status or hints.
- 03
A model request resolves and decrypts the matching key inside the execution path.
What you can plan around.
The behaviour you can design against, stated concretely.
Provider-key read responses never return the stored plaintext.
Envelope encryption separates per-organization data keys from the master-wrapped root.
Production has no environment-variable fallback for a missing organization provider key.
Bring one real process
See how Yekar.AI fits the way you work.
Start with a job your team already owns, plus the tools and decisions around it.
Talk to us