Skip to content
Proxus 2.0.0 Proxus 2.0: the largest release in Proxus history Release notes
Try free Book a demo

Integrations · PostgreSQL

PostgreSQL as a first-class industrial data target.

Write every reading into the database your applications already use, continuously and under the tag names you gave it, so an application developer does not need to know what DB1.DBD0 meant.

Book a demo All integrations Setup guide
Equipment to PostgreSQL PostgreSQL
Model once, deliver to your systems Equipment sends data through an edge gateway to Unified Namespace, then to PostgreSQL. Controllers S7 / CIP / MELSEC Machines & robots FOCAS / MTConnect Meters & SCADA Modbus / OPC UA Modelled signals 02 / EDGE Proxus Edge Collect / evaluate / buffer 03 / PLATFORM Unified Namespace Modelled industrial signals PostgreSQL Destination 01 / PLANT FLOOR04 / CONSUMERS Model once, deliver to your systems Read from bottom to top. Field equipment is at the bottom and data travels upward. Equipment sends data through an edge gateway to Unified Namespace, then to PostgreSQL. 01 Plant floor PLCs / CNCs / robots 02 Proxus Edge Collect / evaluate /buffer 03 Unified Namespace Modelled industrialsignals 04 PostgreSQL Destination
Writes to
A table Proxus creates on first write, one row per reading (device, tag, value, data type, time)
Cadence
Continuous: Pass Through, On Change or Pipelines Only
Reliability
Edge buffering when the database is unavailable
Fits
Application back-ends, internal tools and analysis workflows

Data path

What actually moves, and where it stops.

Tag names, not controller addresses

Model once, deliver to your systems Equipment sends data through an edge gateway to Unified Namespace, then to PostgreSQL. Controllers S7 / CIP / MELSEC Machines & robots FOCAS / MTConnect Meters & SCADA Modbus / OPC UA Modelled signals 02 / EDGE Proxus Edge Collect / evaluate / buffer 03 / PLATFORM Unified Namespace Modelled industrial signals PostgreSQL Destination 01 / PLANT FLOOR04 / CONSUMERS Model once, deliver to your systems Read from bottom to top. Field equipment is at the bottom and data travels upward. Equipment sends data through an edge gateway to Unified Namespace, then to PostgreSQL. 01 Plant floor PLCs / CNCs / robots 02 Proxus Edge Collect / evaluate /buffer 03 Unified Namespace Modelled industrialsignals 04 PostgreSQL Destination

Field

  • PLCs, CNCs, robots
  • OPC UA servers
  • Meters and SCADA

Proxus

  • Collect at the line
  • Model into the namespace
  • Buffer and forward

PostgreSQL

PostgreSQL
  • one row per reading
  • application queries
  • analysis workflows

How it works

From the machine to PostgreSQL, in four steps.

  1. 01

    Collect and name

    Equipment values become named, scaled tags.

  2. 02

    Point at the database

    Configure the outbound target and its strategy; the gateway creates its table on first write.

  3. 03

    Build on it

    Applications and analysts query PostgreSQL directly, with no plant network access required.

  4. 04

    Watch the feed

    Delivery status per target confirms the pipeline is intact.

What you get

Why teams route PostgreSQL through Proxus.

  • Developer-friendly

    A familiar database with tag names in the rows, instead of an OT integration exercise.

  • One fixed table

    The table has the same columns wherever Proxus writes it, so views are written once.

  • Server identity checked

    With SslMode VerifyFull, the gateway encrypts the connection and checks the server’s certificate and name against the CA in the Certificate Store.

  • Controlled scope

    Only the devices attached to the target are written; a pipeline can narrow it to single tags.

Where it is used

Typical deployments.

  • Internal applications

    Give in-house tools live production data without custom OT code.

  • Analysis workflows

    Let analysts work in SQL against named tags.

  • Staging for a warehouse

    Land data locally, then move it onward on your own schedule.

Targets
PostgreSQL; SQL Server, Oracle, MySQL, Firebird, ClickHouse, InfluxDB and TDengine are also supported
Payload
One row per reading: device ID and name, tag name, value (as text), data type and time
Strategies
Pass Through, On Change, or Pipelines Only (only what a pipeline sends)
Security
SslMode up to VerifyFull, with the server’s CA from the Certificate Store. When SslMode is not set, the driver encrypts if the server offers it but does not check the server
You configure
Server, Database, User, Password, Port; SslMode. Test Connection checks the address and credentials from the hub or from a gateway you choose, without writing data.
Setup guide All target parameters

Proven in production

Running in production at these plants.

All deployments

Questions

Before you wire it up.

Is PostgreSQL suitable for high-rate telemetry?
It is a good fit for modelled, on-change and business-facing data. For very high-rate raw telemetry, the built-in columnar historian or a time-series database is usually the better target, and you can use both.
Do application developers need OT knowledge?
No, which is the point. They read named tags with their values and times from a familiar database instead of interpreting controller addresses.
Can we run it on our managed PostgreSQL?
Yes, as long as the plant network can reach it. Delivery is outbound from the gateway.
How do schema changes get handled?
The table Proxus writes has a fixed set of columns, so adding or renaming a tag changes rows, not the schema. Configuration changes are recorded in the audit trail, so a renamed tag is a visible action rather than a silent surprise for a downstream job.

Other integrations

Connection guides

Set it up step by step.

All connection guides

Next step

See it delivering into your own PostgreSQL.

Bring one machine and a PostgreSQL database. We connect the machine, show the rows arriving in the table Proxus creates, and what happens while the database is down.

Book a demo Talk to an engineer
  1. 01

    Scoping call

    Equipment, protocols, sites and the systems the data has to reach.

  2. 02

    Technical walkthrough

    A working demo against a scenario that resembles your plant, not a generic tour.

  3. 03

    Pilot plan

    A defined first line or site, with the deployment and security questions answered up front.

  4. 04

    Roll-out

    The same templates bring the next lines and sites online.