Skip to content

oddk vs Docker Compose, Pigsty and backup tools

Backup tools and oddk solve different problems. Databasus, pgBackWeb, pgBackRest, WAL-G and Barman back up databases you already run. oddk runs them: it creates Postgres instances on one Linux host, sizes and tunes them, manages their users and upgrades, watches their health, and captures the whole deployment in one archive.

The facts about other tools below are from their own documentation and source, linked in each section: as of October 2026 for Databasus, pgBackRest, WAL-G and Barman, and November 2026 for pgBackWeb, Pigsty and Autobase. Check there before relying on a detail.

Which do you need?

  • You run Postgres in Docker Compose, with a cron job for backups. oddk replaces both; see Docker Compose and a cron job.
  • Your Postgres already exists, on a server or a managed service such as RDS or Cloud SQL. A backup tool. oddk runs only the instances it created.
  • You need point-in-time recovery. A backup tool that archives or streams WAL. oddk has none: you can restore to the last snapshot, and snapshots run at most once an hour.
  • You need failover or replicas. A cluster manager such as Pigsty or Autobase, both built on Patroni; see Pigsty and Autobase. oddk runs standalone instances on one host.
  • You back up MySQL, MariaDB or MongoDB as well. Databasus, or WAL-G for MySQL and MariaDB. oddk runs only PostgreSQL.
  • You want to create and run Postgres on a Linux host you own or rent, and rebuild that host from one archive and one key. oddk.

Backup tools, side by side

oddkDatabasuspgBackRest, WAL-G, Barman
What it doesRuns Postgres instances on one hostBacks up existing databasesBack up and restore an existing Postgres server
Creates, sizes and tunes instancesYesNoNo
Database users, major upgradesYesNo 1No
Logical backups (pg_dump)Yes, with --logicalYesNo
Physical backupsYes, the defaultPostgreSQL 17+Yes
Incremental backupsNo; every snapshot is completePostgreSQL 17+Yes
Point-in-time recoveryNoPostgreSQL 17+Yes
Encrypted archivesAlways: age, post-quantum hybrid 2AES-256-GCMOptional 3
Offsite storageS3 and S3-compatibleS3, R2, Google Drive, Azure Blob, NAS, FTP, SFTP, rcloneS3, Azure, Google Cloud Storage and others 4
Rebuild a lost hostYes: one archive and the master key restore every instance and oddk’s configurationRestores databases; the server is yours to rebuildRestores the cluster; the server and its Postgres installation are yours to rebuild
Other databasesNoMySQL, MariaDB, MongoDB (logical)WAL-G: MySQL, MariaDB, SQL Server
InterfaceCLI, plus an API on the host’s loopbackWeb UI with workspaces, roles and an audit logCLI
LicenceMITApache 2.0MIT, Apache 2.0, GPL 3

Where each one is stronger

Databasus restores each backup into a temporary database container and checks the result, after every backup or on a schedule. oddk reads every archive back in full when it is written and again before a restore, and checks catalogued archives against their recorded SHA-256, but does not restore them to prove it. Databasus also has a web UI for a team, backs up databases on managed services and behind SSH tunnels, and covers MySQL, MariaDB and MongoDB.

pgBackWeb (AGPL 3.0, being renamed UFO Backup) is in the same class as Databasus: a web UI that schedules pg_dump of existing databases, PostgreSQL 13 to 18, to local disk or S3, with health checks and webhooks, and restores from the same UI. It encrypts the connection strings and storage credentials it keeps; the dumps themselves are zipped SQL.

pgBackRest, WAL-G and Barman archive WAL continuously, so you can restore to a moment rather than to the last backup. They take incremental backups and work with an existing Postgres installation, however it was set up. They need the server’s archive_command, a replication connection or access to its data directory, so they are set up on or next to the database server.

oddk does the part those tools assume is already done: it creates and runs the instances. A snapshot captures every instance’s data together with oddk’s own configuration in one encrypted archive, so a host that is gone comes back with one command and its master key, with its instances, ports, parameter groups and passwords, and its schedules paused until you resume them. It restores one instance, or one database as a new database, while everything else keeps serving. It checks instance and host health and sends a message when an instance degrades or a scheduled run fails. It is one binary that needs only Docker and systemd.

Docker Compose and a cron job

The most common way to self-host Postgres is a postgres service in a Compose file and a cron job that runs pg_dump. It works until a part you wrote yourself fails quietly. Each row below is something that setup leaves to you.

