SE2EEnd

SE2EEnd is a self-hosted, end-to-end encrypted file-sharing service.

  • Cloud
  • Network Services
SE2EEnd is a self-hosted, end-to-end encrypted file-sharing service. It lets teams transfer files securely while the server never sees file contents or encryption keys. It is suitable for teams that need private file exchange on infrastructure they control.

Platform availability

Available on 1 of 10 platforms

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

60/100 Good

Maintained
95last commit 3 days ago
Popular
2212 GitHub stars
Easy to install
251 install platform, install notes
Light to run
No data
Security check
70no serious findings, 23 minor, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
12
Open issues
8
Last commit
2026-11-18
Latest release
v1.4.0
License
GPL-3.0
Activity
declining

Checked yesterday - source: GitHub (sE2EEnd/sE2EEnd)

Resources & Compatibility

Requirements not published yet.

Checked yesterday - source: Docker Hub image tags and published docs

First-install notes

  • Installation Docker images are published to GHCR; fetch the provided deployment files and run the stack with Docker Compose. source
  • Installation Check the GitHub Releases page for the latest installation packages to deploy on your server. source

Fetched yesterday - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

How do I deploy sE2EEnd on my own server?

Use the published Docker images and run the stack with Docker Compose. The installation instructions tell you to fetch the provided deployment files and start the services from GHCR.

Can I store uploaded files in S3 instead of the local filesystem?

Yes. sE2EEnd supports local filesystem storage or any S3-compatible object store, such as AWS, MinIO, Scaleway, or OVHcloud.

Can I require users to authenticate before downloading a transfer?

Yes, instance policies can require authentication for download and enforce transfer passwords. Authentication is provided through Keycloak using OAuth2/OIDC, SSO, LDAP/Active Directory, and MFA.

Can I revoke a shared transfer after it has been sent?

Yes, it can be revoked instantly from the dashboard. The admin dashboard also manages transfers and monitors storage usage.

Does it handle multi-gigabyte file transfers without loading the whole file into memory?

Yes, transfers are processed in encrypted chunks that are streamed to and from disk. The whole file is not buffered in memory on the client or server.

Answers sourced from github.com, se2eend.github.io, se2eend.github.io

Community

Collected yesterday - public community threads