A focused local workspace.
Discover servers, pair once, browse folders, search, upload, download and resume interrupted transfers.
Secure local network
Move files between Desktop, Android, browser and always-on servers without making someone else’s cloud the middleman. Localynk keeps the transfer path on networks you control.
How it works
Localynk is built around an explicit trust model: run a server, approve a device, then grant only the shares that device should see.
Use Desktop Server for a visual setup, or Headless Server for Proxmox, Debian and Ubuntu.
Desktop, Android and Web clients request access. You decide which devices become trusted.
Grant browse, download, upload or delete rights per shared folder, then move files directly across your network.
Localynk ecosystem
The same Localynk identity and Protocol 2 model across client, server, mobile and headless deployments.
Discover servers, pair once, browse folders, search, upload, download and resume interrupted transfers.
Manage pairing, shares, permissions, transfers, diagnostics and Web Admin from a desktop UI.
Discovery, pairing, share-aware browsing and resumable transfers in a mobile client built for Protocol 2.
Qt-free headless service, systemd integration, health checks, database backups and browser-based administration.
Open the complete Proxmox guideSecurity model
Localynk separates administrator access from device access. Admin sessions use password + TOTP 2FA; trusted clients use device bearer sessions with share-level permissions.
Always-on Localynk
Run the Headless Server in an unprivileged Debian 13 LXC with systemd, Web Admin, health checks and scheduled SQLite backups. Mount large storage separately and keep the application container small.
root@localynk:~# ./proxmox/INSTALL-PROXMOX.sh
✓ dependencies verified
✓ localynk.service enabled
✓ backup timer enabled
✓ health check passed
root@localynk:~# localynk-ctl health
status: ok
protocol: 2
port: 8742Release center
Questions
The important parts of Localynk are intentionally explicit: where it runs, who gets access, and what “production ready” means for this RC.
No mandatory cloud relay is required for the normal Localynk transfer path. It is designed to move files directly across networks you control, such as your LAN or private VPN.
Yes, through a private VPN such as Tailscale. Automatic LAN discovery may not cross the VPN, so manually enter the Localynk server address.
No. The built-in Localynk HTTP server is intended for trusted LAN, Tailscale or another private VPN. Do not directly port-forward TCP 8742 to the public Internet.
The BuildFix9 source, security behavior, API and packaging definitions passed the current audit. Native installers still need to be compiled and qualified on their target operating systems before being published as final binaries.
Use a saved recovery code, or on a Headless/Proxmox server run localynk-ctl reset-2fa from the server console and enroll a new authenticator.
Localynk
Desktop. Android. Browser. Proxmox. One private-first file sharing system for the network you already own.