A free CMMS that runs on your own PC

What works today

Everything on this list is in the current build and passes automated tests against a real server. It is early: enough for a technician to work a job from the phone, not yet a whole maintenance department. The hands-on test on real phones is the next step.

• One server program for Windows, macOS and Linux, plus a Docker image. It runs on a PC in your plant and keeps the database and the backups there.
• HTTPS inside the plant, with its own certificate authority. A phone trusts the server by scanning the plant QR code; browsers on your PCs get the certificate from the server's trust page.
• A Mac app with an 8-step setup assistant: server, certificate, administrator, plant, people, first phone, first work order, backup. Signed with an Apple Developer ID and notarized; not in the Mac App Store.
• A web app, plus iPhone and Android apps in English and Spanish. The phone apps are test builds (TestFlight and Google Play internal testing), not in the public stores. The Spanish is a draft until a native speaker reviews it.
• Work orders on the phone: mine or all, start, put on hold with a reason, done, close, reopen, and the full status history of each order. Creating them in the web app is the first item on the list below.
• Offline on the phone: the phone keeps its own copy and a queue of your changes (encrypted with a key per person) and sends them when the server is back in reach. Each change lands exactly once. After 72 hours without the server (adjustable) it asks for an online sign-in.
• People and sign-in: four roles (operator, technician, manager, admin), password sign-in with a limit on failed attempts, invite codes and QR codes for phones, sessions and devices you can revoke, and an audit log.
• Backup and restore: a snapshot with one button, and a change journal written out every few seconds, so a restore brings back everything up to the last written change.

1. Work orders from the web app: create and edit them with asset, priority, assignee and due date; comments and photos on each order.
2. Assets and locations with photos, QR labels printed in one go, and CSV import of assets and people.
3. Requests without signing in: anyone scans the QR on a machine and reports a problem; a manager turns it into a work order.
4. Preventive maintenance: calendar schedules with checklists that open work orders on time.
5. Notifications in the app and on Telegram.
6. Documents: manuals and drawings on the machine they belong to, with revisions.
7. Windows installer, updates from the admin screen, and export of everything to CSV and JSON.
8. Parts and stock: a parts catalog, stock that follows every use and receipt, minimum levels, labor and cost per work order.
9. Later, and optional: a hosted copy on our servers, the LK On link, and AI that answers from your manuals (free with your own AI key).

Why run it on your own PC

The job UpKeep, MaintainX, Limble or Fiix do, without a per-seat bill, a database admin or an internet connection.

With LK On (planned)

LK On, our backup touchscreen for the machine, already logs alarms and machine stops. The plan is for LK Up to pick them up, so the stop your operator saw becomes a record on the right machine. LK Up does not need LK On; the device is only an optional source of machine events.

The contract between the two will be public. What LK On is →

Free core. Never per seat.