Gokapi — Self-Hosted, Open-Source

Lightweight server to share files, which expire after a set amount of downloads or days. Similar to the discontinued Firefox Send, with the difference that only the admin is allowed to upload files.

License: GPL-3.0. Built with: Go, JavaScript, Go Template, CSS, HTML, Makefile, Shell, Dockerfile. Source: https://github.com/Forceu/gokapi.

Features

Expiring file shares: Automatically removed after a set number of downloads or days
User management with roles: Fine-grained permission control, only registered users can upload
File requests: A shareable URL lets external parties upload files, visible only to the URL’s creator
File deduplication: Identical files use no extra space
Cloud storage support: AWS S3 (or S3 compatible like Backblaze B2), optional
Built-in encryption: Including end-to-end encrypted uploads
OpenID Connect support: Integrate with identity providers like Authelia or Keycloak
REST API: For automation and integration into other systems
Customizable UI: Adjust look and feel with custom CSS and JavaScript

Installation

docker run --rm \ --name gokapi \ -v gokapi-data:/app/data \ -v gokapi-config:/app/config \ -p 127.0.0.1:53842:53842 \ -e TZ=UTC \ docker.io/f0rc3/gokapi:latest

Why self-host Gokapi

Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.

Hardware notes

CPU: 1 core RAM: 256 MB Storage: 100 MB + file storage

Where to go from here

Last verified: 2026-04-21