Project and task management decision
Timeular
A competent developer can build a useful automatic time-tracking replacement (collector + backend + reports) in a few weeks, but reproducing the vendor’s hardware, broad integrations, polished cross-platform apps, and enterprise features is larger work better left to the commercial product.
Visit website↗Open-source builds that already do this
Every project below is open source and already does this job today. Fork one, self-host it, or take the parts you need - the build prompt further down assumes an empty file, and this is the shortcut past that. Licences differ; check the one on each card before you ship. All Timeular alternatives, with the arithmetic →
What a replacement has to do
- Collect app/website/activity events, convert to time entries, allow user corrections/notes, aggregate into timesheets/reports.
What it still won’t have
- Official desktop and mobile apps (production polish and installers)
- Physical Tracker hardware and flip-to-track UX
- 3000+ Zapier connectors and marketplace integrations out of the box
- Enterprise features (SSO, dedicated success manager, migration support)
- Priority technical support and bespoke onboarding
What remains hard
- Product polish and ongoing maintenance
First-year cost
Keep paying
Paying is—cheaper in year one.
On cash alone, building overtakes the subscription at 1 seat.
Money you would actually spend
Time you would spend
—
What you would spend
What we assumed
The verdict above measures whether you could build it. This one is only about money.
Runnable build prompt
Build a minimal self-hosted automated time-tracker using Node.js (Express), Postgres, React, and an Electron desktop client. In scope: (1) Electron app that records active window/app/URL and sends events to the backend, (2) backend API to ingest events, deduplicate and create time entries, (3) React web UI to view/edit time entries, tag entries, assign to projects, export CSV/PDF, and simple reports (weekly/project), (4) calendar sync (Google Calendar OAuth) to import events and suggest time entries, (5) simple authentication (email+password) and role-based access for teams, (6) unit and integration tests, error handling, logging, migrations, and Docker deployment manifests. Out of scope: physical hardware Tracker, Zapier marketplace connectors, SSO, enterprise migration services, mobile apps. Require automated tests for core flows, input validation, rate limiting on ingestion, and a README with setup and backup instructions.
How we checked
How the score was reached
- Partly verdict base52
- An open-source build was found+5
- 5 cited sources+3
- 3/3 assessment runs agreed+4
- Evidence score64
The base comes from the verdict. Everything under it is a check that either happened or did not, and each one is a fact frozen in this record rather than a judgement made at render time - so the same evidence always produces the same number.
How scoring works →Cited sources · 5
Every page the run actually retrieved.
- official productEARLY - official product
- official docsEARLY - How it works
- official pricingEARLY - Pricing
- open sourceActivityWatch/activitywatch
- open sourcekimai/kimai
Integrity checks
What held up, and what did not.
