Bring Your Own Key (BYOK)

DevSpeak supports Bring Your Own Key (BYOK) — a feature that lets you connect your own LLM API credentials to use custom models for translation.

Supported Providers

| Provider | Tier Requirement | Configuration |

| ----------------- | ---------------- | --------------------------- |

| OpenAI | All tiers | API key + optional base URL |

| Anthropic | All tiers | API key |

| Gemini | All tiers | API key |

| OpenAI-Compatible | All tiers | API key + custom endpoint |

Gemini is a BYOK-only provider: it is available when you connect your own key, and is not part of DevSpeak's own model selection.

How BYOK Works

1. Navigate to Settings → LLM Provider.

2. Select your provider from the dropdown.

3. Enter your API key (stored encrypted server-side).

4. Click Validate to test the connection.

5. Once validated, all translations will route through your chosen provider.

Tier Routing

BYOK is available on every subscription tier, including Free. It is always optional — it changes which model executes your translation, not whether you can translate at all.

  • Free: optional. Without it, translations use DevSpeak's models within an hourly limit.

  • Vibecoder: optional. Without it, translations use DevSpeak's models.
  • Developer: optional, and useful once you have used your monthly allowance.
  • Enterprise: optional. Without it, translations use DevSpeak's models.

    • Credential Security

  • API keys are encrypted at rest using AES-256.
  • Keys are never logged or exposed in API responses.
  • You can revoke credentials at any time from the settings panel.
  • Connection validation performs a lightweight test request to verify the key works.

    • Connection Statuses

    | Status | Meaning |

    | -------------- | --------------------------------------- |

    | active | Credentials validated and in use |

    | invalid | Last validation failed — check your key |

    | unconfigured | No custom provider set up |

    | validating | Connection test in progress |

    Troubleshooting

  • Invalid key error: Verify the key is correct and has not been revoked in the provider's dashboard.

  • Timeout during validation: The provider endpoint may be unreachable. Check the base URL and try again.
  • Unexpected model behavior: Ensure your provider plan includes access to the model you're targeting.