Raylux 2026.21: A new look across Raylux, Iris, the built-in assistant and Designer

Raylux 2026.21 is a big one. Every product has a new, brighter look; Iris, the built-in assistant, is complete; and the designer gains a node editor for scripts, a much better binding editor and a long list of new screen components.

Does this affect me?

• Upgrading a running gateway: install over 2026.20 as usual. Projects, tags, history, users and alarm configuration are kept. Configuration changes still apply live; nothing in this release asks you to restart the gateway to switch a feature on.
• Your screens: existing projects keep working. Components you already placed keep their old look as a variant, so nothing on an operator screen changes until you choose the new style.
• Iris: every Iris feature is off until an administrator turns it on and adds an AI provider. Nothing is sent anywhere by default.
• Licensing: licenses issued from this release on are tied to several pieces of the machine's hardware (network adapter, system board, data disk), and at least two must still match. Replacing a single part does not stop a gateway. See the Licensing section below.

A new look across Raylux

• One light, readable design in every product. The designer, the plant-floor client, operator screens, the configuration console and the manual now share one design, with a dark Night theme available in the designer.
• New typeface. Geist and Geist Mono replace the previous fonts in every product, in exported PDFs and in the installer.
• Studio Home replaces the gateway hub. Each gateway is a tile with a live health trend, and the three main jobs (design, run, configure) are one click away.
• Per-project brand kit. Set a project's logo, color, header style, density and theme once; operator screens and the plant-floor client follow it.
• Templates to start from. A water reclamation plant, a pump station, a barn ventilation project, a starter shell and eight screen templates ship in the box. Save your own screens or selections as templates and share them through a company template store.

Iris, the built-in assistant

• Operator chat. Operators can ask Iris about the plant from an operator screen or the plant-floor client, answered from live data.
• Designer assistant. An Iris panel in the designer suggests changes and new screens, checked before you see them.
• Every change is a proposal. Iris never edits a project on its own. Changes arrive as proposals that a person approves, and any approved change can be undone in two clicks.
• Agents. Build agents in the designer that run on the gateway, for example to look into an alarm's likely cause before the notification goes out. Every run can be reviewed in the configuration console.
• Summaries of alarms, tags and other subsystems, on demand.
• Your own tools, in Python. Add tools Iris can use, written in Python and run in a restricted sandbox.
• Anthropic (Claude) as a provider option, alongside local and OpenAI-compatible models.
• Hardened before shipping: tested against misuse, under load, and with every call recorded in the audit log.

Designer

• Python or Nodes for every script. Any script can be written in Python or built visually in the node editor, right inside Scripting.
• Alarm pipelines in the same node editor, redrawn and easier to follow.
• Binding editor reworked. Apply and Clear can be undone, switching a binding's kind asks first, and errors say what is wrong.
• Report editor fixes: no more crash when deleting a selected item, a picker for data sources, and a form for tag-history sources.
• Set a script's trigger tag and interval from the designer, and create expression tags without leaving it.
• Names are checked. New scripts, views, pages and Iris agents refuse a name or route that is already taken.

Screen components

• Trend Explorer: stacked plots, a pen table, brushing, export, comparing and aligning batches, alarm events, notes and saved charts.
• Video: a Video Player component and camera setup, with cameras found automatically on the network (ONVIF). The gateway relays the stream, so operator stations do not connect to cameras directly.
• Map: plain and street maps, plus satellite from your own tile server, with markers and pipelines that take the color of the worst active alarm. Upload a street map file to the gateway and it is served from there, so it works without internet access.
• New process indicators: an improved Moving Analog Indicator, Loop Indicator, Alarm Banner, Sequence Indicator and PID faceplate.
• Tables and lists: Tag Table, Editable Grid, Event Log, Tree and Tree Table.
• More components: state timeline, on-screen keypad, schedule editor, document viewer, and eight new basic components.
• Popups can open as a dialog, a bottom sheet or a side panel.
• Equipment symbols: a tank agitator, a P&ID-style tank, quality captions on symbols, and clearer valve symbols.

Plant-floor client

• Follows the project's theme and branding, with a branded start-up screen.
• A branded waiting screen replaces the browser's error page while the gateway is unreachable, and the client reloads by itself after a page fails.
• Closing a windowed view returns to the hub, and focus outlines appear only when using the keyboard.

Gateway

• Safer operator writes. Values out of range, fractional values for whole-number tags, and invalid numbers are refused before they reach a PLC, with a clear message to the operator.
• Alarms: a value with bad quality holds the alarm's current state instead of changing it, and shutdown no longer risks losing alarm records.
• Historian: writes the database refuses are kept and replayed, not dropped.
• Drivers: fixes for DNP3 status flags and event data, FINS/TCP frame handling, Siemens S7 word addressing, OPC UA value conversion, and connections closed cleanly after a network fault.
• Reports: a failed delivery is reported as a failed run, and email and notification sends time out instead of hanging.
• Renaming a tag or folder keeps its security, members and device binding.
• Security hardening of the web server, WebSocket connections and the designer's embedded pages.
• Scripts can read the live alarm list.

Licensing

• A license is tied to more than one piece of hardware. The gateway records the network adapter, the system board and the data disk, and at least two must still match. Replacing one part keeps the gateway licensed.
• The License page now lists what your license includes and no longer shows the machine fingerprint.
• Moving to new hardware is done from the License page: unactivate on the old machine, then activate on the new one. If the old machine has failed, contact [email protected].
• What did not change: paid licenses never expire, and a license covers every release of the year it was bought.

Installing

• Windows: Windows Server 2019 or later, or Windows 10 or 11, 64-bit. The gateway installs as a Windows service and starts on boot. Installing over an earlier release keeps your projects, tags, history and users. These downloads are not code-signed yet, so Windows will warn you the first time you run one.
• Linux: x86-64. Ubuntu 24.04 or later, Debian 13 or later, Fedora 39 or later, or RHEL, Rocky or Alma 10 or later. Install over an earlier package to upgrade; your data in /var/lib/raylux is kept. Studio and Lens are Windows-only; the gateway serves operator screens to any browser. The packages are not signed yet.

Downloads

• RayluxSetup-2026.21-x64.exe: the whole system for Windows (gateway, designer and plant-floor client). Start here if you are not sure.
• Raylux-2026.21-x64.msi: the gateway on its own for Windows, for scripted or unattended installs.
• Raylux-Studio-Setup-2026.21-x64.exe: the designer, for an engineer's workstation.
• Raylux-Lens-Setup-2026.21-x64.exe: the plant-floor client, for operator stations.
• raylux-nexus_2026.21_amd64.deb: the gateway for Debian and Ubuntu: sudo apt install ./raylux-nexus_2026.21_amd64.deb
• raylux-nexus-2026.21-1.x86_64.rpm: the gateway for Fedora and RHEL: sudo dnf install ./raylux-nexus-2026.21-1.x86_64.rpm