MAJiK Systems
MAJiK IoT Connect

Industrial connectivity, simplified.

Monitor production in real time, from every machine you run. One agent connects nearly every PLC and CNC, driving live production monitoring, condition-based maintenance, and AI you can trust, with clean, contextual data flowing in minutes.

Book a Discovery CallSee How It Works
20 Protocols
Broad coverage, from PLCs and CNC
controls to building systems
See them all
Simple install
One program file, no Java, no Docker,
no gateway server. Runs on every OS.
~5 min
From Install to First Data

Where it fits

From PLC to the Cloud

Your equipment speaks dozens of industrial protocols. Your ERP, CMMS, and BI tools speak none of them. MAJiK IoT Connect is the first half: it streams real-time machine operating data from the shop floor into MAJiK Visual Factory, where it becomes the intelligence that finds your untapped capacity, and flows on into the systems you already run.

Your equipment

PressesCNCsInjection moldersRobotsFillers

Machining & fabrication

Laser cuttersPress brakesWeldersGrindersLathesEDMDie casting

Plastics

ExtrudersBlow molders

Packaging & end of line

PackersCappers & labelersPalletizers

Lines

Assembly linesPackaging linesProduction linesBottling linesCanning lines

Process & utilities

Mixers & blendersOvens & furnacesConveyorsPumps & motors

Sensors

TemperaturePressureFlowLevelVibrationProximity

Every machine already knows its own condition: temperatures, speeds, cycle counts. Each speaks its own protocol.

MAJiK IoT Connect

Typed & contextualOPC UA ServerMQTT · Sparkplug BUnified Namespace

One small agent on a VM or industrial PC. It reads every machine, gives the raw data meaning, and publishes it up to the cloud.

Cloud

MAJiK Visual FactoryERPCMMSBI toolsand more

Your clean, contextual data lands in MAJiK Visual Factory and flows on to your ERP, CMMS, BI tools, and more.

MAJiK IoT Connect is designed to work seamlessly with MAJiK Visual Factory. Real-time machine operating data from the shop floor is what unlocks untapped capacity, holds quality to spec, and grounds AI you can trust. See what MAJiK Visual Factory does with it.

What teams do with real-time machine operating data

Connectivity is the means. These outcomes are what it is for. Follow any of them for the workflow, the proof, and the numbers.

OEE & Production Monitoring
Find the capacity already sitting in your plant: a live read on equipment effectiveness, production counts, and the reasons output slips, straight from your machines.
Condition-Based Maintenance
Service equipment on its real condition instead of the calendar, so unplanned downtime stops draining capacity and your CMMS gets the right work order at the right time.
Hold quality to spec, automatically
Stream process values and setpoints live, so drift shows up while you can still act on it, not in next week's scrap report.
Ground your AI in real machine data
Give AI the clean, contextual data it needs to recommend changes you can trust. Same factory, same equipment, same people, 2 to 5 percent more output.

See it work

From the box on your network to clean, contextual data, all in one app.

Connect every PLC

Point MAJiK IoT Connect at your network and it finds what is there: Allen-Bradley, FANUC, Siemens, and more. Broad protocol coverage is built into the agent, so there are no per-brand drivers to license, install, or keep up to date.

See all 20 protocols
The IoT Connect desktop app showing connected data sources across EtherNet/IP, OPC UA, Modbus, S7, and MQTT
The desktop app's Data Sources view: nine sources across EtherNet/IP, OPC UA, Modbus, S7, and MQTT, each showing its endpoint, tag count, and poll interval, with live connection status.

Everything in one download

The MQTT broker, OPC UA server, Sparkplug B publisher, cloud bridge, and historian all run inside one agent: a single program file, what engineers call a binary. No Java, no Docker, no separate gateway server to assemble or maintain. It runs the same on Windows, Linux, and macOS, so it is far simpler and faster to install and keep running.

Clean, contextual data

Clean data, managed your way. Raw PLC registers become typed, named values with units and quality, scaled and state-mapped by over 20 built-in edge transforms, tagged with the equipment and site they belong to, and auto-classified by downtime reason, all before they leave your network. What publishes is data people can actually use.

See how it works

One tag, transformed

Raw PLC register

DB10.DBW28 = 7242
typed, scaled, named, and given units at the edge

Publishes Messages

