Platforms
The same gateway on a server rack or a single-board computer.
Nexus is one C++ service with no runtime to install alongside it. That is why the same build runs on a Windows plant server and on an ARM64 panel behind a machine: the same gateway, with no cut-down edge variant and no separate feature list.
Specifications
Version 2026.20. Describes Raylux as built.
| Nexus | Value |
|---|---|
| Windows | Server 2019+ or 10/11, 64-bit — packaged installer |
| Linux | .deb for Debian/Ubuntu, .rpm for Fedora/RHEL — x86-64. ARM64 on request |
| Runs as | A Windows service, or a systemd unit |
| Installs to | /opt/raylux on Linux — bundles its own Python |
| Dependencies | None to install. No database server, no OPC server, no separate runtime |
| Clients | Value |
|---|---|
| Spectrum | Any current browser — nothing installed on the machine |
| Studio | Windows 64-bit, installed per engineer |
| Lens | Windows 64-bit, installed per panel |
| Mobile | Spectrum in the phone or tablet browser |
| Footprint | Value |
|---|---|
| Measured | ~38 MB resident on ARM64 |
| Under | 131 device tags, one PLC, historian and alarms running |
| Headless build | No Qt, no desktop — gateway and CLI tools only |
| Storage | Historian writes locally; no external database |
Three shapes
The same service, sized to the job.
Plant server
Nexus on a Windows server or a Linux VM, polling the plant, holding the history and serving every operator screen in the building. Engineers connect with Studio; operators open a browser.
One install per site. Adding a client is opening a tab, not licensing a seat.
Panel
An ARM64 or x86 panel running Nexus locally and displaying its own screens. The panel keeps working when the network does not, because the gateway it talks to is the box it is bolted to.
Running today on a single-board ARM64 panel against a live PLC. See the deployment note.
Headless edge
A skid or a cabinet with no screen at all. Built without Qt, Nexus is a gateway and nothing else: it polls, records, alarms, and answers the API.
No compositor, no browser engine, no desktop pulled in behind it.
Why it fits on small hardware
One service instead of a stack
The tag engine, historian, drivers, alarms, reporting and the web server are one process. There is no database server to provision, no OPC server to license, and no application server underneath.
Native code
Nexus is C++. The one runtime it uses, its own Python, ships inside the package rather than as something to install beside it, and there is no container image. That is most of what makes a conventional SCADA stack too heavy for a panel.
Next step
Put it on a real PLC this afternoon.
Everything is free to download and free to try. Start the trial and Raylux is completely unlocked for two hours: every driver, every module, unlimited tags and clients, nothing withheld. When the two hours are up you restart it, as often as you like.