Skip to content
Proxus 2.0.1 Licence and sign-in fixes after the 2.0 upgrade Release notes
Try free Book a demo

Proxus Industrial Data Platform

Your entire industrial data stack. One product.

Machine connectivity, Unified Namespace, historian, rules, dashboards and delivery to ERP and the cloud, in one install on your own servers.

Book a demo See the product Watch the film
  • 60+ protocols
  • 15+ destination systems
  • Keeps recording when the network drops
  • Priced by gateways and data rate, never by tag

Every machine is read in its own protocol, by software on your plant server.A raw register becomes a named signal with its place in the plant.Rules run on live values; the alarm says what happened and why.The link drops: the Edge Gateway buffers the values and sends them in order when it returns.One model, delivered to every system that needs it.

Machines on the plant floor send their values in their own protocols to the Edge Gateway, software on the plant server. The Edge Gateway forwards them to the Proxus Hub, which places every value in a Unified Namespace, runs rules and alarms and keeps the history; if the link drops the Edge Gateway stores the values and sends them when it returns. The hub delivers the same model to ERP, MES, the cloud, time-series and SQL databases, event streams and a REST API.

In production at Siemens, MEXT, Kaltun, PilenpakSee deployments

  • Siemens
  • Vodafone
  • Turkcell
  • KPMG
  • Cisco
  • Hewlett Packard Enterprise
  • TD SYNNEX
  • İSBAK
  • Komtaş
  • Kaltun
  • Pilenpak
  • Abdi
  • MEXT

From a controller to a dashboard, without leaving the product.

Industrial connectivity

Device connectivity

Connect PLCs, CNCs, robots, meters and OPC UA servers, then define the tags you need and how often they are read.

Explore connectivity

At the line

Edge runtime

Collect, transform and buffer at the line. Evaluate rules, detect anomalies and run your own functions before the data moves.

Explore edge runtime

Unified Namespace

UNS Explorer

Browse every signal by enterprise, site, area, process cell, equipment module and device, with the live value and last update on every node.

Explore unified namespace

Visualization

Dashboards and reports

Operational views and scheduled reports for plant and management teams, built on the same governed data.

Explore dashboards

IT and OT delivery

Integrations

Deliver modelled data to databases, message brokers, cloud services and business systems, per target and per strategy.

Explore integrations

AI Assistant

Proxus AI Assistant

Ask in plain words from any screen (Ctrl+K): why a device is silent, what changed, which alarms are open. The assistant reads the live namespace with your permissions and proposes rules and changes on a card. A change is applied only after you approve it, and the audit trail records it under your name.

Explore ai assistant

The story in two minutes

Four systems. Four answers. One source of truth.

Why ERP, MES and dashboards show different numbers for the same line, and what changes when every system reads one governed model.

Length 2:03 Captions available Also on YouTube
Read the transcript

One simple question. How many good parts did Line 3 make yesterday? The ERP gives you one number. The MES gives you another. The dashboard, a third. And the spreadsheet? Something else entirely. Four systems. Four answers. So which one is the truth? Because plant data gets collected again and again. A driver server for the PLCs. A broker for the messages. A historian for the history. A modelling tool for context. A rule engine for alarms. Dashboards. An edge box for outages. And scripts to glue it all together. Eight tools. Eight copies of your data. Eight licences. And eight places where something breaks. A link drops, and values vanish. A tag is renamed, and a report breaks. And nobody can say which number is right. Proxus replaces that whole chain with one product. One place where the truth lives. It reads every machine directly, with more than 60 native protocols. No driver server. Every value gets one name, one unit, and one place, in a Unified Namespace. That model is your single source of truth. It keeps the history, runs rules and alarms at the edge, and rides through outages. And it delivers that same model to ERP, MES, the cloud, your dashboards, and your AI. No glue code. Now, ask the question again. ERP, MES, the dashboard, the AI assistant. They all read the same model. One answer. Everywhere. Every time. And that truth lives where it belongs. On your servers, in a private cloud, or fully air-gapped. Your data never has to leave your network. Priced by gateways and data rate. Never by tag. Proxus. Your entire industrial data stack. One product. One source of truth.

Why one product

Six jobs, usually six products. One install.

A plant’s data stack is usually bought one product at a time. Each comes with its own upkeep, its own permissions and its own name for the same tag, and most with their own licence.

The job Usually bought as In Proxus
Read the machines A driver server 60+ protocols, built in
One data model (UNS) A data modelling layer One namespace in plant order, ISA-95
History A data historian Plant-level history built in, no separate historian licence
Screens, alarms, reports A SCADA platform (for monitoring screens) Dashboards, alarms and scheduled reports
Rules and automation Flows and hand-written scripts Pipelines and C# functions, running at the line
Delivery to systems and cloud Cloud services plus middleware 15+ destination systems; data waits on site when the link drops
6 productstheir own upkeep, most their own licencetheir own permissionsthe same tag defined again in each 1 install1 data model1 permission model1 vendor to call

Many products on the market do more than one of these jobs, and each is strong at its own. What you already run can stay: Proxus reads existing OPC servers over OPC UA, imports Kepware projects and sends data on to the historian and the other systems you keep.

Map your current stack with us Read the comparisons

Proven in production

Running in production, not in a slide deck.

All deployments

We show the deployment closest to your plant, on your own equipment list.

Book a demo

Inside Proxus

Recorded in the running product.

Recorded in the running product against a simulated food and beverage plant. Every click is real; so are the connection test, the tag read and the diagnosis.

Book a demo Try the live demo

The live demo is a running platform in your browser; the sign-in arrives by email.

Recorded in the product, cursor and all · 0:42Simulated plant data

Before the first meeting

The questions every first meeting asks.

Plant, automation and IT teams ask the same six things. Here are the answers, so the meeting can be about your plant.

What IT reviews first

Trust and compliance
Talk to an engineer
“We already run Kepware.”
Keep it. Proxus connects to it over OPC UA, or imports the Kepware project and reads the devices itself.
“We already have a historian.”
Keep it too. Proxus sends data on to it through its database or web service; new sites need no separate historian licence.
“We could build this ourselves.”
You could. The real cost comes later: years of upkeep, and a data layer only two or three people understand.
“Our data must not leave the plant.”
It does not have to. Proxus runs entirely on your servers, also on a network with no internet access, and no data passes through our cloud. The AI Assistant can use a local Ollama model, so even AI questions stay on site.
“What if the network drops?”
The Edge Gateway keeps collecting, running rules and recording, and sends what it held when the link returns. Its settings live on the hub, so a failed unit is replaced, not rebuilt.
“So many features. Is it complicated?”
You start with one line and one destination system. The rest is switched on when you need it, in the same product.

Pricing

The price is on the site. No surprises.

Two numbers set your price: the gateways you run and the data rate they carry.

Tags, devices, users, dashboards and API calls never change the price.

Get a quote Estimate your plan

Next step

See it against your own plant data.

Bring a machine, a protocol and a system you need to feed. We will show the path from register to governed namespace to delivered value, and what it takes to run it in production.

  1. Scoping call

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

  2. Technical walkthrough

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

  3. Pilot plan

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

  4. Roll-out

    The same templates bring the next lines and sites online.

Tell us about your plant

A Proxus engineer replies within one working day.

We use your details to answer this request. Marketing emails only if you tick the box; no resale. Privacy notice

Rather look around first? Try the live demo