DDATAspBv1.0/NorthPlant/DDATA/edge-01/oven-1
Zone1/Temperature = 72.42 °C

Nothing fails silently

Every agent, connection, and endpoint reports its own health over OpenTelemetry, so a stale tag or a dropped link surfaces before it reaches a dashboard. Pipe the same telemetry into Grafana, Datadog, Prometheus, or any OpenTelemetry backend.

How the agent uses OpenTelemetry
Agent network view showing per-connection status and latency, with a dropped link flagged

Native Protocol Support

Coverage for everything on your shop floor, from PLCs and CNC controls to sensors and building systems. Not adapters or middleware: each protocol is implemented natively in the agent binary with zero external dependencies.

ProtocolSupported EquipmentReadBrowseSubscribe
PLC & Automation
OPC UAKepware, Ignition, Siemens, Beckhoff, B&R
EtherNet/IPAllen-Bradley CompactLogix, ControlLogix, GuardLogix, Micro800—
Siemens S7S7-1200, S7-1500, S7-300, S7-400——
Modbus TCPVFDs, power meters, temperature controllers, sensors——
Beckhoff ADSTwinCAT 2 and 3 controllers—
SLMP / MELSECMitsubishi iQ-R, iQ-F, Q series—
PCCC / DF1Allen-Bradley MicroLogix, SLC 500, PLC-5——
CIP ExplicitAllen-Bradley drives, VFDs, and robots via direct MSG reads—
CNC & Machine Tools
MTConnectMazak, Okuma, Haas, Fanuc CNC machines—
FOCASFanuc CNC controls—
LSV2Heidenhain TNC controls—
Molding & Plastics
EUROMAP 63Engel, Arburg, KraussMaffei—
Building Automation
BACnet/IPAHUs, chillers, boilers, VAV boxes, BTU and energy meters, plant building systems—
Fastening & Torque
Open ProtocolAtlas Copco, Desoutter, Bosch Rexroth, and other tightening controllers—
Weighing & Scales
ASCII ScalesMettler Toledo (MT-SICS, Continuous), Sartorius SBI, A&D, SMA, generic ASCII via Moxa/Lantronix serial servers
Messaging & Data
MQTTAny MQTT publisher, IoT gateways—
HTTP / RESTAny REST API, JSON endpoints, webhooks——
SQLPostgreSQL, SQL Server, MySQL, historians—
FilesParquet, CSV, and JSON files—
IO-LinkIFM, Balluff IO-Link masters——

Every protocol reads live values. Browse discovers tags without a manual list; Subscribe pushes changes instead of polling. It also runs ping, TCP, and HTTP checks for infrastructure health.
Running something you do not see here? Ask us what it takes to connect it.

Not sure how to connect your equipment?

Start with a short conversation. We will look at what you run and give you a simple plan for bringing your machines online.

Talk through your setup

Replacing something?

How MAJiK IoT Connect compares to the tools teams reach for today.

vs. Kepware
Everything an OPC server gives you, plus the broker, the historian feed, and the glue between them, in one download. Fewer products to license, fewer to maintain.
vs. Ignition Edge
Edge collection, the broker, and an OPC UA server, with none of the JVM and platform footprint to size and patch. A smaller box runs it, and your team has less to babysit.
vs. AWS IoT
Collection, the broker, an OPC UA server, and a Unified Namespace in one download, instead of a stack of cloud services to assemble, operate, and maintain. Live in minutes, not a project.

See all the side-by-side comparisons

Built for IT and OT security

Outbound-only connections, read-only PLC access, and encrypted transport with a unique per-agent identity, so MAJiK IoT Connect fits the policies IT and OT teams already enforce.

Outbound-Only Connections
The agent makes only outbound connections, over MQTT (8883) and HTTPS (443). No inbound ports to open, so it fits the outbound firewall policy your IT team already runs.
Unique Per-Agent Identity
Every agent registers with its own unique machine identity and authenticates with its own credential that rotates automatically, so there are no shared keys to leak. The cloud broker enforces per-tenant isolation, so an agent can only ever publish its own site's data.
Read-Only PLC Access
The agent reads from your PLCs and never writes: no reprogramming, no setpoint changes. For defense in depth, pair it with a read-only OPC UA role or a one-way firewall rule, so read-only is enforced outside the agent too.
Store-and-Forward
If connectivity drops, data is buffered on disk and replayed in order on reconnect. Nothing already collected is lost to a restart or power loss, within the configured buffer window.

