Bring your own keys
Why the platform asks you to connect your own accounts and credentials — and exactly where in the product you add them.
Why bring your own keys
The platform is built around a simple principle: you keep ownership of your accounts and your data. Instead of routing everything through a shared house account, your AI employee uses your own keys, so the work happens on infrastructure and services that already belong to you.
This also keeps you in control of cost. When a job runs against your provider — an AI model, a media service, a cloud database — it bills to your account at your rates. You see and control the spend directly, with no opaque markup in between.
Finally, it keeps you in control of scope. You grant exactly the access you want, no more, and you can revoke any credential at any time. Keys are encrypted at rest and delivered to the workroom only in the safest way for each type, as described in the "How your keys are stored" article.
Where to add your keys
When you create a workroom: the setup flow has a "Connect your tools" section for the services your AI employee should use, and a "Network access" section for reaching private servers or databases. This is the quickest way to get a new workroom productive from the start.
In Config → Secrets: this is where tenant-wide skill secrets live — keys shared by the AI capabilities your whole organisation uses. Add a key here once and the relevant skills can use it across your workrooms.
In Profile → Integrations: this is where your personal, per-user connections live — for example your git token or an OAuth login. These belong only to you and are not shared with the rest of your organisation.
What you stay in control of
Ownership: your accounts and the data they hold remain yours. The platform acts on your behalf using credentials you choose to share, never by absorbing your data into a shared pool.
Cost: because jobs bill to your own providers, you decide which services to enable and you carry the spend transparently.
Access: you grant a narrow scope and revoke it whenever you like. How safely each key is handled once connected — kept at our backend or injected only during a session — is covered in the "How your keys are stored" article, and the isolated environment those keys serve is explained in "How workrooms work".