oddkCompose + cron
Create an instanceoddk create picks the data mount for the Postgres major, sets CPU and RAM limits and shared memory, and applies a parameter group calculated from them (Tuning)You write the service, volume and settings. PostgreSQL 18’s official image moved its data directory: a volume at the old path /var/lib/postgresql/data stops the container from starting
Postgres passwordNever in the container’s Docker configuration; oddk sets it over SQLPOSTGRES_PASSWORD in the Compose file, and readable with docker inspect
What a backup holdsEvery instance, physical by default, plus oddk’s own configuration, in one archiveWhat the script dumps, usually one pg_dump per database
EncryptionAlwaysWhatever the script adds
Is the backup good?Every archive is read back in full before it counts, and its SHA-256 is recordedWhat the script checks. pg_dump | gzip > file reports gzip’s exit status, not pg_dump’s, unless the script sets pipefail
RetentionThe newest two archives are never pruned, and a local archive with no offsite copy is keptTypically find -mtime +N -delete, which removes the last good dump as readily as any other once new ones stop arriving
A failure tells youA failed run or an unhealthy instance sends a message to Slack, email, Telegram or a webhookcron mails a job’s output to a local user, if the host can send mail. A Compose healthcheck marks a container unhealthy and tells no one
Major upgradeoddk instance major-upgrade: dump, fresh cluster, restore, with a full backup kept as the rollbackBy hand: dump, new image, new volume, restore
Rebuild a lost hostOne archive and the master key restore every instance, port, password and scheduleReinstall, recreate the Compose project, restore each dump

Compose is stronger when Postgres belongs to one application. The database sits in the same file as the app, versioned with it in git, on the same network, and nothing else runs on the host. oddk is a separate daemon with its own CLI, and an application reaches its instances over the host-local bridge 10.88.0.1.

Pigsty and Autobase

Pigsty and Autobase build highly available PostgreSQL clusters across several servers, with Patroni for failover. oddk runs standalone instances on one host. If you need a standby that takes over by itself, read replicas or point-in-time recovery, use one of them: they are built for it and oddk is not.

oddkPigstyAutobase
What it runsStandalone instances on one hostClusters on one node or many, with monitoring, pooling and load balancingHighly available clusters on your servers or a cloud provider
Failover and replicasNoYes, with PatroniYes, with Patroni
Point-in-time recoveryNoYes, with pgBackRestYes, with pgBackRest or WAL-G
How Postgres runsOfficial Docker images, or compatible ones such as pgvector and postgisOS packages on bare Linux; Docker only for trying it outOS packages, installed by Ansible
SetupOne binary, plus Docker and systemdAnsible playbooks, run by an admin user with passwordless SSH and sudoA web console, an Ansible collection, or GitOps
Day to dayCLI, plus an API on the host’s loopbackA YAML inventory and playbooks; Grafana dashboardsThe web console, or Ansible
LicenceMITApache 2.0MIT; the web console is proprietary, with a free Starter plan

Pigsty packages 626 extensions and alternative Postgres kernels, and monitors Postgres, nodes and infrastructure with VictoriaMetrics and Grafana. Autobase adds connection pooling with PgBouncer, a load balancer, and major upgrades across a cluster.

oddk is for when one host is enough. It installs with one command, and its whole state, every instance included, fits in one encrypted archive that rebuilds the host on a new machine.

Using a backup tool with oddk

A logical backup tool can back up an oddk instance like any other Postgres server. It gives you a second, independent copy on its own schedule, with the tool’s own encryption, storage and restore tests.

Get the instance’s connection string:

oddk instance get-postgres-password app --conn
# postgresql://postgres:…@10.88.0.1:5432/postgres

10.88.0.1 is host-local. A tool on the same host connects to it directly, from the host or from a container on Docker’s default network. A tool on another machine needs an SSH tunnel to the host; Databasus has one built in.

Choose the user carefully. A dump is complete only if its user can read every object:

  • oddk instance add-db-user app --username backup --database app --readonly grants read access to the public schema’s current tables and sequences, and to tables created later. A new schema or a new sequence, such as one from a serial column, makes the next dump fail.
  • PostgreSQL’s pg_read_all_data role (PostgreSQL 14 and later) covers every schema and sequence, but not large objects or tables with row-level security.
  • The postgres user can read everything.

Whatever the user, a restore test finds out that a dump is incomplete.

Physical backups and point-in-time recovery from outside do not work against an oddk instance as installed. Its pg_hba.conf accepts replication connections only from inside the container, and oddk does not set an archive_command.

What oddk is not

  • Not highly available. No failover, no streaming replicas, no quorum. It runs standalone instances.
  • Not multi-tenant. It assumes a single trusted operator on a single host. Anyone with the API token has full control.
  • Not internet-facing. The API binds to 127.0.0.1 and Postgres to a host-local Docker bridge. Reach them over an SSH tunnel.
  • Not a Postgres fork, driver or connection pooler. It runs the official PostgreSQL images and compatible ones such as pgvector and postgis.
  • Not a Kubernetes operator. It talks to Docker directly.

  1. Databasus can create a read-only database user for its own backups. ↩︎

  2. ML-KEM-768 + X25519, with the key derived from oddk’s master key. There is no setting to turn it off and no second key to manage. Without the master key, no archive can be restored or read; see Encrypted at rest. ↩︎

  3. pgBackRest: AES-256-CBC. WAL-G: libsodium, OpenPGP or Yandex Cloud KMS. Barman: GPG. Off by default in all three. ↩︎

  4. pgBackRest: S3, Azure, Google Cloud Storage, SFTP, POSIX and CIFS paths. WAL-G: S3, Google Cloud Storage, Azure, Swift, Alibaba Cloud, SSH. Barman: its own server’s disk, or S3, Azure and Google Cloud Storage through barman-cloud. ↩︎