1. What is Postgresus and why should I use it instead of hand-rolled scripts?
Postgresus is an Apache 2.0 licensed, self-hosted service backing up PostgreSQL, v13 to v18. It differs from shell scripts in that it has a frontend for scheduling tasks, compressing and storing archives on multiple targets (local disk, S3, Google Drive, NAS, Dropbox, etc.) and notifying your team when tasks finish or fail — all without hand-rolled code
2. How do I install Postgresus in the quickest manner?
The most direct route is to run the one-line cURL installer. It fetches the current Docker image, spins up a single PostgreSQL container. Then creates a docker-compose.yml and boots up the service so it will automatically start again when reboots occur. Overall time is usually less than two minutes on a typical VPS.
3. What backup schedules can I schedule?
You can choose from hourly, daily, weekly or monthly cycles and even choose an exact run time (such as 04:00 when it's late night). Weekly schedules enable you to choose a particular weekday, while monthly schedules enable you to choose a particular calendar day, giving you very fine-grained control of maintenance windows.
4. Where do my backups live and how much space will they occupy?
Archives can be saved to local volumes, S3-compatible buckets, Google Drive, Dropbox and other cloud targets. Postgresus implements balanced compression, which typically shrinks dump size by 4-8x with incremental only about 20% of runtime overhead, so you have storage and bandwidth savings.
5. How will I know a backup succeeded — or worse, failed?
Postgresus can notify with real-time emails, Slack, Telegram, webhooks, Mattermost, Discord and more. You have the choice of what channels to ping so that your DevOps team hears about successes and failures in real time, making recovery routines and compliance audits easier.
6. Does Postgresus reduce database security?
No. All the data executes within containers you control, on servers you own. Credentials and backup files are left on your server or in the cloud account of your choice. Additionally, Postgresus offers enterprise-grade AES-256-GCM encryption for your backup files. This means even if someone gains access to your storage, encrypted backups remain useless without the decryption key. Because it's open source, you or your security team can inspect every line to make sure it meets your organization's needs before it's run.
7. How do I set up and run my first backup job in Postgresus?
To start your very first Postgresus backup, simply log in to the dashboard, click on New Backup, select an interval — hourly, daily, weekly or monthly. Then specify the exact run time (e.g., 02:30 for off-peak hours). Then input your PostgreSQL host, port number, database name, credentials, version and SSL preference. Choose where the archive should be sent (local path, S3 bucket, Google Drive folder, Dropbox, etc.). If you need, add notification channels such as email, Slack, Telegram or a webhook and click Save. Postgresus instantly validates the info, starts the schedule, runs the initial job and sends live status. So you may restore with one touch when the backup is complete.
8. How does PostgreSQL monitoring work?
Postgresus monitors your databases instantly. This optional feature helps avoid extra costs for edge DBs. Health checks are performed once a specific period (minute, 5 minutes, etc.). To enable the feature, choose your DB and select "enable" monitoring. Then configure health checks period and number of failed attempts to consider the DB as unavailable.
9. Who is Postgresus suitable for?
Postgresus is designed for single developers, DevOps teams, organizations, startups, system administrators and IT departments who need reliable PostgreSQL backups. Whether you're managing personal projects or production databases, Postgresus provides enterprise-grade backup capabilities with a simple, intuitive interface.
10. How is Postgresus different from PgBackRest, Barman or pg_dump?
Postgresus provides a modern, user-friendly web interface instead of complex configuration files and command-line tools. While PgBackRest and Barman require extensive configuration and command-line expertise, Postgresus offers intuitive point-and-click setup. Unlike raw pg_dump scripts, it includes built-in scheduling, compression, multiple storage destinations, health monitoring and real-time notifications — all managed through a simple web UI.
11. Can I use Postgresus as an individual and as a team?
Yes, Postgresus works perfectly for both individual developers and teams. For individuals, you can manage all your databases with a simple, secure interface. For teams, Postgresus offers access management features that let you create multiple users with different permission levels (viewer, editor, admin). You can control who can view or manage specific databases, making it ideal for DevOps teams and development organizations. Additionally, audit logs track all system activities, showing who accessed what and when, which is essential for security compliance and team accountability.