Docs
Self-hosting (Community Edition)
Updated Apr 23, 2026
LogForMe has a free, open-source edition you can run on your own infrastructure. This is the Community Edition.
Why self-host
- Privacy: your data never leaves your server.
- Cost: free, forever. No usage caps.
- Control: modify, extend, or integrate however you want.
- Air-gap-friendly: works on a LAN, in a homelab, or on a private VPS.
At LogForMe, we respect your data privacy and handle it with the utmost care. The hosted service is built with the same focus on security and reliability, so your data stays protected.
Why not self-host
- Maintenance is on you: backups, updates, uptime.
- No hosted features: no managed AI verbal entries (requires your own LLM API key), no email delivery (requires your own SMTP), no managed backups.
- No support SLA: community support via GitHub Issues, not a ticketing system.
If any of those feel like yours, use app.logforme.com - the hosted service is one-click and handles all of it.
Repository and license
GitHub: <PLACEHOLDER: repository URL - to be provided>
License: GNU GPL v3.0. You can run, modify, and redistribute the Community Edition, but any distributed derivative work must also be licensed under GPL v3.0 and its source must be made available. See the LICENSE.md file in the repository for the full, authoritative license text.
The hosted service at app.logforme.com (Starter and Premium plans) is proprietary and not covered by the GPL - it's a separate codebase with additional cloud-only features.
Installation Guide (Docker)
See README.md at https://github.com/ahmed-fawzy99/LogForMe-ce.
What's in the Community Edition
Common with Hosted Service
- All core entities: Projects, Time Frames, Entries, Taxes, Preferences.
- Manual entry and stopwatch.
- Invoice generation (PDF download).
Excluded (hosted-only)
- Multi-user system
- Verbal commands
- Keyboard shortcuts
- Round-entries preferences.
- Soft-delete and restore (trashed UI).
- Dark mode.
- Languages other than English.
- Billing integration.
- Email invoice delivery.
- Analytics dashboards.
- Few UI/UX changes.
Backups
Your responsibility. At minimum:
- Database dumps on a cron (daily).
.envfile (off-server).
Test your restore procedure occasionally. "I have backups" is not the same as "I can recover from backups."
Getting help
- Bug reports: GitHub Issues on the repo.
- Feature requests: GitHub Discussions.
- Commercial support: not offered.