Skip to content
radkawarPublic

About

Self-hosted MDM for Linux fleets. Enrollment, profiles, disk encryption, lock and wipe, OS updates and remote assistance with each distribution's native tools.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

23 stars

Watchers

0 watching

Forks

Latest commit

 

History

704 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

lindm icon

lindm

License: Apache-2.0 Checks

lindm is a self-hosted MDM for Linux fleets. It uses each distribution's native package and system tools. You run the server yourself.

Dashboard with work that needs review and the latest recorded activity.

Screenshots and animations use synthetic demo data.

What it does

  • One-line or installer-file enrollment, with agents served by your own server.
  • TPM-backed disk encryption with escrowed recovery keys.
  • Remote lock, wipe and recovery wipe for lost devices.
  • Profiles with staged rollouts and two-person approval.
  • Vulnerability findings from vendor advisory feeds.
  • OS update windows.
  • Browser-based remote assistance with user consent.
  • A signed audit log and exports.
  • An MCP server for AI assistants.

Enroll devices

Choose a distribution, create a one-time code or a bounded provisioning token, and copy the install command. The device page shows enrollment, inventory and security findings separately.

Choosing an operating system and copying its enrollment command, then reviewing a demo device.

Configure a fleet

Publish a profile, review the affected devices and roll it out in stages. Review the pilot's results before advancing to the fleet.

Publishing a profile, reviewing impact, obtaining a second administrator's approval and advancing a completed demo pilot to the fleet.

Review vulnerabilities

Follow an advisory to its affected devices and review the finding before requesting a patch or accepting a risk.

Opening vendor advisories, their affected devices and a device's security findings.
Lost devices, remote assistance and administration

Respond to a lost device

Find the device, review a lock or wipe request and record the reason. Destructive actions require independent approval.

Reviewing a named lost device and its lock request before independent approval.

Ask to help

Choose the access, tools and time limit before asking the user for consent. This demo shows the request and consent states, not a live shared desktop.

Finding a device, reviewing remote assistance permissions and waiting for user consent.

Manage access

Create administrator accounts, define roles and review changes in the audit log.

Defining a read-only role, creating an administrator account and updating its access.

Distributions

x86_64: ✓ supported · ✗ not supported · not yet tested. Footnotes name feature limits.

Distribution / release Enrolment Profiles Encryption / TPM Lock & wipe OS updates Findings Assistance
Ubuntu 22.04 LTS ✓ ✓ 1 ✓ ✓ ✓ ✓ ✓
Ubuntu 24.04 LTS ✓ ✓ ✓ ✓ ✓ ✓ ✓
Ubuntu 26.04 LTS ✓ ✓ ✓ ✓ ✓ ✓ ✓
Debian 12 ✓ ✓ ✓ ✓ ✗ 2 ✓ ✓
Debian 13 ✓ ✓ ✓ ✓ ✗ 2 ✓ ✓
Fedora 43 ✓ ✓ 3 4 ✓ ✓ ✓ ✓ ✓
Fedora 44 ✓ ✓ ✓ ✓ ✓ ✓ ✓
RHEL 9 ✓ ✓ ✓ ✓ ✓ ✓ 5 ✓
RHEL 10 ✓ ✓ ✓ ✓ ✓ ✓ 5 ✓
Rocky Linux 9 ✓ ✓ ✓ ✓ ✓ ✓ ✓
Rocky Linux 10 ✓ ✓ ✓ ✓ ✓ ✓ ✓
AlmaLinux 9 ✓ ✓ ✓ ✓ ✓ ✓ ✓
AlmaLinux 10 ✓ ✓ ✓ ✓ ✓ ✓ ✓
Linux Mint 22.3 ✓ ✓ ✓ ✓ 6 ✗ 7 ✓ 8 ✗ 9
Pop!_OS 24.04 LTS ✓ ✓ ✓ ✓ 6 ✗ 7 ✓ 8 ✗ 10
Arch Linux (rolling) ✓ ✓ ✓ ✓ ✓ ✓ ✓
Omarchy 4.0.4 ✓ ✓ 4 11 ✓ 12 ✓ 13 ✗ 14 ✗ 15 ✗ 16
openSUSE Tumbleweed (rolling) ✓ ✓ ✓ ✓ ✓ ✓ ✓

arm64 builds are available for Ubuntu 22.04 LTS, Ubuntu 24.04 LTS, Ubuntu 26.04 LTS, Debian 12, Debian 13, Fedora 43, Fedora 44, RHEL 9, RHEL 10, Rocky Linux 9, Rocky Linux 10, AlmaLinux 9, AlmaLinux 10, openSUSE Tumbleweed (rolling); their distribution pages list the tested features.

