# ChronoFrame vs scanopy

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

| | ChronoFrame | scanopy |
|---|---|---|
| Score | 63/100 | 64/100 ✓ |
| Rank in category | #8 of 41 in Photo Management | #1 of 10 in Network |
| GitHub stars | 1 964 | 5 915 ✓ |
| Stars, last 30 days | +32 | +121 ✓ |
| Stable releases, 12 months | 3 | 40 ✓ |
| Latest release | v1.0.2 · 21 Oct 2026 | v0.19.3 · 27 Oct 2026 ✓ |
| Setup | Easy ✓ | Moderate |
| Official Docker image | Yes ✓ | No |
| License | AGPL-3.0 | AGPL-3.0 |
| Main language | Typescript | Rust |

## Which one should you pick?

scanopy scores 64/100 against 63/100 for ChronoFrame, so it is the safer default.

scanopy ships more often: 40 stable releases in the past year, against 3 for ChronoFrame.

If you want the quickest setup, ChronoFrame is easier to run; scanopy needs more configuration.

scanopy is growing faster right now (+121 stars in 30 days).

## Details

- [ChronoFrame](https://selfhost.directory/project/chronoframe) (markdown: https://selfhost.directory/project/chronoframe.md)
- [scanopy](https://selfhost.directory/project/scanopy) (markdown: https://selfhost.directory/project/scanopy.md)

---
Source: https://selfhost.directory/compare/chronoframe-vs-scanopy