Payload CMSvsPostal
Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.
| Payload CMS | Postal | |
|---|---|---|
| Score | 83/100 | 72/100 |
| Rank in category | #2 of 13 in Headless CMS | #3 of 16 in Mail Server |
| GitHub stars | 45 570 | 16 899 |
| Stars, last 30 days | +638 | +72 |
| Stable releases, 12 months | 20 | 3 |
| Latest release | v3.92.1 · 27 Oct 2026 | 3.3.7 · 3 Jun 2026 |
| Setup | Moderate | Advanced |
| Official Docker image | No | Yes |
| License | MIT | MIT |
| Main language | Typescript | Ruby |
Which one should you pick?
Payload CMS scores 83/100 against 72/100 for Postal, so it is the safer default.
Payload CMS ships more often: 20 stable releases in the past year, against 3 for Postal.
If you want the quickest setup, Payload CMS is easier to run; Postal needs more configuration.
Payload CMS is growing faster right now (+638 stars in 30 days).
Payload CMS details →Postal details →