Your apps, connected. No agent sees a key.
Agents use 63 apps and APIs. The secret stays with Connections, never with the agent.

Post the weekly summary to #support
- Kill switch checked
- Signed Titan grant verified
- Token released once
Every app. No shared keys.
Connect once. Agents get a short-lived token per action, never the secret.
63 apps and APIs.
Connected once, used by any agent you allow.
Every way in.
However the app expects to be signed in to.
People consent first.
Personal connections widen only when their owner says yes.
The details.
- Your key storeEnvelope encryption in Vault, AWS KMS or Azure Key Vault.
- FIPS 140-3 buildFor teams that need it.
- Kill switch firstChecked before any token is released.
- Hosted Connect pagesPeople connect their accounts without you building a screen.
- Background refreshTokens renew on their own.
Where Connections sits.
One stack, from the agent to the ground it runs on.
Runs where you run.
From the public cloud to networks sealed from the world.
01CloudLive in minutes.
02EdgeBeside the work.
03On-premYour servers. Your walls.
04Air-gappedNothing gets out.
- Keys stay in your vault
- Kill switch checked first
- FIPS 140-3 build
- Default deny
Questions.
Does the agent ever see the token?
No. A short-lived token is released once per signed Titan grant, after the kill switch is checked.
Where are secrets kept?
Encrypted with envelope encryption in your Vault, AWS KMS or Azure Key Vault. A FIPS 140-3 build is available.
Which sign-in methods are supported?
OAuth 2 with PKCE, API keys, mTLS, service accounts and MCP OAuth.
Can people connect their own accounts?
Yes. Personal connections belong to their owner, who must consent before access widens.



