Integrations
Collect once. Deliver everywhere it is needed.
Proxus sits between the equipment and the systems that consume its data. Each target gets its own devices and its own delivery strategy, without another collection layer per consumer.
- Collect from
- PLCs, CNCs, robots, meters, OPC UA servers and devices that publish to the built-in MQTT broker
- Deliver to
- 18 kinds of system: cloud services, message brokers, relational and time-series databases, and REST APIs
- Per target
- Which devices send to it, and its strategy: Pass Through, On Change or Pipelines Only
- Reliability
- Buffered at the edge, forwarded when the target returns
Streaming and events
-
Apache Kafka Publish plant readings, and the events your pipelines raise, to Kafka for event-driven consumers. Apache Kafka integration -
MQTT & Sparkplug B Subscribe to the namespace on each gateway’s built-in broker, publish to your own broker, and collect from devices that publish their own values. MQTT & Sparkplug B integration -
Splunk Send industrial readings and events to Splunk’s HTTP Event Collector. Splunk integration
Database
-
Microsoft SQL Server Write production data continuously into a SQL Server table that reports and business systems can read. Microsoft SQL Server integration -
PostgreSQL Write industrial data continuously into PostgreSQL for applications and analysis. PostgreSQL integration -
InfluxDB Stream industrial time-series readings into InfluxDB 2.x. InfluxDB integration
Also supported
Targets without a page of their own, yet.
These work the same way: choose which devices send to the target and its strategy, and the gateway buffers if the target is unavailable.
- RabbitMQ To an exchange with a routing key, in a virtual host you choose.
- Redis Into the database number you choose, as a hash by default.
- Azure Data Lake Storage Gen2 Parquet, JSON or CSV files, written in batches. Covered on the Azure page. Microsoft Azure
- TDengine Into a super table in the database you name, with its retention set on the target.
- ClickHouse Into a table of your own ClickHouse. The hub keeps its own history in ClickHouse too.
- REST API A JSON POST per reading, or called from a pipeline’s Call Api node for ERP and MES.
- MySQL A table the gateway creates on first write; SslMode up to VerifyFull.
- Oracle A table the gateway creates on first write, by data source or TNS name.
- Firebird A table the gateway creates on first write.
Need a system that is not listed? A REST API target, or a pipeline that calls the system’s API with a Call Api node, reaches many of them.
Talk to an engineerBeyond targets
Other ways in and out of Proxus.
Outbound targets push data to other systems. These read from Proxus, bring older data into it, or reach people.
- Namespace over MQTT Each gateway’s built-in broker publishes every tag value on topics that follow the namespace, in JSON or Sparkplug B 3.0. Applications subscribe with the gateway’s token. Setup in the docs
- REST API Sign in as a Proxus user and read or change devices, gateways, rules and other objects over OData, within that user’s role. Setup in the docs
- Telemetry API Query stored tag values with one SQL SELECT over HTTP and read the rows back as JSON lines. For administrators only. Setup in the docs
- MCP for AI assistants Claude, Cursor or VS Code connect to the hub over the Model Context Protocol and answer from the live system, with the rights of the Proxus user they sign in as. Setup in the docs
- Historical import Send readings a device recorded in the past, from a data logger or a CSV export, to the historian in batches over HTTP. Turned on in the configuration. Setup in the docs
- Notification channels Rules, pipelines and scheduled deliveries reach people by email, SMS, WhatsApp, push, Slack, Teams, Discord, Telegram, Line or Messenger. Setup in the docs
Next step
See it delivering into your own stack.
Bring the target system and the signals it is missing. We will show the path from the controller to your table, topic or service, including what happens when the link drops.
- 01
Scoping call
Equipment, protocols, sites and the systems the data has to reach.
- 02
Technical walkthrough
A working demo against a scenario that resembles your plant, not a generic tour.
- 03
Pilot plan
A defined first line or site, with the deployment and security questions answered up front.
- 04
Roll-out
The same templates bring the next lines and sites online.