BeaverHabits

BeaverHabits is a lightweight, self-hosted habit tracker that lets you log and check off daily habits through a minimal, privacy-focused web interface without…

  • Productivity
  • Tools & Utilities
BeaverHabits is a lightweight, self-hosted habit tracker that lets you log and check off daily habits through a minimal, privacy-focused web interface without any cloud accounts.

Platform availability

Available on 1 of 10 platforms

  • Unraid (not listed)
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS (not listed)
  • Proxmox
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)
  • Any server (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

61/100 Good

Maintained
86last commit 5 days ago
Popular
651,865 GitHub stars
Easy to install
251 install platform, install notes
Light to run
100256 MB minimum RAM
Security check
103 serious findings, 10 minor, CI, tests

Availability: platform listings confirmed today, links checked today

GitHub stars
1,865
Open issues
18
Last commit
2026-11-16
Latest release
v0.10.0
License
BSD-3-Clause
Activity
rising

Checked today - source: GitHub (daya0576/beaverhabits)

Resources & Compatibility

Minimum requirements: 256 MB RAM, 1 CPU core(s), 100 MB disk.

Checked 40 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create and verify your first account Once BeaverHabits is running, register a user and finish the account verification step before creating habits. If you skip it, you may not be able to log in or use the app. source
  • Log in to use the habit API After registering, log in to get a JWT (a login token the app uses to identify you). Without that token, the app will not know whose habits to create or save. source
  • Check /health before setup Open the /health endpoint in a browser to confirm the service is up before you start configuring or using it. If this page fails, the main app and habit tracking will not work either. source

Fetched 40 days ago - each note links to its source

Alternatives

No alternatives collected yet.

Common questions

Which port should I expose for the BeaverHabits container?

The Docker examples use port 8080, so map your host port to container port 8080.

Where is BeaverHabits data stored, and what should I back up?

It can store data in a single SQLite database named habits.db in DATABASE mode, or in a local JSON file in USER_DISK mode. The Docker examples keep that data in the mounted ./beaver/ directory under /app/.user/.

How can I skip authentication for a trusted local user?

Set the TRUSTED_LOCAL_EMAIL environment variable to that user's email address. The compose example describes this as skipping authentication.

Why might BeaverHabits have permission problems with the mounted volume?

The container starts as nobody, so the host folder must be owned by the same UID as the container user. The compose example sets user 1000:1000 to align ownership.

Is there a native iOS app for BeaverHabits?

Yes, the repository lists an iOS Native App that is offline-first. It also lists an Apple Shortcut for sharing the app on iPhone.

Answers sourced from github.com

Community

Collected 48 days ago - public community threads