See the full security and trust details

Questions IT and controls teams ask

What operating systems and hardware does it run on?
A single 59 MB binary for Windows, Linux, or macOS, on x64 or ARM. The footprint is small: 2 cores and 2 GB of RAM handle roughly 5,000 tags, so a small VM on the plant network or a dedicated industrial PC is all it needs.
Does it run on Windows?
Yes, Windows is a first-class platform. MAJiK IoT Connect ships as a native Windows binary (x64), not a Linux container or a port. The installer registers it as a Windows service with automatic startup, graceful shutdown, and restart on failure, so it runs unattended on the VM or industrial PC your IT team provisions for it. The same agent ships as native builds for Linux and macOS too, on x64 and ARM.
Do I need Java or a separate gateway server?
No. MAJiK IoT Connect is a single compiled binary that embeds the runtime, all 20 protocols, the MQTT broker, the OPC UA server, store-and-forward, and a local UI. There is no JVM to install, patch, or tune, and no separate gateway server to license. That keeps it lightweight, handling thousands of tags on modest hardware.
Can I run it in Docker?

You can, but you usually do not need to. The agent is a single self-updating binary with no runtime dependencies: it installs as a service and restarts and updates itself in place, so there is no image to pull and nothing to orchestrate.

The difference shows up on Windows. Docker Desktop runs the container inside a Linux VM, so it sits a layer away from your OT network. If that Windows host is itself a VM on VMware vSphere, you end up reaching your PLCs through a container, inside a Linux VM, inside a Windows VM. The networking gets complicated and fragile, and often needs promiscuous mode enabled on the ESXi virtual switch, which many security teams leave off. Running natively as a Windows service avoids all of that and reaches the network directly.

On Linux, Docker is fully supported, with a published image and a Compose file.

When a single node is not enough, MAJiK IoT Connect also runs as a high-availability Kubernetes cluster, with one node per plant area collecting its own equipment and standing in for the others on automatic failover. See how the cluster works.

What happens if the broker or network slows down? Will I lose data?
Every stage is bounded, so the agent never grows memory without limit or silently drops data. A bounded in-memory queue sits between collection and publishing: if the broker slows it absorbs the burst and pushes backpressure upstream rather than growing without limit, and if a poll runs longer than its scan rate the next cycle is skipped instead of queued, so a slow PLC never builds a backlog. If the connection drops entirely, readings spill to an on-disk store-and-forward buffer, up to 1 GB by default and configurable, so nothing is lost while offline. When it fills, it evicts the oldest data first and always keeps the most recent readings. On reconnect the agent replays the buffer oldest-first and removes each record only after the broker confirms it, so order is preserved and the buffer drains back to empty on its own. Nothing is wiped on recovery, and nothing is dropped without first being delivered.
How do I install it, and is it secure?
The install script pulls a checksum-verified binary, and every agent runs with its own unique machine identity and a credential that rotates automatically, so there are no shared keys across agents or sites. Updates are signed and verified before they apply, and the agent makes outbound-only connections with no inbound ports to open.
How do I manage agents across multiple sites?
Manage each agent at the level your security allows: locally on the box (including air-gapped), across your plant network, or from the cloud console. Every level uses the same authenticated, outbound-only control plane, so you can push configuration, roll out verified updates, and watch agent and connection health, with no inbound ports to open.
Which protocols are supported?
20 industrial protocols natively, including EtherNet/IP, OPC UA, Siemens S7, Modbus, MTConnect, and FOCAS, with no per-driver licensing.See the full list of 20 protocols
Can it run on-premise or air-gapped?
Yes. The embedded broker, OPC UA server, and local buffer mean data never has to leave the line. It is built for air-gapped and security-sensitive sites.
Will it write to my PLCs?
No. Read-only access: it polls or subscribes to the tags you choose and never writes to your controllers.

Want the technical detail? See how MAJiK IoT Connect works.

“We are definitely benefiting from having access to accurate, real-time and historical machine information presented quickly and easily.”

Jeroen Ahsmann, Production Engineering, Blount International

Manufacturing AUTOMATION

Connect your first machine todayMinutes from install to real-time machine operating data flowing from the shop floor, designed to work seamlessly with MAJiK Visual Factory and the systems you already run.

Book a Discovery CallSee MAJiK Visual Factory