Encryption and wipe require an encrypted installation. TPM2 unlock needs a compatible TPM and boot setup. Wipe erases encryption keys, not physical drives. Assistance requires a compatible desktop and user consent. Findings cover packages in the vendor's advisory feed. Extra assistance tools depend on the desktop.

Server install

Server installation is separate from device support above. The table distinguishes maintained installer recipes from full lifecycle qualification. New platforms are connected-only; arm64 server qualification is not available. See the installation guide for prerequisites and proof records.

Server platform Architecture PostgreSQL Packages Install mode Lifecycle
Ubuntu 22.04 LTS x86_64 16 PGDG Connected only Qualified
Ubuntu 24.04 LTS x86_64 16 Distribution Connected and air gap Qualified
Ubuntu 26.04 LTS x86_64 18 Distribution Connected only Qualified
Debian 12 x86_64 16 PGDG Connected only Qualified
Debian 13 x86_64 17 Distribution Connected only Qualified
RHEL 9 x86_64 16 Distribution stream Connected only Qualified
RHEL 10 x86_64 16 Distribution Connected only Qualified
Rocky Linux 9 x86_64 16 Distribution stream Connected only Qualified
Rocky Linux 10 x86_64 16 Distribution Connected only Qualified
AlmaLinux 9 x86_64 16 Distribution stream Connected only Qualified
AlmaLinux 10 x86_64 16 Distribution Connected only Qualified

Install

Build a release with your own signing keys, then install the bundle on your server. Installation from a prepared bundle is the five-minute part. The build takes longer, depending on your machine and network. See the installation guide for prerequisites and server setup.

  1. Install the pinned tools from CONTRIBUTING, then clone and build:

    git clone https://github.com/radkawar/lindm.git
    cd lindm
    make bootstrap
    make release-keys
    make release

    Keep the release keys and their encryption passphrase on the signing workstation. Read self-built releases and signing keys for key custody and public trust files.

  2. Copy the verified artifacts/release/ bundle and public trust files to the server. From the bundle directory, run:

    sudo ./install.sh --release-key-file "$TRUSTED_RELEASE_PUBLIC_KEY" \
      --release-key-id "$RELEASE_KEY_ID" --backup-recipient-file "$BACKUP_RECIPIENT_FILE"

    Supply the stable HTTPS origin when prompted.

  3. Trust the deployment CA in your browser, then open the setup URL printed by the installer. Read the one-use setup code as root from /var/lib/lindmd-operations/setup/code. Enter the code, create the owner account and register a user-verifying passkey.

  4. In Settings, confirm that the agent repository is Ready. Select Enroll, choose the device's operating system and copy the install-and-enroll command. Run it on a second device. The console shows the device as Enrolled.

How it works

lindmd is a Go server with PostgreSQL as its store and work queue. It serves the React console and Connect RPC on separate administration and device TLS listeners. The device agent separates an unprivileged network process from a root executor through a protected Unix socket. The executor checks signed authority and owns device identity, trust and durable execution state. See architecture for the security boundaries.

Contribute

See CONTRIBUTING for development and DCO sign-off, and the roadmap for planned work. Report vulnerabilities privately through SECURITY. The code of conduct applies to project discussions.

Documentation · Enrollment · Operations · Platform details

lindm's original code is licensed under Apache-2.0. Third-party code and data retain their own licenses. See NOTICE.

Footnotes

  1. Systemd unit definitions require a newer systemd. ↩

  2. Security-origin selection is not implemented for this update runner. ↩ ↩2

  3. Package profiles require a newer DNF. ↩

  4. Password-policy profiles are unavailable with this PAM stack. ↩ ↩2

  5. Findings cover verified Red Hat packages declared for the selected product stream. Other packages and unusable vendor components are listed as unchecked. ↩ ↩2

  6. Account locks and wipe work; the desktop does not report its screen-lock state. ↩ ↩2

  7. Automatic OS updates are not supported on this release. ↩ ↩2

  8. Findings cover upstream base packages only. ↩ ↩2

  9. The desktop has no screen-sharing or remote-control portal. ↩

  10. Stock COSMIC hides consent buttons; newer portal support alone does not enable assistance. ↩

  11. Firewall profiles require firewalld rather than the installed ufw. ↩

  12. TPM2 unattended unlock is unavailable with this boot setup. ↩

  13. Account locks and wipe work; screen locking is unavailable. ↩

  14. System upgrades must use the distribution's own updater. ↩

  15. No vendor advisory feed covers this distribution. ↩

  16. The desktop's notification surface has not been verified to show safe consent buttons. ↩

About

Self-hosted MDM for Linux fleets. Enrollment, profiles, disk encryption, lock and wipe, OS updates and remote assistance with each distribution's native tools.

Topics

Resources

Code of conduct

Contributing

Security policy

Stars

23 stars

Watchers

0 watching

Forks

Releases

Packages

Used by

Contributors

Languages