AI on your work computer. Accessible from your phone.

The Conduit bridge runs on each person's computer. It connects the app to the AI programs configured there. Employees can send files from their phone and resume conversations later. Depending on the AI program and its permissions, the AI can read and edit files and run commands.

Voice is available too. With local speech models, the computer processes recordings and text for read-aloud locally. Using the device's own dictation instead may send recordings to its speech recognition provider.

The computer must be switched on and reachable. Your IT team should define what the AI is allowed to do before employees use it.

Encrypted connection. Chat content, files, voice recordings and AI results are end-to-end encrypted between the app and the bridge. Comms Connect and Cloudflare do not receive the keys. This encryption protects that connection. A configured cloud AI provider receives the content the bridge sends to it for processing.

Content on your own computers. The bridge stores chat histories, attachments and activity records locally. The bridge does not encrypt its local database. Disk encryption and secure user accounts are therefore part of setting up the workplace. AI programs may also keep their own histories; deleting a chat in Conduit does not delete those records.

Open-source bridge. The bridge's source code is public. Your IT team can inspect the local component and how it works: Conduit bridge on GitHub.

With Ollama running on the employee's computer, AI requests and their processing stay on that computer. No cloud AI provider is required. In Conduit, Ollama provides text answers; this integration cannot edit files or run commands.

Local AI does not make the entire Conduit installation cloud-free. The app interface, sign-in and connection still use external services. These process account and connection data, such as email addresses, IP addresses and connection times.

Bridge updates are signed and installed automatically by default. Automatic updates can be switched off.

Since bridge version 3.0.4, your IT team can limit AI permissions, disable individual AI programs and control updates more precisely. Updates can be set to notification-only mode, capped at a version or restricted to maintenance windows. A version cap does not downgrade an already installed newer version. Retention periods for local chats, activity records and attachments are also configurable. Running the installer again preserves the business settings.

The default for personal use gives AI agents full access within the computer user's permissions. A paired device can therefore initiate extensive actions on that computer. The user can change the local settings. They do not replace centrally enforced company policies; rules that users cannot change require the relevant AI program's management features, where available.

• Each person needs their own computer with the bridge installed on macOS, Windows or Linux, and a device paired with it.
• For cloud AI: individual AI accounts suitable for business use, or company API keys. Your business chooses the provider and enters into its own contract. Accounts are not shared between employees.
• For local AI: Ollama and a local model on the computer.
• IT policies covering device access, AI permissions, permitted data and the handling of local histories.

Conduit does not include an AI subscription. For Claude Code, access options include individual Team or Enterprise credentials, company API keys or your own credentials for Amazon Bedrock, Google Vertex AI or Microsoft Foundry. Comms Connect recommends company accounts for OpenAI Codex. This recommendation comes from Comms Connect and makes no statement about OpenAI requirements. The chosen provider's terms also apply.

Conduit currently has no single sign-on, central admin console, organisation structure or role model. Devices and bridges are paired per person. Users can delete the local activity record; it is not a tamper-evident compliance log.

The app interface is loaded from the server at every launch. Businesses cannot pin its version. End-to-end encryption relies on the integrity of that interface and the devices involved. There has been no external penetration test or security certification. All Cloudflare tunnels are operated within one Comms Connect account. The tunnel infrastructure has no SLA.

Your IT team can request a security concept and rollout guide as PDFs free of charge to assess and set up Conduit independently. Send questions about Conduit to hi@tryconduit.de.

Request the security concept and rollout guide

Contact: hi@tryconduit.de Conduit: tryconduit.de