Connector architecture
Provider Vault for BYOK AI Teams
BYOK must keep customer keys separated from dpanel.ai-managed Pack routing while preserving usage visibility and approvals.
Customer-owned keys
Keys belong to the customer account, not the runtime image or public client.
Model selection
Choose model path by task, team member, policy, and spend controls.
Usage evidence
Track usage by org, instance, task, provider, and model class.
FAQ
What is Provider Vault for BYOK AI Teams?
Plan dpanel.ai provider vault connectors for OpenAI, Anthropic, Gemini, OpenRouter, and customer-owned model keys.
How does this fit dpanel.ai AI TeamOps?
BYOK must keep customer keys separated from dpanel.ai-managed Pack routing while preserving usage visibility and approvals.
Does this replace the external tool?
No. dpanel.ai is designed to coordinate AI-team work around external tools, then write, sync, or hand off only through approved workflows.
Where does human control appear?
dpanel.ai uses approval-aware tasks, prepared external writes, visible sync jobs, and handoff packets before sensitive actions reach external systems.
How do operators start?
Design provider vault