// the find
eduardolat/pgbackweb
🐘 Effortless PostgreSQL backups with a user-friendly web interface! 🌐💾
PG Back Web is a self-hosted PostgreSQL backup manager with a web UI. You deploy one Docker container, point it at your databases, configure cron schedules and S3/local destinations, and it runs pg_dump on schedule with PGP encryption. It is for solo developers and small teams who want scheduled backups without writing shell scripts or paying for a managed backup service.
The architecture is honest about what it is: a thin Go wrapper around pg_dump with a scheduler and a UI, which means the actual backup mechanics are battle-tested. PGP encryption at rest is built in, not bolted on. The webhook support for backup completion/failure events means you can wire it into Slack or PagerDuty without any custom glue. Supporting PostgreSQL 13 through 18 with health checks that verify connectivity before scheduling runs is the kind of operational detail that prevents silent failures.
Single-user auth model — the service has one account, so any team sharing it shares credentials. There is no role-based access or per-user audit trail. The project is mid-pivot to 'UFO Backup' with multi-database ambitions, which is a real risk if you are adopting it: the roadmap may drift away from the PostgreSQL-specific hardening that makes it trustworthy today. No support for streaming replication or WAL-based point-in-time recovery — it is pg_dump snapshots only, so your recovery granularity is whatever your cron interval is. The restoration flow restores into an existing database via the web UI, which is convenient but also the kind of footgun that has caused real production incidents.