BYOK

Your keys, your costs, your control

DeckCrew uses your own OpenAI and Claude keys. Billing stays with your provider, and workspace-scoped credentials are managed securely so each team keeps clear ownership and separation.

Request beta access See features

1. Connect provider keys

Add your OpenAI and Claude credentials so model usage is billed and controlled in your own provider accounts.

2. Assign by agent role

Map keys to specific agents instead of reusing one broad credential across all workflows.

3. Operate with visibility

Run with clear role boundaries, action logs, and predictable key ownership as your agent setup grows.

Area Without BYOK BYOK with DeckCrew
Credential ownership Often shared through the platform account. Keys remain in your provider-owned accounts.
Billing visibility Usage is harder to reconcile by team role. Spend stays visible where your finance team already looks.
Access pattern One key can quietly become global. Keys can be split per agent role and environment.

Practical guide: BYOK for AI Agents: OpenAI and Claude Keys

BYOK FAQ

BYOK questions

What does BYOK mean?

Bring Your Own Key. You connect your own OpenAI or Claude API keys. Model costs are billed by your provider, not by DeckCrew. You keep full control.

Can different agents use different keys?

Yes. You can map keys by role — your support agent can use one provider while your dev agent uses another. No shared credentials.

Is BYOK required?

Yes. DeckCrew is BYOK-only by design. This keeps provider billing transparent and prevents vendor lock-in on model access.

Does BYOK affect security?

It improves ownership and billing clarity. Your model billing stays with your provider, while DeckCrew stores workspace-scoped secret references securely so each workspace can use the right credentials.

Run DeckCrew with provider access your team controls

Request beta access See features
  • Guided onboarding included
  • Your own provider keys
  • No commitment required