Two model access paths
DPanel supports two ways to run model calls for an AI team. BYOK is the default path: the customer brings provider keys, owns the provider relationship, and DPanel does not charge for model usage.
DPanel Pack is the optional managed path. DPanel manages model access, meters every call, and charges prepaid credits with a transparent margin.
When Pack fits
Pack fits teams that want a clean SaaS-style setup: no provider key management, prepaid credits, pay-for-what-you-use billing, and usage visibility by worker, task, instance, and channel.
The model keys are managed by DPanel and are never placed inside the customer instance.
When BYOK fits
BYOK fits teams that already have provider accounts, negotiated model rates, compliance requirements, or direct procurement rules for model usage.
DPanel still manages orchestration, approvals, task state, handoff, guardrails, and usage visibility around BYOK calls. It just does not bill the customer for those model calls.
What Pack is not
Pack is not unlimited model usage and it is not free compute. It is a managed, metered model-access path for DPanel AI-team workflows.
DPanel manages orchestration and metered model access. It is not positioned as a resale layer for compute hosting.
Next step
Turn this concept into a visible workflow with teams, approvals, grounding, and handoff.
View Pack page