# ChronoFrame vs static_status

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

| | ChronoFrame | static_status |
|---|---|---|
| Score | 63/100 ✓ | 50/100 |
| Rank in category | #8 of 41 in Photo Management | #24 of 51 in Monitoring & observability |
| GitHub stars | 1 964 ✓ | 732 |
| Stars, last 30 days | +32 ✓ | +0 |
| Stable releases, 12 months | 3 ✓ | 0 |
| Latest release | v1.0.2 · 21 Oct 2026 | — |
| Setup | Easy ✓ | Easy |
| Official Docker image | Yes ✓ | No |
| License | AGPL-3.0 | GPL-3.0 |
| Main language | Typescript | Shell |

## Which one should you pick?

ChronoFrame scores 63/100 against 50/100 for static_status, so it is the safer default.

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

ChronoFrame is growing faster right now (+32 stars in 30 days).

## Details

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

---
Source: https://selfhost.directory/compare/chronoframe-vs-static-status