Appearance
Where files live
Raylux keeps program files and data strictly apart. Program files are replaced on every upgrade and removed by an uninstall; the data directory is neither.
Program files
text
C:\Program Files\Raylux\
nexus\
raylux-nexus.exe Nexus, registered as the RayluxNexus service
fonts\ fonts embedded into report PDFs
web\ the operator runtime (Spectrum)
python\ the bundled Python 3.14t runtime
studio\ Raylux Studio, if installed
lens\ Raylux Lens, if installedtext
# Installed from the .deb
/opt/raylux/bin/raylux-nexus
/opt/raylux/bin/python/ the bundled Python 3.14t runtime
/opt/raylux/lib/ bundled libraries
/opt/raylux/share/raylux/web/ the operator runtime (Spectrum)
/opt/raylux/share/raylux/fonts/ fonts embedded into report PDFs
/lib/systemd/system/raylux-nexus.service
# Installed from source (prefix /usr/local)
/usr/local/bin/raylux-nexus
/usr/local/share/raylux/web/
/usr/local/share/raylux/fonts/
/usr/local/lib/systemd/system/raylux-nexus.servicenexus\python and nexus\fonts are load-bearing names
Nexus finds both relative to its own executable. That is what lets you relocate the whole installation. Move or rename either directory and you must point at it with RAYLUX_PYTHON_HOME or RAYLUX_FONTS_DIR instead.
The data directory
| Platform | Location |
|---|---|
| Windows | C:\ProgramData\Raylux |
| Linux | /var/lib/raylux |
This is what you back up — Backup and restore lists every file in it and what each backup method covers. It survives uninstall.
| File or folder | Contents |
|---|---|
raylux_project.json | The gateway configuration — tags, devices, alarms, reports, and Nexus's own settings. |
projects/ | The projects, one file per screen, script, named query and the rest. |
.git/, .gitignore | The source-control history of the two entries above. Managed by Nexus. |
raylux_users.json | User accounts and password hashes. |
raylux_refresh_tokens.json | Active sign-in sessions. |
raylux_secrets.json | Stored passwords for devices, email, SMS, databases and SSO, and the key that signs sign-in tokens. Not encrypted — protected by file permissions. |
raylux_history.db | Recorded process history. Usually the largest file here. |
raylux_history_buffer.db | History not yet written to its final destination. |
raylux_audit.db | Who changed what, and who wrote to which tag. |
raylux_ai.json | Iris settings. Holds no API key. |
raylux_ai.db | Iris usage, transcripts, agent runs and change proposals. |
raylux_mcp_keys.json | Iris MCP API keys, stored as hashes. |
raylux_alarms.db | Alarm state and history. |
raylux_system.db | Nexus internals. |
raylux_user_prefs.db | User preferences. |
raylux_memory.db | Current values of persistent memory tags. |
raylux_esignature_chain.db, raylux_esignature_secret.key | The electronic-signature record and the key that seals it. |
raylux_license.raylux-license | The installed license. |
device_discovery_state.json | Whether the Find devices banner on the Devices page has been used or dismissed. See Finding devices. |
raylux_first_boot.txt | The one-time commissioning token. Inert once an administrator exists — delete it. |
certs/ | TLS certificate and private key. |
logs/raylux_nexus.log | The rotating Nexus log. |
downloads/ | Studio and Lens setup programs, served by the Downloads page. |
assets/ | Images and files uploaded to projects. |
templates/ | Project templates. |
report-output/ | Where scheduled reports with a file target are written. A report's file path is relative to this folder; a path that leaves it is refused. |
FTP delivery credentials are set by hand for now
A report's FTP target (ftpUrl, ftpCredentialRef) is a JSON-only setting; there is no editor for it yet (it is filed with the report editor). The credential must be an entry named report-ftp:<name> in raylux_secrets.json, whose value is user:password. Any other name, including the SMTP, device and AI keys stored in the same file, is refused. Until the editor exists, add the entry to raylux_secrets.json by hand while Nexus is stopped.
The electronic-signature chain is verified, with one limit
Nexus re-checks every record of raylux_esignature_chain.db when it starts and whenever an administrator calls GET /api/audit/esign/verify. A changed, reordered or removed record in the middle is reported. Records deleted from the end of the chain cannot be detected from inside the file, because nothing later refers to them. Keep an external copy of the chain's latest hash (for example in a backup or a ticket) if you need to prove nothing was cut off the end.
Restrict access to this directory
It holds the TLS private key, every stored device credential and all your history. On Windows it inherits C:\ProgramData permissions; tighten them if non-administrators can log on to Nexus.
Moving the data directory
Set RAYLUX_DATA_DIR, or pass --data-dir. On Windows the service has the path baked into its registration, so change it by re-registering the service rather than by setting a variable a service will not see.
Stop Nexus, move the directory, then start it again — nothing in it is tied to its own path.
Logs
Nexus writes logs/raylux_nexus.log in the data directory and rotates it. On Linux the same lines also reach the journal (journalctl -u raylux-nexus).
Administrators can read the log in the browser without server access, on the Nexus's Logs page.