Agents work with systems behind your firewall.
Without opening a single inbound port.
Run one small bridge in your network. It only connects out to connic, so agents can work with your ERP, mail server and internal tools while your firewall stays closed to inbound traffic.
Your ERP, mail server and internal tools, in reach of your agents.
Take a wholesaler whose ERP, mail server and internal tools run on site. One bridge lets agents work with all three while the firewall stays shut.
When an article in the on-site ERP drops below its minimum stock, the agent drafts a purchase requisition for a buyer to release.
The agent reads orders from your own mail server, checks prices and stock in the ERP and confirms from the same address.
A sales rep asks whether a customer can order more this month. The agent checks the ERP and answers with the credit limit and open invoices.
Set it up with one command. Leave the firewall as it is.
Start the bridge on any machine that reaches your systems and the internet. It opens one outbound connection to connic and keeps it open, so nothing in your network accepts traffic from outside.
- No inbound ports, no public IP
- The bridge only dials out, so there is no inbound firewall rule to open or review.
- Only the systems you list
- Give the bridge an exact list of systems, and it blocks and logs every attempt to reach anything else. Without a list, it reaches whatever its network can.
- Encrypted in transit
- Traffic between the bridge and connic is encrypted.
One bridge per network, each with its own key.
Run a bridge at each site or cloud network, and a separate one for staging. The dashboard shows which ones are connected. A new token cuts off the old one, and the audit log records who changed it.
Your code reaches private hosts by name.
Tools reach a private host as <target>.cnc-bridge-<bridge_id>, and MCP servers name the bridge in the agent file. Connectors take it from their Connection, so you install no VPN client and write no network code.
- Connectors
- Kafka, SQS, PostgreSQL, email and S3 use the bridge of their Connection, picked under Network Access. Outbound webhooks pick one on the connector.
- tools/, middleware/, hooks/, guardrails/
- Any TCP connection from your code, with clients such as psycopg, httpx or aiokafka.
- MCP servers
- The bridge field on a server entry in the agent file.
version: "1.0"
name: stock-assistant
description: Answers stock and delivery questions in the trade portal
model: connic/glm-5.3
system_prompt: |
Answer stock and delivery questions with live ERP data.
tools:
- stock.stock_level
mcp_servers:
- name: erp
url: http://erp-mcp:8080/mcp
bridge: ${ERP_BRIDGE_ID}import os
import psycopg
from connic import bridge_host
def stock_level(sku: str) -> dict:
"""Available stock per warehouse, from the ERP database.
Args:
sku: Article number, for example A-1042
"""
host = bridge_host(os.environ["ERP_BRIDGE_ID"], "erp-db")
with psycopg.connect(
host=host, port=5432, dbname="erp", user="reader",
password=os.environ["ERP_DB_PASSWORD"],
) as conn:
rows = conn.execute(
"SELECT warehouse, on_hand - reserved"
" FROM stock WHERE sku = %s",
(sku,),
).fetchall()
return {"sku": sku, "available": dict(rows)}