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

Windows

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 installed

Linux

# 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.service

nexus\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 whole configuration — tags, devices, screens, alarms, reports, projects.
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_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 licence.
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.

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.