How to Self-Host Readeck
Readeck read-it-later and web-archiving service for saving articles, tagging bookmarks, preserving readable copies, and exporting content. It was added to SelfHub after appearing in What I Self-Host, What I Don't, and Why; the product facts below were checked against the project's official site and source repository.
When Readeck is a good fit
Choose Readeck when you want this capability on infrastructure you control and are prepared to own updates, access control, monitoring, and recovery. Review the upstream documentation before selecting a version because deployment requirements can change between releases.
Deployment notes
Run the official binary or container with a persistent data directory and a reverse proxy for HTTPS. Create the first administrator through the documented command.
Place any browser-accessible interface behind HTTPS. Pin a release rather than an unqualified latest tag, apply updates deliberately, and keep the service reachable only from the networks and users that need it.
Data and recovery
Back up both the database and archived article assets; exports provide an additional portable copy of selected content.
Write down the restore sequence, required secrets, exposed ports, and external dependencies. A scheduled backup is not complete until a clean host can restore it and pass a functional check.
Important limitation
Archived pages may contain private or copyrighted material. Control access and follow the terms and laws that apply to saved content.
Production checklist
- Pin and record the deployed version.
- Persist every documented data and configuration path.
- Terminate TLS at a maintained reverse proxy or trusted tunnel.
- Restrict administrative interfaces and rotate default credentials.
- Monitor uptime, disk space, certificate expiry, and failed jobs.
- Test an off-host backup with a real restore.
