Frequently Asked Questions

Yes! TimeTracker is completely free and open source, released under the GPL-3.0 license. You can use it, modify it, and distribute it without any cost. There are no hidden fees, subscriptions, or premium features locked behind a paywall.

Basic technical knowledge helps, but TimeTracker is designed to be easy to deploy. If you're comfortable with Docker, you can have it running in minutes. We provide comprehensive documentation and step-by-step guides to help you get started, even if you're not a developer.

TimeTracker has minimal requirements. You need a server with Docker support, at least 512MB RAM, and a few GB of storage. It works on Linux, Windows (with WSL), and macOS. The application uses SQLite by default, but you can also use PostgreSQL for larger deployments.

Absolutely! TimeTracker supports unlimited projects, tasks, and clients. You can organize your work by client, project, or task, track time for each separately, and generate invoices for specific clients or projects. Perfect for freelancers and agencies managing multiple clients.

TimeTracker's invoicing feature lets you generate professional invoices directly from your tracked time. You can select specific time entries, add expenses, set hourly rates, and export invoices as PDF. The system tracks invoice status (draft, sent, paid) and supports multiple currencies.

Yes! Since TimeTracker is self-hosted, your data never leaves your server. You have complete control over your data, backups, and security. The application includes role-based access control, audit logs, and supports secure authentication methods. Your sensitive business data stays private.

Yes! TimeTracker supports unlimited users with role-based access control. You can assign different roles (admin, manager, user) with appropriate permissions. Team members can track their own time, view assigned projects, and managers can see team reports. Perfect for teams of any size.

You can get help through our GitHub repository. Report bugs or request features on GitHub Issues, participate in discussions, or check the documentation. For direct contact, email us at info@drytrix.com. Community support is also available through GitHub Discussions.

Yes—TimeTracker is GPL-3.0, self-hosted, and has no per-user license fee. You pay only for infrastructure (often a small VPS). See Toggl Alternative and vs Toggl for a feature-by-feature snapshot.

Yes. TimeTracker ships Docker Compose recipes so you can deploy in minutes. Follow Getting Started for the quick-start commands.

Each vendor exposes exports (commonly CSV/Excel) from their reports or account settings. Download clients, projects, tags, and detailed time entries, then map columns into TimeTracker. Start with a staging instance before cutover.

You need network connectivity to the server you host. Users on flaky networks can still log time once reconnected, and mobile browsers work against your HTTPS endpoint.

Self-hosting helps: data stays on infrastructure you control. You still must configure TLS, retention, DPIAs, and subprocessors for your organization—but you are not shipping employee time data to a SaaS vendor by default.

Cloud tools host your database for you (fast setup, recurring fees). Self-hosted means you operate the app—lower long-run cost at scale, stronger data residency, more operational responsibility.

SaaS trackers often land around $9–$18 per user per month once you need invoicing and reporting—thousands per year for ten people. TimeTracker avoids per-seat licensing; budget hosting and admin time instead.

Yes—export Toggl reports to CSV, normalize to your project structure, import into TimeTracker on Docker, and run parallel tracking for one cycle to validate totals.

Yes. Generate invoices from tracked time, manage statuses, and export PDFs without paying a separate invoicing subscription.

Yes. Larger teams can configure PostgreSQL for concurrency and backup tooling you already trust.

TimeTracker is web-first. Mobile browsers work against your deployment; many teams bookmark the timer page for one-tap access.

Because you own the server, snapshot the database volume and configuration regularly. Test restores—SaaS cannot compete with your ability to keep cold copies offline.

Follow GitHub releases, read notes, and roll out updates on staging first. Open-source means you choose when to upgrade.

Browse Screenshots for dashboards, timers, reports, and invoicing.