> **Can't find what you're looking for?** Use `search_docs` on the docs MCP server at `https://accounts.tempo.xyz/api/mcp` to find what you need.

# Bring Your Auth

Bring your own authentication and signing infrastructure, then expose it to app code through a Tempo Accounts SDK adapter.

This path is for teams that already have user identity, compliance, custody, or signing requirements that should remain outside Tempo Wallet.

## Common patterns

| Pattern                                             | Use it when                                             |
| --------------------------------------------------- | ------------------------------------------------------- |
| [Privy](/docs/enterprise/bring-your-auth/privy)     | Privy owns app auth and wallet state.                   |
| [AWS KMS](/docs/enterprise/bring-your-auth/aws-kms) | Keys live in AWS-controlled infrastructure.             |
| [Turnkey](/docs/enterprise/bring-your-auth/turnkey) | Turnkey owns signer infrastructure.                     |
| [Custom](/docs/enterprise/bring-your-auth/custom)   | Your own service owns auth, signing, or wallet hosting. |

## Integration shape

```mermaid
flowchart LR
    App["App"]
    SDK["Tempo Accounts SDK"]
    Adapter["Custom adapter"]
    Auth["Auth/session system"]
    Signer["Signer infrastructure"]
    Tempo["Tempo"]

    App --> SDK --> Adapter
    Adapter --> Auth
    Adapter --> Signer
    Signer --> Tempo
```

## Human Pass Needed

This section needs enterprise positioning and security review before publishing as final guidance.

## Next Steps

* [Custom adapter](/docs/adapters/custom)
* [Hosted Universal Wallets](/docs/enterprise/hosted-universal-wallets)
* [Spend Permissions](/docs/guides/spend-permissions)