umami-software/umami

Prefer upstream unless you specifically want this exact historical snapshot; the fork adds no visible functionality and is far behind current Umami.

Choose this fork only if you want an old, mostly untouched Umami snapshot. For production use or an actively maintained self-hosted analytics platform, upstream is the better choice.

Choose this fork only if the `captain-definition` deployment path is specifically valuable to you. Otherwise, upstream is the better default because this fork is essentially an outdated packaging fork, not a maintained product branch.

Choose this fork only if you specifically need this older upstream snapshot. For most adopters, upstream is the better default because this fork shows no added capabilities and is 680 commits behind.

Choose this fork if you want Umami plus practical URL-based reporting and deployment tweaks, and you are comfortable carrying a large upstream lag. Avoid it if you want the latest upstream maintenance and broad feature parity.

This fork is best viewed as a near-upstream mirror, not a value-added variant. Choose it only if you want Umami with essentially no divergence and are fine absorbing the small upstream lag.

Choose this fork only if you specifically want a near-clean Umami baseline and are comfortable carrying a small upstream lag. For most adopters, upstream is the better default because it is more current and this fork shows no added capability.

This fork is not a differentiated variant of Umami; it is an older snapshot. Adopt it only if you specifically want a frozen baseline or plan to own all future maintenance yourself. If you want current fixes, Docker/build updates, and ongoing compatibility, upstream is the better choice.

Choose this fork only if the schema change is specifically what you need and you are willing to carry a large upstream rebase burden. For most adopters, upstream Umami is the safer default because this fork is only slightly customized but substantially behind.