Integrate legacy infrastructure with modern protocols,
no coding, no hardware replacement and extend the life
of your infrastructure, accelerating your digital transformation.
Start bridging the gap now.
Protolinker helps factories, system integrators, machine builders, and engineering teams connect industrial equipment, IoT services, databases, and business systems through a visual, configurable protocol bridge with a protocol library that keeps expanding as integration needs grow.
Create protocol connections, tags, and links from the interface instead of building and maintaining custom integration code for every machine, broker, API, or database connection.
Connect Modbus TCP, Modbus RTU, MQTT, OPC UA, REST APIs, TCP/IP sockets, serial devices, and SQL databases from one application, with client and server modes where the codebase supports them. Protocol support is designed to keep growing as more industrial and IoT integration cases appear.
Define tags, choose source and destination protocols, and link data points through a structured workflow that makes every route visible before data starts moving.
Add scripts to tags or links when values need transformation, validation, formatting, filtering, or custom business logic before they are forwarded to another system.
Scan authorized local IPv4 networks, detect supported endpoints, review confidence and details, then create supported Modbus TCP, MQTT, OPC UA, or REST API connections from selected results.
Store tag values in SQL databases and schedule AI-assisted reports that analyze machine and sensor data for trends, anomalies, correlations, possible causes, and recommended actions.
Track protocol status changes, tag value changes, and errors with plan-based log lookback and retention, including real-time log viewing and direct access to log files.
Buffer tag-link writes while a destination is disconnected, then flush them when the connection is restored. Automatic reconnect logic helps integrations recover from transient network issues.
Save integration configurations as JSON, import existing setups, and run in CLI mode with a stored file so repeatable deployments can be started without rebuilding the setup from the UI.
Built with Qt and packaged for Windows, Linux, and macOS, Protolinker gives engineering teams a consistent integration tool across common industrial workstations.
Start with constrained testing on Free, unlock unlimited protocols, tags, and links on paid plans, then add scripts, all protocol types, AI reporting, discovery, and longer retention as needs grow.
Sign in, restore saved sessions, monitor connection state, start or stop every protocol at once, and use the tray controls to keep integrations running in day-to-day operations.
Start free, then upgrade when you need more protocols, automation, scripting, reporting, and long-term data visibility.
For demos, testing, and small protocol experiments.
For small integrations that need unlimited mappings.
For advanced automation with scripting and all protocols.
For teams that want the complete Protolinker platform.
Protolinker gives teams a faster way to test, connect, and reuse industrial data flows without turning every protocol integration into a custom software project.
“We expected another custom converter project. Instead, Protolinker let us connect Modbus sensors to MQTT and see live machine data on the dashboard in a fraction of the time.”
“The biggest surprise was how visible the integration became. We can see where each data point goes, change mappings quickly, and stop relying on one person who understands every script.”
“We did not have to replace the machine to get value from it. An older PLC started feeding data into a modern system, which opened up monitoring options we did not have before.”
“For us, the value is flexibility. We can connect devices from different vendors, test new data routes, and adjust the flow without rebuilding the entire integration every time.”
A quick guide to how Protolinker fits into industrial integration projects, from protocol support and legacy equipment to scripts, logs, discovery, and AI-assisted reporting.
Protolinker is built for teams that need machine data moving sooner, without replacing working equipment or maintaining custom middleware for every protocol bridge.
Protolinker connects industrial and IoT systems so data can move between machines, brokers, APIs, databases, dashboards, and other tools. Instead of writing a custom bridge for every case, teams configure protocols, tags, and links visually.
The current codebase includes support for Modbus TCP, Modbus RTU, MQTT, OPC UA, REST APIs, TCP/IP sockets, serial connections, and SQL databases, with client and server modes where implemented. Protocol support is designed to keep growing as more industrial and IoT use cases appear.
No. Protolinker is designed to work with existing equipment and existing communication channels whenever those systems expose supported protocols. That makes it useful for getting value from legacy machines before planning larger infrastructure changes.
No. Developers can extend integrations with scripts, but the core workflow is visual: create protocol connections, define tags, link data points, and monitor status. This helps engineering and operations teams understand the data flow without reading custom code first.
Yes. On plans that include scripting, scripts can be attached to tags or links for formatting, validation, filtering, calculations, or custom logic. This is useful when a simple source-to- destination mapping is not enough for a real production case.
Yes, protocol discovery is available on supported plans. Protolinker can scan authorized local IPv4 networks, detect supported endpoints, show confidence and details, and create compatible protocol connections from selected results.
Protolinker includes reconnect handling and, on supported plans, disconnected buffering for tag-link writes. Buffered writes can be held during short disconnects and flushed when the destination reconnects, reducing the risk of losing important values during temporary outages.
Yes. Protolinker logs protocol status changes, tag value changes, and errors. Log lookback and retention depend on the active plan, with longer retention available on higher plans for debugging, auditing, and troubleshooting.
AI-assisted reports can analyze SQL-stored machine and sensor data for trends, anomalies, correlations, possible causes, and recommended actions. They are useful when teams want more than raw telemetry and need clearer operational insight from historical data.
Yes. Protolinker can export and import integration configurations as JSON. This helps teams back up working setups, repeat proven configurations, and start similar deployments faster.
Use Protolinker to test integrations, map data visually, and move industrial signals from PLCs, sensors, brokers, APIs, and databases into the systems your team already uses.
