Skip to main content
v2.4 Available Now: UNS for Everyone

The Operating System for
Industrial Intelligence

Connect Edge to Enterprise in real-time. Proxus streams data into a unified namespace, runs rules at the edge, and fan-outs safely to dashboards, analytics, and databases.

Explore Platform expand_more
Robotics
PLC/CNC
Sensors
Legacy DB
Ingest
2,412 msg/s
Normalize
1.2 ms
Rules Engine
Active
Edge Store
88 IOPS
Dispatch
Streaming
SAP
ERP
Cloud
Grafana
Alerts

Trusted By

Abdi
Cisco
HP
ISBAK
Kaltun
Komtas
KPMG
Pilenpak
Siemens
TD Synnex
Turkcell
Vodafone
Abdi
Cisco
HP
ISBAK
Kaltun
Komtas
KPMG
Pilenpak
Siemens
TD Synnex
Turkcell
Vodafone
Abdi
Cisco
HP
ISBAK
Kaltun
Komtas
KPMG
Pilenpak
Siemens
TD Synnex
Turkcell
Vodafone

Eliminate the "Spaghetti Architecture"

Traditional point-to-point integration leads to Operational Blindness and skyrocketing Total Cost of Ownership (TCO). Proxus replaces this fragile web with a Unified Namespace (UNS)—a central data highway where all devices and apps communicate fluently.

  • Single Source of Truth: No more data silos or conflicting metrics.
  • Decoupled Architecture: Add new tech without breaking the old.
  • Instant Access: ERP, MES, and Cloud get real-time data instantly.
Before: Point-to-Point
ERP
MES
SCADA
PLC
HMI
Cloud
Blind spots · High TCO · Fragile links
After: Unified Namespace
UNS
ERP
PLC
Cloud
MES
Dashboards
AI/Analytics
Single source of truth · Decoupled · Real-time

Built for Engineers,
Loved by Developers

Why wait months for deployment? Spin up a full instance in 5 minutes with Docker. Need custom logic? Use our built-in C# editor to write high-performance scripts directly at the edge.

Docker Ready
C# Scripting
EdgeScript.cs
 

Success Stories from the Field

Siemens Kocaeli production line
Siemens

Operational Efficiency in Production

  • Issues: No data from punch/bending machines; hard to spot bottlenecks or optimize planning.
  • Why Proxus: Siemens Edge-friendly, strong data collection, bidirectional SAP, AWS-ready.
  • Impact: Real-time OEE from legacy machines, better capacity plans, fewer unplanned stops, optimized energy.
Kaltun mining sites and fleets
Kaltun Maden

15+ Sites, One Unified View

  • Issues: Data from plants, fleets, GES scattered; efficiency and cost reduction hard.
  • Why Proxus: Scales to all sources, multi-protocol, advanced analytics, cloud-ready, GES capture.
  • Impact: Live reports on equipment, fuel, production, energy, safety; inefficiencies removed, costs down, safer ops.
Pilenpak production line
Pilenpak

Digital Transformation Kickoff

  • Issues: Limited data collection; hard to optimize production or track energy instantly.
  • Why Proxus: UNS as SoT, multi-protocol (OPC UA, Modbus, MQTT), analytics/dashboards, Oracle ERP link.
  • Impact: Live OEE and energy analytics feeding Oracle ERP; clearer plans, faster cycles, fewer stoppages, optimized energy.

Projects in Progress

Ongoing
IETT fleet edge computing
İSBAK / İETT

Fleet Edge Computing

  • Issue: 6,000+ buses; CANBus/video bandwidth limits; GSM dropouts.
  • Approach: Edge filtering/buffering, critical events only, async sync at depot.
  • Result: Real-time alerts with major bandwidth savings (rollout in progress).
Ongoing
CK Enerji transformer monitoring
CK Enerji

Grid Monitoring at the Edge

  • Issue: LV transformer blind spots, SCADA licensing limits, unstable links.
  • Approach: Edge buffering, IEC 60870-5-104/Modbus ingest, local anomaly detection.
  • Result: Better visibility and fewer outages (deployment underway).
Ongoing
TREDAS transformer analytics
TREDAŞ

LV Transformer Analytics

  • Issue: Irregular LV data, visibility gaps, costly scaling.
  • Approach: Edge cache, offline replay, IEC/Modbus ingest, local alarms.
  • Result: Targeted maintenance and fewer outages (pilot in progress).

Frequently Asked Questions

Common questions about Proxus deployment, licensing, and architecture.

How fast can we deploy Proxus?

With Docker, you can spin up a Proxus instance in under 5 minutes on any x86 or ARM hardware (edge gateways, on-prem servers, cloud VMs). Pre-built images include all drivers and integrations. Configuration is centralized—deploy once, scale to hundreds of gateways without rebuilding.

Do we pay per device or per protocol?

No. Proxus includes 50+ industrial protocols out of the box—Siemens S7, Modbus TCP/RTU, OPC UA, MQTT, Ethernet/IP, and more. No hidden driver fees, no per-device or per-tag licensing. Connect as many machines as your hardware can handle.

What happens if the network goes down?

Edge Gateways buffer all telemetry locally using NATS JetStream when the central connection drops. Once the link is restored, data replays in order automatically—zero data loss. Critical rules and local dashboards continue running at the edge during outages.

Can we integrate with our existing ERP (SAP, Dynamics, etc.)?

Yes. Proxus has built-in IT/OT bridge integrations for SAP, HTTP/REST APIs, Kafka, AWS IoT, Azure IoT Hub, and more. Data flows outbound from the unified namespace to your enterprise systems—no inbound PLC exposure. Custom integrations can be built with our C# scripting engine.

Is Proxus cloud-only or can we run it on-premises?

Proxus is deployment-flexible. Run the central server on-premises, in your private cloud, or in AWS/Azure. Edge Gateways operate at the plant network edge—no cloud dependency for core operations. You control where data lives and how it moves.

Do we need to replace our existing SCADA or MES?

No. Proxus complements existing systems. It acts as a data backbone—your SCADA, MES, and ERP subscribe to the unified namespace for real-time telemetry. You can modernize incrementally without ripping and replacing legacy investments.

What kind of hardware do Edge Gateways need?

Any modern x86 or ARM device works—industrial PCs, Raspberry Pi 4+, mini PCs, or ruggedized edge computers. Minimum: 2GB RAM, 10GB storage. For high-throughput lines (1000+ tags/sec), use 4GB+ RAM. Gateways are stateless, so if one fails, replace and redeploy in minutes.