Introducing VERSUR Bridge

Every time an agent runs against a third-party model, some of your organization's most valuable intellectual property has to leave your environment to be executed. Whether or not that data is used for model training depends on the provider and your agreement - but the operational knowledge still leaves.

We built VERSUR Bridge to solve that problem.

Your advantage is how you operate

Your competitive advantage is not just your data. It is how your organization operates - the workflows you have refined over years, the decisions your experts make, and the processes that differentiate your business. That is the knowledge you should own.

Bridge is the desktop companion that makes that ownership practical: local LLMs for Agent blocks, MCP connectors for the design apps already on your machine, and one link from Settings → Connectors - no API keys pasted into every Agent block.

Not a tunnel. A companion.

Bridge does not need to sit on the same computer as the browser where you open VERSUR. Install it on the workstation that has the GPU and the design apps - usually the machine at the office. Link it once from Settings → Connectors. Then leave it running.

From there you can open VERSUR anywhere: a cafe, an airport, a client meeting, your laptop on the train. Agent blocks still call the local models and desktop connectors on that office machine. Bridge reaches VERSUR from your machine - nothing opens inbound, no port forwarding, no exposing the LAN.

Local models in Agent blocks

Install Ollama or LM Studio. Bridge detects what is available and reports it to VERSUR. On an Agent block, open the model list: you get Local models when Bridge is connected, plus Local / Auto when you want VERSUR to pick a local model that fits the task - the same idea as cloud Auto.

The Agent still plans, calls tools, and follows the instructions you give it. The thinking just happens on your GPU instead of a hosted provider - so the context that shapes those calls never has to leave for a third-party model. Bridge is included on every plan with no hosted AI markup on those local runs.

Desktop connectors for design apps

Bridge Setup installs and prepares MCP connectors so agents can reach apps already on the machine. Link Bridge once in Connectors, then connect each app you use. VERSUR registers the connection for the workspace.

• Rhino MCP - drive Rhino (and Grasshopper via that path) from Agent tools. Restart Rhino after install, then run MCPStart each session.
• Revit MCP - for Revit 2027 and later.
• Blender, Maya, Bluebeam, Adobe Illustrator MCP - same Connectors flow.

How to connect

• Download and run VERSUR Bridge Setup on the computer where the models and apps live - typically your office workstation, not necessarily the laptop you browse VERSUR on.
• In VERSUR (from any device), open Settings → Connectors and Link Bridge - enter the pairing code from the desktop app.
• Connect each desktop app you need. For Rhino, restart Rhino and run MCPStart when you start a session.
• Keep Bridge running on that workstation - local models and desktop tools stay available wherever you open VERSUR.

Available now

Bridge is available with VERSUR today. Install it, link from Connectors, pick a Local model on an Agent - and keep the operational knowledge that differentiates your practice under your control.

Brain is where the practice remembers. Design agents are how the practice designs. Bridge is how that work stays yours when it needs to.

Integrations · Models · Integrations · VERSUR Agent · Design Agents · Brain · Changelog