# Connections: your apps, no keys shared

> Your apps and APIs. Agents never see a key.

Source: https://www.hexelstudio.com/connections

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

## 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 store:** Envelope encryption in Vault, AWS KMS or Azure Key Vault.
- **FIPS 140-3 build:** For teams that need it.
- **Kill switch first:** Checked before any token is released.
- **Hosted Connect pages:** People connect their accounts without you building a screen.
- **Background refresh:** Tokens renew on their own.

## Where Connections sits

Orbit (for people) and your own agents (built with the SDK) sit on Titan: identity, policy, approvals, ledger, kill switch. Under Titan: Connections, Atlas, Memory, Router, Sandboxes, Harness, Routines, Skills, Waypoint. Everything runs on your ground (cloud, edge, on-prem, air-gapped), with Identity for sign-in.

## Runs where you run

From the public cloud to networks sealed from the world.

- **Cloud:** Live in minutes.
- **Edge:** Beside the work.
- **On-prem:** Your servers. Your walls.
- **Air-gapped:** Nothing gets out.

Built in: 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.

## Goes well with Connections

- [Titan](https://www.hexelstudio.com/titan.md): Control for every agent.
- [Identity](https://www.hexelstudio.com/identity.md): Sign-in for your teams and apps.
- [Sandboxes](https://www.hexelstudio.com/sandboxes.md): A sealed computer for every run.

---
Hexel Studio · https://www.hexelstudio.com · Index for agents: https://www.hexelstudio.com/llms.txt
