Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Go
Self-host Gokapi
updated Nov 2026deployed by usprices checked · Jul 2026Install verified on Ubuntu 26.04 · Nov 2026 · how we test
We earn commissions when you shop through the links below. Full disclosure →
A self-hosted file sharing server, written in Go as an alternative to Firefox Send. A logged-in user uploads files and gets a download link that expires after a set number of downloads or days and can be password-protected; admins can add users with roles, create file-request links so outside people can upload to you, and use a REST API. Files are stored on local disk by default or in an S3-compatible bucket, with optional server-side or end-to-end encryption, and the metadata is held in SQLite or Redis. The first start opens a web setup wizard that creates the admin account and the storage, database and encryption settings.
Pick Gokapi when you want a private place to send files to other people: you upload, it gives you a link, and the file deletes itself after a download count or a number of days, optionally behind a password. It is a single Go binary in a small image, keeps its metadata in SQLite by default, can use S3-compatible storage instead of disk, and offers server-side or end-to-end encryption, users with roles, file-request links for receiving uploads, and OpenID Connect sign-in. It is AGPL-3.0. Pick something else if you want a full cloud drive with sync clients or collaborative editing; Gokapi shares files, it does not manage a file tree.
What you need
Any VPS with at least 128 MB of RAM
A domain you control — most self-hosted setups need HTTPS in front of them
Paid link — we earn a commission if you shop through it.
Install
Run these commands on your server:
# Gokapi — compose adapted from the project's docker-compose.yaml and the documented docker run command, with named volumes and restart: unless-stopped, image f0rc3/gokapi pinned to v2.2.4; it ends at the first-run setup wizard, which is a web form (admin account, database, storage) and is not completed herecat > docker-compose.yml <<'EOF'services: gokapi: image: f0rc3/gokapi:v2.2.4 restart: unless-stopped ports: - "53842:53842" environment: TZ: UTC volumes: - gokapi-data:/app/data - gokapi-config:/app/configvolumes: gokapi-data: gokapi-config:EOFdocker compose up -dtimeout 180 bash -c 'until curl -fsSL -o /dev/null http://localhost:53842/setup; do sleep 3; done'# → http://SERVER_IP:53842/setup — the Gokapi setup wizard; choose a database, webserver settings, authentication and storage there and create the admin account in the browser (not automated by this snippet)
Gokapi's README and setup, update and troubleshooting docs flag these before you rely on it:
non-negotiableThe install ends at a browser wizard. Nothing is configured until you open /setup and create the admin credentials, choose the database and storage and set the public URL; finish it before you expose the port, since the wizard is where authentication gets set up.
non-negotiableThe docs bind the container to 127.0.0.1:53842 and say direct access without a reverse proxy sends traffic unencrypted. Our snippet publishes the port on all interfaces so it can be reached by IP, which means uploads and the admin password travel in clear text until you add TLS (the wizard's own SSL option makes a self-signed certificate, which the docs recommend only when you are not behind a proxy).
non-negotiableMount /app/data and /app/config as volumes or all data is lost when the container is removed (the docs warn about this explicitly). Some releases change the data format on first start, and the changelog warns for those (v2.0.0, for one) that you cannot downgrade afterwards, so back both volumes up before changing the tag and read the changelog for breaking changes.
non-negotiableThe encryption implementation has not been independently audited, according to the setup docs. File requests also bypass level-3 end-to-end encryption, and files on S3 are stored in plain text unless you enable encryption in the wizard.
non-negotiableThe wizard's authentication step includes a Disabled option that the docs call very dangerous: it removes Gokapi's own login except for API calls and leaves your reverse proxy to protect a list of paths. Header and OpenID Connect modes also exist; do not pick Disabled without that proxy rule in place.
non-negotiableThe wizard has a Save IP option that logs downloader IP addresses and which the docs say may not be GDPR-compliant. Only the latest stable release receives security fixes per SECURITY.md, and v2.2.4 was a security-fix release, so plan to move forward rather than sit on an old tag.