TL DeviceSDK

TL DeviceSDK is a toolkit that allows different pieces of Thorlabs equipment to communicate with your computer.

  • Home Automation
  • Tools & Utilities
TL DeviceSDK is a toolkit that allows different pieces of Thorlabs equipment to communicate with your computer. It acts as a bridge, enabling you to build custom software to control and coordinate your laboratory devices through a single, unified interface.

Platform availability

Available on 0 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

53/100 Fair

Maintained
91last commit 97 days ago
Popular
165 GitHub stars
Easy to install
250 install platforms, install notes, Docker image
Light to run
No data

Based on 3 of 4 factors.

GitHub stars
5
Open issues
3
Last commit
2026-08-16
Latest release
@devicesdk/[email protected]
License
AGPL-3.0
Activity
stale

Checked yesterday - source: GitHub (device-sdk/devicesdk)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 54 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Install via WinGet On Windows, install TL_DeviceSDK with WinGet using winget install Thorlabs.ThorlabsDeviceSDK. source

Fetched 48 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I start the DeviceSDK server locally?

Use Docker Compose to run one container that exposes port 8080 for the API, WebSockets, and dashboard. The first registered account becomes the admin.

Where does DeviceSDK store its data, and what should I back up?

All persistent state lives in the data directory, default /data, including the SQLite database, device scripts, and firmware images. In Docker Compose, mount a host directory such as ./data to /data.

How do I stop new users from registering after setup?

Set the ALLOW_REGISTRATION environment variable to false. This closes sign-ups once your account already exists.

What environment variable must I set for an HTTPS reverse proxy?

Set SECURE_COOKIES to true when the server is served behind an HTTPS reverse proxy.

How can I run several DeviceSDK servers on the same LAN?

Give each server a different MDNS_HOSTNAME. Set MDNS_ENABLED to false if you do not want mDNS advertisement.

Do updates force breaking changes?

Releases are intended to be infrequent, and you can skip an update if you do not need it. Opt-in compatibility flags are used when behavior must evolve so you can migrate on your own schedule.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads