Secret

Secret is a self-hosted service for sharing passwords, notes and files through a one-time link that burns after reading.

  • Cloud
  • Productivity
  • Security
  • Tools & Utilities
  • Web & Publishing
Secret is a self-hosted service for sharing passwords, notes and files through a one-time link that burns after reading. Everything is encrypted in the browser and the key stays in the link's fragment, so the server never sees the content. Notes expire from 5 minutes to 30 days after one or a set number of reads, with an optional Argon2id password, up to 10 files per note, Markdown, QR codes and 10 languages. No accounts, no analytics, and the logs keep no content, keys or IP addresses, making it a private, open-source alternative to hosted one-time paste services.

Platform availability

Available on 1 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 (not listed)

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.

69/100 Good

Maintained
100last commit 3 days ago
Popular
209 GitHub stars
Easy to install
351 install platform, install notes, Docker image
Light to run
No data
Security check
100no serious findings, CI, tests

Based on 4 of 5 factors.

Availability: platform listings confirmed today

GitHub stars
9
Open issues
0
Last commit
2026-11-17
Latest release
v1.8.1
License
MIT
Activity
rising

Checked 3 days ago - source: GitHub (largerio/secret)

Resources & Compatibility

Requirements not published yet.

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

First-install notes

  • Install CRDs before the Helm chart Before installing the Helm chart (the packaged install instructions), install the CRDs (Custom Resource Definitions, Kubernetes' rules for External Secrets objects). Without them, Kubernetes may not recognize those objects, so the install or the secret controller can fail. source
  • Use HTTPS when pointing to Vault If you're connecting External Secrets to a Vault server, use https:// in the server setting instead of the example http:// address, and configure TLS if needed. That keeps your Vault credential requests from crossing the network in plain text, where they could be seen or captured. source
  • Choose which secret keys to push In a PushSecret (the object that copies keys from a Kubernetes Secret to a chosen store), add a match rule unless you truly want every key copied. Also set rewrite if you need to rename keys there, or the store may end up with missing, extra, or confusing key names. source
  • Run as a single container Secret runs in a single Docker container that you host yourself; no other services, accounts or analytics are required. source
  • Back up the data folder The data folder holds the database, the encrypted notes and the server's encryption key generated on first start; back it up whole before migrating or updating so secrets and the key can be restored. source

Fetched 3 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Does the server store or log the contents of shared notes?

No, notes are encrypted in the browser before sharing, and the logs hold no content, keys, or IP addresses.

Where are uploaded files stored in self-hosted Secret?

Files are stored on the container's data volume or in any S3-compatible bucket, such as AWS S3, Cloudflare R2, RustFS, or Garage.

Can a note be limited to a certain number of reads?

Yes, notes can burn after one read or after a set number of reads, with expiry from 5 minutes to 30 days.

Can I add an optional password to a note?

Yes, notes can use an optional Argon2id password, with the server checking a proof of the password before serving anything.

Can note sharing be automated from scripts or apps?

Secret provides a JavaScript/TypeScript SDK and a command line client for sending and reading notes.

Answers sourced from github.com

Community

Collected 3 days ago - public community threads