LitePan: Multi-Cloud-Drive Aggregator with WebDAV, STRM, and FUSE Mount

What LitePan Aggregates and Who It Targets

Managing a home media library across multiple cloud drives means logging into each service separately, searching each one individually, and running separate media server integrations for each. LitePan addresses this by providing a single web interface that aggregates multiple cloud drive accounts under unified management. A user with files spread across several storage services can browse, copy, and organize from one place.

The target user is a home media server operator who uses Emby or Jellyfin and stores content on cloud drives rather than local disks. LitePan handles the integration between cloud storage and the media server through STRM file generation and FUSE local mounting, removing the need to build that integration manually. The current release is the Go rewrite, labeled v0.5.6-Beta; the Python predecessor is archived in a separate repository named LitePan-old.

Core Features: Cross-Drive File Operations and Instant Transfer

LitePan provides several features that go beyond simple file browsing. The cross-drive instant transfer attempts to move files between cloud drives without downloading and re-uploading them: if the target drive supports it, the transfer is completed server-side at the cloud provider level. If instant transfer is not supported, LitePan falls back to a standard download-then-upload path.

The STRM generation feature creates .strm files that point to the direct streaming URLs of media files on the cloud drives. Emby and Jellyfin read these .strm files and stream the content directly from the cloud without copying it to the local server. LitePan can also write NFO metadata files and download poster art, enabling a full media library poster wall with content that remains stored remotely.

Directory organization uses TMDB recognition to identify media titles before archiving them into folder structures. The README describes a workflow that shows the TMDB-identified results for preview before committing the organization, which prevents misclassification from corrupting the library silently.

Deploying LitePan with Docker Compose

LitePan requires Docker and runs as a single container. FUSE mounting requires the host machine to have /dev/fuse access and privileged mode, which is why the Compose file sets privileged: true and pid: "host".

The docker-compose.yml in the repository deploys the Beta image:

services:
  litepan:
    image: ponphil/litepan:beta
    container_name: litepan
    restart: unless-stopped
    ports:
      - "5211:5211"
      - "42069:42069/tcp"
      - "42069:42069/udp"
    environment:
      - TZ=Asia/Shanghai
    volumes:
      - ./data:/app/data
      - ./strm:/app/strm
      - ./mounts:/app/mounts:shared
    devices:
      - /dev/fuse:/dev/fuse
    pid: "host"
    privileged: true

Ports 42069 TCP and UDP handle the built-in BitTorrent/DHT listener for offline download capability. After starting the container, the web interface is at http://your-ip:5211 and the default administrator password is admin. The README includes a warning: do not use the ponphil/litepan:latest tag for this Go version, as latest still points to the archived Python predecessor.

WebDAV, FUSE Mount, and 302 Direct Links

LitePan exposes cloud drive content through three access methods. WebDAV lets other applications, operating systems, or NAS devices mount the aggregated drive collection over a standard protocol. FUSE mounting creates a local mount point on the host where the cloud drive files appear as a local filesystem, allowing applications that do not support WebDAV to read cloud files directly.

The README notes that FUSE mounts require the host to have /dev/fuse available and that the mounts directory must be mounted with the :shared option in the Compose volume configuration. A separate volume path is documented for the FUSE read cache, with a recommendation to map it to a faster disk if available.

The 302 direct link feature returns a redirect to the cloud provider's direct download URL rather than proxying file data through the LitePan server, which reduces server bandwidth consumption and can improve download speed for clients that follow redirects.

License, Beta Status, and Contribution Policy

LitePan is licensed under the PolyForm Noncommercial 1.0.0 license. This license allows personal learning and non-commercial use and explicitly prohibits commercial use. Teams considering LitePan for any deployment that generates revenue, reduces commercial costs, or is part of a commercial product should read the full license text before proceeding.

The Go rewrite is in Beta status. The README includes a caution that the first release may have significant issues and recommends careful testing. The Python predecessor has been archived, so the Go version is the only path for new deployments. The repository does not accept public pull requests; contributors with maintenance interest are directed to contact the author privately. External contributions that were accepted are credited in ACKNOWLEDGEMENTS.md.

OpenList (formerly Alist) is the natural alternative for cloud drive aggregation with WebDAV support. OpenList supports a wider range of storage providers and has a larger contributor base. LitePan's differentiation is the STRM generation workflow and media library integration with Emby and Jellyfin, which is more directly built into the product rather than requiring external scripts.

Build Stack and Module Dependencies

LitePan is written in Go 1.26.6 and builds with CGO disabled for the non-FUSE target and CGO enabled for the FUSE build. The go.mod file lists key dependencies including go-fuse/v2 v2.11.0 for FUSE support, anacrolix/torrent v1.61.0 for BitTorrent, go-chi/chi v5 for HTTP routing, studio-b12/gowebdav for WebDAV, and modernc.org/sqlite for the embedded database. The Dockerfile uses a two-stage build: a Node.js stage compiles the frontend from the web/ directory, and a Go stage compiles the backend with the pre-built frontend embedded.

The Makefile provides standard development commands: make lint runs golangci-lint, make test runs the test suite with race detection, and make build compiles both the FUSE and no-FUSE targets. The last push to the repository was on 2026-09-20.

Editorial conclusion

LitePan is suitable for personal or non-commercial home media server users who want a single interface across multiple cloud drive accounts, STRM-based media library integration with Emby or Jellyfin, and FUSE local mounting without managing each drive separately. The PolyForm Noncommercial 1.0.0 license explicitly prohibits commercial use, which rules it out for any revenue-generating deployment. The Go rewrite is labeled Beta (v0.5.6-Beta as of the last documented version), so expect breaking changes and verify against the Docker Hub changelog before upgrading.

Frequently asked questions

Official sources

1. Issues
2. Ponphil/LitePan on GitHub
3. Project website
4. README