Hosted
Versur-managed providers. Fastest path - covered by the platform default.
Blog
Product
Models you control
Three ways VERSUR agents run models: hosted providers, bring your own key (BYOK), or local models through VERSUR Bridge - so you choose speed, contract, or sovereignty.
June 16, 2026VERSUR · Product5 min read
BYOK
Your OpenAI, Anthropic, Gemini, or Azure contract. Versur orchestrates - you keep the key.
Local
VERSUR Bridge + Ollama or LM Studio. Inference stays on your machine.
Hosted
Use Versur-managed model providers. Simplest path - pick a model on an Agent block and run.
BYOK
Bring your own OpenAI, Anthropic, Gemini, or Azure key. Traffic rides your contract and region choices.
Local
VERSUR Bridge + Ollama or LM Studio. Prompt content for that run stays on your machine.
Pick per workflow
The same Agent block can use hosted, your keys, or Local / Auto - governance is a choice, not a fork of the product.
You are not buying access to a single model. You are buying infrastructure that runs design intelligence - on the providers, keys, and hardware your studio already uses.
VERSUR gives you three ways to run models in Agent blocks and workflows: hosted, bring your own key (BYOK), and local via Bridge. Same canvas. Different boundaries.
Hosted
The default. Steps run against Versur-managed provider accounts. Pick a cloud model on an Agent block - or Auto - and run. Fastest setup; covered by the platform path.
Customer content is not used to train models. Hosted traffic goes through provider API endpoints whose terms exclude training on API data.
Bring your own key
When your organization already has an OpenAI, Anthropic, Gemini, or Azure OpenAI agreement - use it. Supply the key once. AI traffic then flows on your own contracts and region choices. Versur-managed provider accounts stay out of that path.
OpenAIAnthropicGeminiAzure OpenAI
Local via Bridge
When operational knowledge must not leave your environment, run models on your own hardware. Install VERSUR Bridge on the workstation with the GPU. Link it once. Ollama or LM Studio models appear in Agent blocks as Local and Local / Auto.
VERSUR BridgeOllamaLM StudioLocalLocal / Auto
For those runs, prompt content stays in the customer environment. Leave Bridge on the office machine; open VERSUR from elsewhere when you need to - inference still happens on your hardware.
What does not change
- Agent blocks still plan, call tools, and follow the instructions you give them.
- Skills, manuals, loops, and Brain tools work the same across postures.
- You can standardize providers and models through workspace configuration.
How to choose
- Hosted - when speed and simplicity win.
- BYOK - when the provider contract and tenancy must stay yours.
- Local / Bridge - when the brief and operational knowledge must stay on your machine.
Available now
Hosted models, BYOK, and Bridge-backed local models are available in the workspace today. Pick the posture that matches the work - not a different product for each.
Integrations connect your stack. Bridge keeps local execution on your hardware. Models you control is how those choices show up on every Agent block.