Digital Twin Pro answers on-device by default. When you want a frontier cloud model for a specific task, you can connect your own provider account — Claude, GPT, or Gemini — using that provider's API key. This page explains exactly what that means for your data.
What BYOK actually is
BYOK here means bring your own provider API key: the credential from your own Anthropic, OpenAI, or Google account. It gives the appliance permission to send a task to that provider under your account, your billing, and your provider settings. It is an authentication credential — not an encryption key, and it does not make your prompts invisible to the provider.
What leaves the appliance, plainly
When you route a task to an external model, the prompt and any attached content for that task leave the appliance and are processed by the provider under the provider's terms and retention policies. Transport is encrypted in transit (HTTPS), but the provider must read the content to answer it. Everything you don't route stays local.
Setting it up
Step 1 — Get a key from your provider. Create an API key in your Anthropic, OpenAI, or Google account console.
Step 2 — Add it in the dashboard. Settings → External models → paste the key. Keys are stored on the appliance.
Step 3 — Choose when it's used. Nothing routes externally by default. You pick which tasks may use the external model, and the active provider is shown on every externally routed task.
Removing or rotating a key
Delete or replace the key anytime in the same settings panel; deletion takes effect immediately and the appliance returns to local-only answering.
Updated July 15, 2026.