LaboraX

The problem

Licensing by hand does not survive growth. Keys get issued over email, expiry dates live in someone's head, and there is no reliable way to tell whether an install has been cloned onto a second machine. Every one of those gaps is revenue that quietly leaks.

Laboratories also cannot be held hostage to connectivity. An instrument bench that stops working because a licence server is unreachable is worse than no licensing at all — so validation had to keep working offline.

What we built

• Laboratory client registry with sequential lab codes and soft‑delete, so licence history survives a departing client
• Time‑limited licence keys with an explicit lifecycle — unused, active, expired, revoked
• Machine‑bound activation: one machine per licence, enforced at activation time
• RSA‑signed activation tokens the laboratory system validates locally, so a bench keeps working offline
• Filterable, paginated audit log of every administrative action, by event type, entity and date
• Dashboard: laboratories registered, licence counts by state, and recent activity at a glance
• Three‑container Docker stack that runs on hardware as small as a Raspberry Pi

LaboraX is an internal administration tool, not a public product — there is no sign‑up page to link to, and the deployment details are deliberately left out here.