Briefkasten
Briefkasten is a self-hosted bookmarking app that lets you save and organize web bookmarks on your own server, offering a private alternative to cloud…
Platform availability
Available on 2 of 10 platforms
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.
71/100 Good
- Maintained
- 77last commit 20 days ago
- Popular
- 611,181 GitHub stars
- Easy to install
- 452 install platforms, 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, links checked 13 days ago
- GitHub stars
- 1,181
- Open issues
- 0
- Last commit
- 2026-11-01
- License
- MIT
- Activity
- rising
Checked 18 days ago - source: GitHub (ndom91/briefkasten)
Resources & Compatibility
ARM (e.g. Raspberry Pi) is supported.
Checked 54 days ago - source: Docker Hub image tags and published docs
First-install notes
- Self-hosting with Docker You can self-host Briefkasten with Docker or docker-compose; the docs offer two compose setups depending on how much you want to self-host and which cloud services you'd like to use. source
Fetched 45 days ago - each note links to its source
Variants
Alternatives
No alternatives collected yet.
Common questions
How should I run Briefkasten self-hosted with Docker?
Use docker-compose.yml for the frontend and backend containers. Add docker-compose.storage.yml to include Postgres and RustFS if you do not want to use hosted database or object storage.
Which environment variables are required before starting Briefkasten?
Both web and backend need separate .env files. At minimum set DATABASE_URL, BETTER_AUTH_SECRET, BETTER_AUTH_URL, PUBLIC_WORKER_URL, and one Better Auth provider such as GITHUB_CLIENT_ID and GITHUB_CLIENT_SECRET.
How do I initialize an existing v2 database during an upgrade?
If the schema already matches, baseline it with pnpm --filter sveltekasten-web exec prisma migrate resolve --applied 0_init. This records the migration without re-running the DDL.
What data stores do I need to manage for backups?
The Docker setup can use Postgres for the database and RustFS for S3-compatible object storage. If you use hosted providers instead, those external services are the data sources to manage.
Answers sourced from github.com
Community
- Help needed deploying this amazing Docker : r/selfhosted - Reddit (reddit)
- Bookmarks manager Similar to Google Bookmarks : r/selfhosted - Reddit (reddit)
- Advice on Self-Hosting Mailserver : r/selfhosted - Reddit (reddit)
Collected 48 days ago - public community threads