Track habits, tasks and notes with time tracking, calendar view and completion statistics.
License: GPL-3.0. Built with: C#, HTML, JavaScript, CSS, Python, Dockerfile. Website: https://openhabittracker.net. Source: https://github.com/Jinjinov/OpenHabitTracker.
APPSETTINGS_USERNAME=admin [email protected] APPSETTINGS_PASSWORD=admin APPSETTINGS_JWT_SECRET=your-extremely-strong-secret-key ``` Replace `your-extremely-strong-secret-key` in Windows terminal: ``` [System.Convert]::ToBase64String([System.Security.Cryptography.RandomNumberGenerator]::GetBytes(32)) ``` Replace `your-extremely-strong-secret-key` in Linux / macOS terminal: ``` openssl rand -base64 32 ``` docker-compose.yml ``` services: openhabittracker: image: jinjinov/openhabittracker:latest ports: - "5000:8080" environment: - AppSettings__UserName=${APPSETTINGS_USERNAME} - AppSettings__Email=${APPSETTINGS_EMAIL} - AppSettings__Password=${APPSETTINGS_PASSWORD} - AppSettings__JwtSecret=${APPSETTINGS_JWT_SECRET} volumes: - ./.OpenHabitTracker:/app/.OpenHabitTracker
Self-hosting gives you three things SaaS can’t: data ownership (the files live on disks you control), cost predictability (a one-time setup vs. recurring per-seat fees that grow with your household or team), and longevity (open-source means the app keeps working even if the maintainers move on, since you can pin a working version). The trade-off is that you take on the operational work of running a server, applying updates, and handling backups.
Most self-hosted apps run comfortably on modest hardware — a Raspberry Pi 4, a mini PC, a NAS with Docker support, or a small VPS is usually enough for personal or family use. CPU and RAM requirements scale with how many simultaneous users or how much data you push through OpenHabitTracker. Storage requirements depend on the kind of data you keep; check the README for guidance on data retention.
Last verified: 2026-04-21