The M&L technology approach

API & MQTT Developer Integration

Integrate NetRelay into your software stack. Read I/O data, collect sensor telemetry and control physical relays in real time using MQTT, HTTP, TCP and WebSocket.

Stop Rebuilding Hardware. Focus on Your Software.

For professional developers, the real challenge is not learning how to drive a relay. It is creating a reliable bridge between software and the physical world. NetRelay combines Ethernet, Wi-Fi, PoE, digital inputs, relay outputs, sensor interfaces and multiple communication protocols in a ready-to-use platform.

Applications built with Python, Node.js, C#, VB.NET, Delphi, PHP, C++ and many other technologies can access physical I/O resources, read digital inputs, collect sensor data and control relay outputs programmatically.

Direct Access to Physical I/O from Your Software

Instead of thinking of NetRelay as a traditional relay board, think of it as a network-accessible physical I/O layer. Your application can read inputs, query device status, monitor sensors and trigger real-world actions whenever your business logic requires it.

Integrate in Minutes with HTTP API

HTTP GET and POST support makes simple integrations possible without requiring a proprietary SDK. Applications can retrieve I/O and sensor information in JSON format and control relay outputs using standard web requests.

This makes NetRelay easy to integrate into existing ERP, MES, production tracking, building management and custom backend applications.

Build Real IoT Architectures with MQTT

For distributed and scalable systems, NetRelay can operate as an MQTT client connected to a local or remote broker. Device and sensor states can be published as telemetry while relay outputs can respond to command messages.

The publish/subscribe architecture decouples devices from applications. NetRelay devices publish their data to the broker while dashboards, mobile applications, analytics services and automation engines subscribe only to the topics they need.

Own Your MQTT Infrastructure

NetRelay does not require you to depend on a vendor-specific cloud. Your MQTT broker can run on your own server, VPS or directly inside the local network of your facility.

You decide where data is stored, how users authenticate, which applications can control which devices and how telemetry is processed.

Instead of purchasing hardware that locks you into someone else's cloud, NetRelay enables you to own the complete IoT architecture.

Build Your IoT Backend with Node.js

Node.js developers can connect NetRelay devices to an MQTT-based backend and build centralized device management platforms. Incoming telemetry can be stored in PostgreSQL, MongoDB, Redis or any data platform of your choice and streamed to web dashboards through WebSocket connections.

A Node.js backend can receive state information from many NetRelay devices, monitor their availability and route commands from users to the appropriate physical relay.

Give Python Applications a Physical Output

Python-based AI, computer vision, analytics and automation applications can use NetRelay to turn software decisions into real-world actions.

A computer vision application can recognize an authorized vehicle and open a barrier. A machine-learning model can identify an abnormal production condition and trigger an alarm. A monitoring service can analyze sensor values and automatically control pumps or ventilation equipment.

Your model does not have to stop at making predictions. With NetRelay, its decisions can become physical actions.

Connect Existing C#, VB.NET and Delphi Applications

Existing enterprise and desktop applications do not need to be completely rewritten to gain IoT capabilities. C#, VB.NET and Delphi applications can communicate with NetRelay through standard HTTP, MQTT or TCP protocols.

TCP Integration for Existing Systems

TCP Server and Client capabilities provide flexibility for industrial software, barcode systems, proprietary device protocols and legacy applications.

Real-Time Control with WebSocket

WebSocket support enables low-latency control interfaces. A command issued from a web dashboard can reach NetRelay immediately and trigger a physical output in real time.

Collect, Process and Visualize Telemetry

NetRelay is not only a command receiver. Digital input states, sensor measurements and device information can be sent to central software for storage, visualization and analysis.

Store the data in time-series databases, display it in dashboards or feed it into analytics and AI pipelines.

Cloud Is Optional: Build Fully Local Systems

NetRelay can operate completely inside a local network. Devices, MQTT broker and backend services can remain on the same LAN, allowing automation systems to continue operating without an external cloud dependency.

A Clean Edge-to-Backend Architecture

NetRelay handles physical inputs and outputs while your application manages business logic, user permissions, data storage, reporting and automation rules.

This separation allows developers to focus on software instead of repeatedly solving the same embedded hardware problems.

Build Your Own Product on NetRelay

Software companies can use NetRelay as the physical control layer of their own products. Instead of investing months into custom hardware development, teams can focus on their user interface, backend and unique business logic.

Build your own energy management application, production monitoring platform, remote device management system, smart agriculture solution or access control product on top of NetRelay.

Beyond a Typical API Call

In traditional software, an API call usually changes data. With NetRelay, an API call can create a real physical result.

Your code no longer has to end at the screen.

Example Professional Architecture

Imagine NetRelay devices deployed across several facilities. Each device connects to an MQTT broker and publishes its I/O states under a defined topic structure. A central Node.js backend processes these messages and stores them in PostgreSQL. A web dashboard receives live device updates through WebSocket connections.

When a user issues a relay command, the backend publishes the instruction to the appropriate MQTT topic. NetRelay receives the command and controls the physical output. The updated device state is then published back through MQTT and reflected in the user interface in real time.

In this architecture, NetRelay provides the field I/O layer, MQTT provides the messaging layer, your backend implements business logic and your web application delivers the user experience.

Use the Technology You Prefer

NetRelay does not lock developers into a specific programming language or framework. Use Python, Node.js, C#, C++, VB.NET, Delphi, PHP or any platform capable of communicating over MQTT, HTTP, TCP or WebSocket.

Build the dashboard with React or Vue, create your SaaS application with Next.js, run your MQTT backend with Node.js, integrate AI services with Python or maintain existing enterprise software with C# and Delphi. NetRelay remains the common physical I/O layer.

NetRelay for Developers

You build the intelligence. NetRelay handles the physical I/O layer between your code and the real world.