Proxus platform
Every project we deliver runs on Proxus
Instead of stitching together a connectivity server, data model, historian, SCADA screens and integration tools, we use one product, and we build it ourselves.
Our clients
- Siemens
- Anadolu Isuzu
- BSH
- Tofaş
- Toyotetsu
- Martur
- Turkcell
- Vodafone
- Doğadan
- Pakmaya
- Bross
- Abdi İbrahim
- Nobel İlaç
- Plastimak
- Dalgıç Kalıp
- Barbaros Motor
- Magneti Marelli
- Rözmaş
- Sanel
One product, machine to ERP
What Proxus holds
It runs on your servers, in a private cloud or on air-gapped networks, with no vendor cloud in your data path.
-
Industrial connectivity
Ready drivers for Siemens, Allen-Bradley, Mitsubishi, Omron and Beckhoff PLCs, Fanuc and Heidenhain CNCs, OPC UA, Modbus and more.
See it on proxus.io ↗ -
Edge runtime
Rules, functions and alarms run next to the machine. Data is buffered when the network drops and sent when it returns.
See it on proxus.io ↗ -
Unified Namespace
Every signal defined once in an ISA-95-shaped namespace, with permissions and traceability.
See it on proxus.io ↗ -
Historian and analytics
Time-series data, queries, reports and ready indicators such as OEE.
See it on proxus.io ↗ -
Dashboards
Line, plant and management screens, from the operator panel to the board report.
See it on proxus.io ↗ -
Enterprise integration
Delivery to databases, MQTT/Kafka, cloud services and ERP.
See it on proxus.io ↗
VOLSOFT and Proxus
The team that builds the product installs it
You can buy Proxus and deploy it with your own team or a partner. If you want VOLSOFT to take on the deployment, data model and integrations, you work with the team that builds the product, and needs found on the floor go straight into the roadmap.
For the product, pricing and documentation, see proxus.io; for a project, scope or proposal, contact us.
Next step
Let’s turn your goal into a clear engineering scope.
Tell us about your plant, your machines and your goal. An integration engineer will set up a discovery call with you.
