Lancache

Lancache is a self-hosted caching proxy that stores game download content on your local network to reduce internet bandwidth.

  • Downloaders
  • Network Services
  • Other
  • Tools & Utilities
Lancache is a self-hosted caching proxy that stores game download content on your local network to reduce internet bandwidth. For any network with more than one PC gamer, it serves repeated downloads from the local cache, drastically cutting bandwidth consumption.

Platform availability

Available on 3 of 10 platforms

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

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.

56/100 Fair

Maintained
71last commit 43 days ago
Popular
59911 GitHub stars
Easy to install
553 install platforms, install notes, Docker image
Light to run
1016 GB minimum RAM

Availability: platform listings confirmed today, links checked 10 days ago

GitHub stars
911
Open issues
42
Last commit
2026-10-09
Activity
stale

Checked 2 days ago - source: GitHub (lancachenet/monolithic)

Resources & Compatibility

Minimum requirements: 16 GB RAM, 8 CPU core(s), 2560 GB disk. ARM (e.g. Raspberry Pi) is not supported.

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

First-install notes

  • Install Linux tools first Install curl, jq, unzip, and wget with apt-get (the package installer). These download and setup tools are needed for SteamPrefill, and missing them can make the install script fail. source
  • Fill in scheduled job details Edit the systemd (Linux background job) service file and replace User, WorkingDirectory, and ExecStart with your real user and paths. If you leave the placeholders, SteamPrefill may not start when the scheduled job runs. source
  • Turn on the scheduled job After setup, run the provided systemctl commands (the Linux tool for starting background jobs) to enable and start steamprefill.timer. This makes SteamPrefill run on schedule and after reboot, so it can keep games preloaded automatically. source

Fetched 45 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

What steps are needed to start Lancache with Docker Compose and point the network at it?

Clone the Lancache docker-compose repository, edit the .env file, run sudo docker compose up -d, and configure your router to serve only lancache-dns.

How can I put Lancache cache storage on a separate disk on Linux?

A self-hosted post covers the default Lancache data location on Ubuntu and explains how to add a separate disk for cache storage on Linux.

Can SATA port or disk layout make Lancache slower?

A thread suggests slower speed may be related to the OS SSD being on a SATA2 port, notes cache files were stored on a RAID0 array, and asks whether installing Lancache on the RAID drive could help.

Why does a host-mode Lancache container need IPv6 handled at the network level?

LANCache Manager disables IPv6 inside bridge-mode prefill containers to prevent a problem. Docker does not allow that with host networking, so a host-mode container needs IPv6 handled at the network level instead.

Answers sourced from lancache.net, regix1.github.io, www.reddit.com, www.reddit.com

Community

Collected 54 days ago - public community threads