OT/IT Bridge
Vendor-Agnostic
99.9% Uptime

Sync Connect. Connect everything.

OT/IT integration. Production data flow for IT systems.

ProvidersSync ConnectConnectors

One layer. Every protocol.

Controllers deliver data via OPC UA, Modbus, S7. IT systems expect MQTT, REST, Kafka, InfluxDB. Sync Connect bridges both — configuration-based, no custom middleware, no vendor lock-in.

How it works.

Sync Connect is built around three concepts:

Providers

Connection to controllers, Modbus sensors, OPC UA servers. Each provider handles authentication, polling, and write-back for one physical or virtual source.

Connectors

Data output to MQTT brokers, REST endpoints, Kafka topics, InfluxDB, MongoDB, ClickHouse. No direct access to field devices — connectors receive ready-to-use data snapshots.

Routes

Connects provider to connector — defines which data flows where. When adding a new source or destination, the configuration is extended, not the code.

Configuration example.

config.yaml
resources:
  my-metrics:
    currentTemperature: ns=4;i=1
  my-options:
    desiredTemperature: ns=4;i=2

providers:
  my-plc:
    driver: opcua
    config:
      endpoint: opc.tcp://127.0.0.1

connectors:
  my-connector:
    driver: mqtt
    config:
      broker: 127.0.0.1
    routes:
      plc/metrics:
        mode: read
        provider: my-plc
        resource: my-metrics
      plc/options:
        mode: write
        provider: my-plc
        resource: my-options

What it runs on.

Linux, Windows, ARM, x86, embedded hardware, a Raspberry Pi, a DIN-rail PC, an enterprise server. Deployed via Docker or systemd. No proprietary IPC required. No hardware lock-in.

Built for production.

Security

mTLS by default. Zero-trust architecture. Role-based authentication. Containerised isolation. Security is the constraint, not the feature.

Observability

Native OpenTelemetry. Prometheus metrics, structured logs, distributed traces. Compatible with Grafana, ELK and existing monitoring stacks.

Fault Tolerance

Hot reloading. Automatic health checks. Graceful recovery. Change-only data transfer and backpressure management for stable pipelines with slow consumers.

How it compares.

vs. Cogent DataHub

Cogent works. But it's Windows-tied, DCOM-dependent, and not designed for testable, version-controlled, CI/CD-friendly integrations. Sync Connect runs headless on any platform, extends in Go, and ships with structured observability out of the box.

vs. Siemens Industrial Edge

Powerful ecosystem — if you're all-in on Siemens hardware and accept the licensing cost. Sync Connect is vendor-agnostic, runs on commodity hardware, and costs a fraction of the TCO.

Technical.

Provider DriversOPC UA, Modbus, S7, KNX
Connector DriversMQTT, AMQP, Kafka, HTTP, InfluxDB, MongoDB, ClickHouse
SecuritymTLS, zero-trust, role-based auth
ObservabilityOpenTelemetry — traces, metrics, logs
DeploymentDocker, systemd, binary
ConfigDeclarative YAML
Fault ToleranceHot reload, auto health checks, graceful recovery

Frequently Asked Questions.

Connect everything.

OT/IT integration. Configuration-based, vendor-agnostic, on-premise.