Raylux 2026.19: Licensing, Project history (source control) and Projects

Raylux 2026.19 is the first release since 2026.12. It adds licence keys, keeps a history of every project change that you can browse, compare and roll back, lets you copy and move more of a project as JSON, makes named queries much faster, and fixes the problems we found walking the getting-started tutorial click for click. We recommend it for every gateway.

Licensing

• Licences are now activated with a licence key. Each gateway gets one key (RLX-XXXX-XXXX-XXXX). In the configuration console, under License, you enter the key and either activate online or download a request file that carries it. Your existing licence keeps working; nothing needs to be reissued.
• Online activation and the activation page open with the Raylux licence store. Until the store opens, the Activate online button and the activation page on rayluxscada.com are not available yet. To license a gateway in the meantime, contact us and we will license it for you.
• A gateway licensed with a licence key checks its licence once a day when it can reach the internet, whether it was activated online or with a request file. It contacts the Raylux licence server and sends the licence key, licence ID, a hardware fingerprint, the computer name and the Raylux version. It sends no plant data. A gateway that cannot reach the internet is never affected: it keeps running exactly as before. Blocking the connection at your firewall is fine.
• A licence can be moved to another computer. Unactivate it on the old gateway first; the configuration console gives you a receipt file if that gateway is offline.
• If Raylux ever withdraws a licence key, for example after a refund, the gateway shows a banner with a seven-day countdown that says why and who to contact, before anything stops.
• The configuration console warns before an upgrade the licence does not cover. The License card shows "Covers: every release through 2026", and once the year has passed it tells you that a newer year's release would run unlicensed until the licence is extended.

Project history (source control)

• The gateway now keeps a history of its projects. Every project save is recorded, and you can commit changes with a message. It lives in the gateway's data folder; there is nothing to install or set up.
• The configuration console has a Source Control page. Browse the history, see exactly what changed in each screen or file, restore a single file to an earlier version, undo a commit, and create or switch branches. Every one of these shows you what it will change and asks before doing it.
• Studio has a Source Control panel showing what has changed since the last commit, with a diff for each file and a Commit button.
• Committing needs the new Source Control permission, which Administrators and Developers have by default. A commit is always recorded under the name of the person signed in.
• Files edited by hand outside Raylux are shown, never committed.

Projects

• More of a project can be copied and moved as JSON. In Studio's Project Browser, named queries, pipelines, reports, event and project scripts, and style classes now have Copy JSON, Export to file, Paste JSON and Import from file, alongside screens and tags. An import that clashes with an existing name asks whether to overwrite or skip.
• Named queries are much faster on large projects. A query polled by an open screen no longer re-reads the whole project each time.
• Fixed a rare problem during a project save, where a request arriving at the same moment could briefly see no screens, or a mix of old and new files.

Designer and screens

• The Tag Editor no longer clears a tag's alarms when you save an unrelated change.
• The Tag Editor no longer switches a tag's public read access off every time you save; "gateway default" now stays that way.
• The Tag Editor fits on a 1080p screen; its pages scroll instead of pushing Save off the bottom.
• Toggles and buttons no longer ask for an electronic signature on tags that do not require one.
• Operators are asked to sign in when a screen's tags need it, instead of seeing dashes with no way to sign in.
• Opening a project's address opens its first screen, instead of "No screens found".
• A tag's initial value is kept after a gateway restart.
• The first-run New Project form in the Hub offers its starting templates.
• Tank scale labels are no longer cut off.

Security

• The gateway's own HTTPS certificate now names the computer it runs on, so modern clients accept it once it is trusted. The gateway also records the certificate's fingerprint in its log at start-up, and Studio's trust prompt tells you where to check it.

Lens and installers

• Lens returns to its Hub after Ctrl+Shift+H. The window previously closed and Lens kept running with nothing on screen.
• The Windows installers carry the Raylux artwork, and Raylux has its own icon in Apps & Features.

Does this affect me?

• Everyone upgrading from 2026.12 — install as usual. Projects, tags, history, alarms and users are kept. The first start creates the project history in the data folder.
• You want the improved HTTPS certificate on an existing gateway — the gateway keeps its current certificate on upgrade. To get the new one, stop the gateway, delete certs/nexus.crt and certs/nexus.key from its data folder and start it again; Studio asks once to trust the new fingerprint.
• Your gateways sit behind a firewall — the daily licence check is an outbound HTTPS connection to rayluxscada.com. Allowing it is optional; blocking it changes nothing.
• Existing licences — keep working unchanged, and a licence installed without a key never contacts the licence server. Licence keys apply to licences issued from now on.

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