wal-e/wal-e
Continuous Archiving for Postgres observed · 2026-08-28
Health v2 · maintenance only
32/100
- Activity 0
- Release rhythm 35
- Longevity 100
Flags: no_releases
How is this computed?
round(0.45*activity + 0.35*rhythm + 0.20*longevity); archived -> min(score, 10) — computed 2026-09-03. Adoption (stars, forks) is never an input.
- gap_med: n/a
- age_days: 4975
- days_rel: n/a
- days_push: 987
- n_releases_24m: 0
Adoption not part of the score
3464 stars · 312 forks observed · 2026-08-28
What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded
WAL-E is a command-line tool for continuous archiving of PostgreSQL WAL files and base backups to cloud blob storage such as S3, Azure, Google Cloud Storage, and Swift. It integrates with Postgres's archive_command and restore_command for point-in-time recovery, but is now officially obsolete in favor of WAL-G and pgBackRest.
Use cases
- archive postgres wal files to s3
- take base backups of postgresql to cloud storage
- set up point-in-time recovery for postgres
- restore a postgres database from cloud backup
- prune old postgres backups to retain a finite number
When to choose
- you maintain a legacy deployment already built around WAL-E archives
- you need to read or manage existing WAL-E-format archives
When to avoid
- starting a new Postgres backup setup - use WAL-G or pgBackRest instead
- you need actively maintained software or fast archiving performance
Facets
cli-tool · maturity abandoned
backup database databases cloud-computing self-hosted python cli postgresql pitr wal-archiving s3 cloud-storage disaster-recovery linux
2 sources
- readme: https://github.com/wal-e/wal-e · fetched 2026-08-28 · 69fb6ea43f16
- registry_pypi: https://pypi.org/pypi/wal-e/json · fetched 2026-08-29 · 6762e88eb27b
Member repositories
| Repository | Role | Health v2 |
|---|---|---|
| wal-e/wal-e | main | 32 |
For agents
Data as of 2026-08-30T08:39:29.467469+00:00 · Report a problem