FileRise

FileRise is a lightweight, self-hosted web file manager that lets individuals and teams store, upload, share, and organize files with WebDAV, per-folder…

  • Cloud
  • Network Services
  • Tools & Utilities
FileRise is a lightweight, self-hosted web file manager that lets individuals and teams store, upload, share, and organize files with WebDAV, per-folder access controls, and optional encryption.

Platform availability

Available on 2 of 10 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • 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.

77/100 Good

Maintained
100last commit 16 days ago
Popular
601,028 GitHub stars
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data
Security check
85no serious findings, tests

Based on 4 of 5 factors.

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

GitHub stars
1,028
Open issues
9
Last commit
2026-11-05
Latest release
v3.42.0
License
MIT
Activity
rising

Checked 12 days ago - source: GitHub (error311/FileRise)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

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

First-install notes

  • Docker port and storage setup Use persistent folders for uploads, user data, and metadata, and choose a dedicated upload directory rather than the root of a large share. For the default Docker bridge setup, map host port 8080 to container port 80 unless you also change the matching HTTP or HTTPS container target port. source

Fetched 38 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I change FileRise's HTTP_PORT or HTTPS_PORT without losing WebUI access?

If you change HTTP_PORT or HTTPS_PORT, edit the corresponding Container Port (Target) in the Port mappings to the same numbers. Otherwise the container listens on a different internal port and the WebUI will not be reachable.

What uploads path should I use in a Docker or Unraid FileRise deployment?

Set UPLOADS PATH to the folder where uploaded files are stored. Use a dedicated folder such as /mnt/user/appdata/FileRise/uploads/ rather than the root of a huge media folder.

What admin-account problem is reported for FileRise on YunoHost?

The YunoHost support thread reports that FileRise installs and is served, but the user cannot create an admin account.

Answers sourced from forum.yunohost.org, forums.unraid.net

Community

Collected 53 days ago - public community threads