Composio key modes explained: BYO, dedicated project, and shared
Behind every integration is a Composio key, and HIIE resolves which key your account uses through a tiered model. Understanding the three modes helps you know how isolated your connections are.
The three key modes
HIIE resolves your Composio key in order of preference:
- BYO (bring your own) — your own Composio key, stored in the Credentials vault. Connections run under your own Composio organization. This is the highest-isolation, most private option.
- Dedicated project — a Composio project minted per account from HIIE's organization key. This gives your account project-level isolation, and the minted key is encrypted at rest.
- Shared — a managed fallback key shared across accounts, isolated per user by always passing your user ID. This isolation is enforced in code rather than cryptographically.
How a mode is chosen
HIIE uses your BYO key if you've added one; otherwise it uses a dedicated project key if your account has one; otherwise it falls back to the shared managed key. In every case, your user ID scopes the connections so they stay separated from other users'.
Key safety across all modes
No resolved key — BYO, dedicated, or shared — is ever sent to your browser or logged. HIIE only ever shows a masked hint for BYO and dedicated-project keys.
Choosing a mode
If you want maximum privacy and your integrations to live in your own Composio org, add your own key in the Credentials vault. Otherwise, a dedicated project key gives strong per-account isolation without you managing a key. You can check your current mode in the Environment tab.