Analytics cookies only (Google Analytics, PostHog). No ad networks, no cross-site tracking. See our privacy policy.
Self-host Yopass
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 service for sharing passwords and other secrets through a one-time or expiring link. The browser encrypts the text or file with OpenPGP before it reaches the server, and the decryption key stays in the link's URL fragment, so the server stores only encrypted data. Secrets expire automatically or after the first read, can be protected with an extra password, and need no user accounts. Data is kept in Memcached or Redis, files can go to disk or S3-compatible storage, and Prometheus metrics are built in.
Pick Yopass when you want a small service for handing someone a password or file through an expiring, one-time link without an account on either side. The browser encrypts the secret with OpenPGP and the decryption key stays in the link's URL fragment, so the server stores only the encrypted message. Secrets expire or are deleted after the first read, can be protected with an extra password, and can be text or files. The open source edition is Apache-2.0 Go with a React frontend, storing data in Memcached (the default) or Redis. Our snippet combines the README quick start with `deploy/docker-compose/insecure/docker-compose.yml` into one Compose file with the images pinned to `jhaals/yopass:16.1.0` (released 2026-11-07) and `memcached:1.6.45-alpine`, and publishes port 1337 on all interfaces instead of loopback. No RAM figure is published, so our 64 MB floor is an estimate. In the catalog, Infisical, Phase, OpenBao and Vault are secrets managers that store application secrets and credentials long term; Yopass stores nothing for long, has no accounts, and exists only to pass one secret to one person.
What you need
Any VPS with at least 64 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:
# Yopass — share secrets with expiring links — adapted from the README quick start and deploy/docker-compose/insecure/docker-compose.yml, images pinned to jhaals/yopass 16.1.0 and memcached 1.6.45-alpine# Changed from upstream: the README's two docker run commands as one Compose file, port 1337 published on all interfaces instead of 127.0.0.1mkdir yopass && cd yopasscat > docker-compose.yml <<'EOF'services: memcached: image: memcached:1.6.45-alpine restart: unless-stopped yopass: image: jhaals/yopass:16.1.0 command: ["--memcached=memcached:11211"] restart: unless-stopped depends_on: - memcached ports: - "1337:1337"EOFdocker compose up -dtimeout 300 bash -c 'until curl -fsS -o /dev/null http://localhost:1337/; do sleep 3; done'# → http://SERVER_IP:1337 (no login; create a secret and open the link it returns. Plain HTTP only: put a TLS reverse proxy in front before real use)
Yopass's README, server options reference and Compose files flag these before you rely on it:
non-negotiableThe README lists features that need a paid business licence: OpenID Connect and email-domain restrictions, custom themes, logo and application name, audit logging, secret requests, read receipts, signed webhooks and file uploads larger than 1 MB. Without a key, --max-file-size (default 512KB) is capped at 1 MB, and the server refuses to start if --oidc-issuer, --audit-log or --webhook-url are set without a licence.
non-negotiableOur snippet serves plain HTTP. The README says Yopass must be served over HTTPS in production so the web application and the encrypted payload cannot be modified in transit, and its quick start is for local testing or use behind a TLS-terminating reverse proxy. The README lists Compose, Kubernetes and Let's Encrypt deployments for real use.
non-negotiableThere is no authentication in the open edition, so anyone who can reach the port can create secrets (the README: no user accounts). Requiring login (--require-auth) is documented as a licence feature. Secrets are limited to 10000 encrypted bytes by default (--max-length), and the expiry pre-selected in the UI is one hour (--default-expiry); custom expiry is off until --allow-custom-expiration is set.
non-negotiableOur Compose file mounts no volume for Memcached. The README documents Redis as the other storage option (--database redis --redis ...); we did not test it.
non-negotiableFiles go into the database unless you set a disk or S3 --file-store; the file-storage guide covers both. The server image is distroless and runs as user 1000; Docker Hub lists amd64 and arm64 builds for this tag.
non-negotiableThe run checks that / answers 200; we did not create or open a secret, so the encrypt and decrypt flow is untested here.