1. Overview
  2. Enterprise Deployment & Security
  3. BYOK (Bring Your Own Key)

BYOK (Bring Your Own Key)

Overview

Peridot supports Bring Your Own Key (BYOK) for all model providers.

This ensures that your organization maintains full control over model access, credentials, and usage.

Why BYOK Matters

Without BYOK:

  • Model access is shared

  • Credentials may be exposed

  • Usage is harder to audit

  • Compliance risk increases

With BYOK:

  • You control all API keys

  • Usage is tied to your accounts

  • Access can be restricted and audited

How BYOK Works

  • API keys are stored in your environment

  • Peridot uses your credentials for model access

  • No shared keys are used

Supported Providers

  • OpenAI

  • Anthropic

  • Google

  • Azure OpenAI

In Production

  • Keys are securely stored and rotated

  • Access is controlled via policies

  • Usage is fully auditable

Best Practices

  • Rotate keys regularly

  • Scope access by environment

  • Restrict usage to approved systems

Next Steps

Was this article helpful?