# Payload CMS vs tg-spam

> Two self-hosted projects, compared on the numbers selfhost.directory tracks live: score, popularity, release cadence and setup effort.

| | Payload CMS | tg-spam |
|---|---|---|
| Score | 83/100 ✓ | 52/100 |
| Rank in category | #2 of 13 in Headless CMS | #3 of 4 in Anti-Spam |
| GitHub stars | 45 570 ✓ | 453 |
| Stars, last 30 days | +638 ✓ | +0 |
| Stable releases, 12 months | 20 ✓ | 15 |
| Latest release | v3.92.1 · 27 Oct 2026 | v1.29.1 · 27 Oct 2026 |
| Setup | Moderate | Easy ✓ |
| Official Docker image | No | Yes ✓ |
| License | MIT | MIT |
| Main language | Typescript | Go |

## Which one should you pick?

Payload CMS scores 83/100 against 52/100 for tg-spam, so it is the safer default.

Payload CMS ships more often: 20 stable releases in the past year, against 15 for tg-spam.

If you want the quickest setup, tg-spam is easier to run; Payload CMS needs more configuration.

Payload CMS is growing faster right now (+638 stars in 30 days).

## Details

- [Payload CMS](https://selfhost.directory/project/payload-cms) (markdown: https://selfhost.directory/project/payload-cms.md)
- [tg-spam](https://selfhost.directory/project/tg-spam) (markdown: https://selfhost.directory/project/tg-spam.md)

## Related comparisons

- [Ghost vs Payload CMS](https://selfhost.directory/compare/ghost-vs-payload-cms)
- [directus vs Payload CMS](https://selfhost.directory/compare/directus-vs-payload-cms)

---
Source: https://selfhost.directory/compare/payload-cms-vs-tg-spam