I built *[TimeTracker](https://github.com/DRYTRIX/TimeTracker)*, an open-source, self-hosted time tracking app for freelancers and small teams who want full control of their data.

Most time trackers I tried either:

* lose your running timer if the browser closes, or * lock you into cloud services.

I wanted something simple, reliable, and offline-friendly — so I built TimeTracker.

### Key Features

* *Persistent timers* (server-side, survive browser closes/reboots) * *Team support* (multi-user, roles, projects/clients, billing) * *Reporting & exports* (project/user breakdowns, CSV) * *Self-hosted* (Docker, Raspberry Pi friendly) * *Responsive interface* (Flask + HTMX + WebSockets for live updates)

### What’s New in the Latest Release

* Improved reporting and exports * Cleaner UI/UX, faster navigation * Optimized performance & stability * Better Docker configs and documentation

### Try It

```bash git clone https://github.com/DRYTRIX/TimeTracker.git cd TimeTracker cp .env.example .env docker-compose up -d ```

Then visit `http://localhost:8080` and start tracking.

### Who It’s For

* Freelancers who want full control of billable hours * Small teams who prefer LAN or Pi-based solutions * Anyone who wants to own their data without SaaS dependency

### What’s Next

Mobile apps, integrations (Zapier, Slack), richer analytics, and internationalization.

I’d love feedback from the HN community — especially around usability, reporting, and team workflows.

Repo: [https://github.com/DRYTRIX/TimeTracker](https://github.com/DRYTRIX/TimeTracker)