PG Back Web

PG Back Web is an open-source web UI and service that manages PostgreSQL logical backups using pg_dump and psql. It provides scheduled backups, local or S3-compatible storage, basic encryption (environment-key based, details unverified), and restore controls from a browser-based dashboard. The project is AGPL v3 and self-hosted only.

It targets hobbyists, developers, and small teams that need simple GUI-managed logical backups and centralized visibility across multiple Postgres servers. It removes CLI-only workflows, simplifies storing dumps to local disk or S3-compatible buckets, and makes restores and scheduled retention observable without full DBA tooling.

Use Cases

  • Home server Postgres backups for notes and home automation.
  • Side projects needing quick restore or database cloning.
  • Small teams needing scheduled logical backups and simple restores.
  • Create staging clones by exporting and importing SQL dumps.
  • Compliance use: encrypted backups and retention in EU S3.
  • Local dev and test snapshotting, shared via object storage.

Strengths

  • Schedule backups and enforce retention policies from the web UI.
  • Store dumps to local disk or S3-compatible object storage.
  • Web-based restore using psql -f for small-to-medium databases.
  • Uses standard pg_dump and psql tools; predictable SQL dumps.
  • Provides Docker Compose and Kubernetes manifests for repeatable deployment.
  • Basic encryption configurable via PBW_ENCRYPTION_KEY (details unverified).
  • GUI centralizes multiple Postgres servers and audit-friendly activity.
  • Suitable for self-hosting; deploys easily on Coolify.

Limitations

  • Logical-only backups use pg_dump; larger files and slower restores.
  • No WAL-archiving or point-in-time recovery (PITR) features.
  • Not suitable for strict low-RTO or very large production databases.
  • AGPL v3 license requires care before offering managed services.
  • Encryption scope and key-storage details are not fully documented.

Final Thoughts

Try PG Back Web now if your databases are small-to-medium and logical dumps meet your RTO/RPO expectations; it makes backups and restores visible to non-DBA teammates.

Consider managed cloud backups when you need WAL-based PITR, continuous archiving, faster RTOs, or provider-managed SLAs and operational guarantees.

References