PG Back Web is a web interface for scheduled PostgreSQL backups. It runs as a small Docker service in front of pg_dump and pg_restore: you register your database connections once, say how often to dump them, and it keeps the history, shows the logs of every run and lets you download or restore a dump from a browser tab. Nothing needs installing on the database server itself — the backups are taken through a normal connection string.
PBW_ENCRYPTION_KEY.pg_dump in the background, so a backup does not depend on a cron entry somebody has to remember.pg_restore against the same database from the same page.The image bundles pg_dump and pg_restore for PostgreSQL 13 through 18, so one container can back up a mixed fleet — a 13 cluster and an 18 cluster from the same interface. Webhooks can fire when a backup finishes or fails, when a health check fails, and on other events, which is enough to bridge it into an existing alerting setup without another agent.
Two containers: the application and a PostgreSQL database that stores its own metadata. The documented start is a Compose file with PBW_ENCRYPTION_KEY (your secret) and PBW_POSTGRES_CONN_STRING (where its own data lives); the UI listens on port 8085, and the first visit creates the administrator account. TZ controls the timezone used for scheduling and backup filenames.
AGPL-3.0 — free and open source, self-hostable from the published Docker image. The project is being renamed to UFO Backup to reflect a planned expansion beyond PostgreSQL; the current code and image remain under the PG Back Web name.