Productivity
Self-host Wallabag on a VPS
Save and read articles later, on your own server.
A self-hosted read-later service with full-text capture, tags and mobile apps.
Why self-host Wallabag?
Wallabag keeps your reading list private and yours, instead of in a service that profiles you.
How to install Wallabag
- 1
Provision a VPS
Choose a plan with room for your data as well as the app.
- 2
Install the stack
Install PHP/Symfony + SQLite/Postgres.
- 3
Deploy the application
Follow the project’s official install guide for your distribution.
- 4
Enable HTTPS
Serve it on your own domain behind a reverse proxy with a certificate.
- 5
Back it up
Schedule a database dump plus a copy of any uploaded files to an off-box location.
Practical tips
- Give Wallabag its own database user with rights only on its own schema.
- Reverse-proxy Wallabag and terminate TLS at the proxy so certificates are managed in one place.
- Take a VPS snapshot before major upgrades so you can roll back cleanly.
- Keep Wallabag patched — most self-hosting incidents are unpatched software.
Frequently asked questions
- How much RAM does Wallabag need?
- Plan on 1 GB for typical use; add headroom if you expect many concurrent users.
- What stack does Wallabag run on?
- PHP/Symfony + SQLite/Postgres.
- Can I run other things on the same VPS?
- Yes — size the plan so Wallabag plus your other workloads fit in RAM with room to spare.
Looking for something else? Popular alternatives include Linkding, Shiori, Pocket (hosted) — browse all app guides.