The plain flow
Choose a connected provider key, choose the instance that should use it, tick consent, and apply the setting. After that, the selected instance runs that provider directly on the customer key.
BYOK means DPanel can show usage and keep orchestration visible, but DPanel does not charge the customer for model usage on that provider path.
The trust model
The key goes into the user-owned instance only. It is not shared with another customer, and it is not treated as a DPanel-managed Pack key.
Consent is required before applying a key to an instance. The user can change the key, remove it, or move a worker back to another provider path at any time.
What DPanel still manages
DPanel remains the control plane for teams, workers, tasks, approvals, handoff, guardrails, and usage visibility.
The provider account and model spend stay with the customer. DPanel should show the usage trail so operators can understand which worker, task, instance, channel, provider, and model caused the work.
Next step
Turn this concept into a visible workflow with teams, approvals, grounding, and handoff.
Open the BYOK guide