On the “self-hosted” point, I’d like to clarify what I mean in this context:

1. You run Docker entirely on your own machine or server (bare metal or cloud).

2. You deploy it yourself — via Docker Compose, Kubernetes, or whatever you prefer.

3. You have full control over your data volumes and config files.

The Docker environment here isn’t tied to any third-party infrastructure or remote service — everything runs under your control. From that standpoint, I’d still consider it self-hosted. Using Docker is just a way to avoid the usual “it works on my machine” headaches and make setup easier for others.

That said, since ChronoFrame runs in a Node.js environment, it doesn’t produce a native binary. But I totally get your point — I’ll add docs for running it directly with node or managing it via pm2, so users can skip Docker if they prefer.

Thanks again for the feedback — really glad you took the time to look into it.