Skip to main content

BYOK

Keep the secrets and model traffic a self-managed deployment depends on inside your own boundary, rather than handing them to Cracken.

What you can bring​

  • Your own secret manager — store tool and integration credentials in your existing vault; Cracken references them instead of holding its own copy.
  • Bring-your-own-key (BYOK) — supply your own API keys for external commercial models, so model calls bill and authenticate through your accounts.
  • Self-hosted LLM endpoints — point Cracken at a model you host yourself, so prompts and responses never leave your network.

Why it matters​

With BYOK and self-hosted endpoints, credentials and prompts stay in-boundary: data and credentials remain local during testing, and only selected, redacted results leave your network. Connections are TLS-encrypted and storage is encrypted at rest.

BYOK is configured as part of a self-managed deployment. Contact sales@cracken.ai or your Cracken account team to set it up for your environment.

Next steps​

  • Deployment — Cracken Cloud, private cloud, on-premises, or air-gapped.
  • Models — choose which model an operation runs on.
  • Team — roles and access control for your tenant.