What it does
Desktop app that runs quietly
A native desktop application records working time without anyone having to remember a timer.
Periodic screenshots
Screenshots are captured at intervals through the working session and stored encrypted.
Activity scoring
Keyboard and mouse input are combined into an activity score, weighted across distinct keys, productive keystrokes, clicks, scrolls and pointer movement.
Idle detection
Tracking pauses automatically when the machine goes idle, so breaks are not billed as work.
Editor and browser extensions
A VS Code extension records commits, file saves and editing activity. A browser extension covers work done on the web.
Automation detection
Raw input patterns are analysed on the server to identify simulated activity such as key repeaters and mouse jigglers.
Be straight with your team
Activity tracking only works when people know it is running and why. We would rather you deploy it openly than quietly.
What is recorded
- Working time in tracked sessions
- Keyboard and mouse activity volumes
- Periodic screenshots during sessions
- Editor activity, if the extension is installed
How it is handled
- Screenshots are stored encrypted
- Tracking pauses automatically when the machine is idle
- Data belongs to your own deployment
- Access follows the same role permissions as the suite
From tracked hours to a sent invoice
The tracker is most useful when the hours it records end up on a bill without being retyped.
The desktop app records the work
Time, activity and periodic screenshots are captured on the machine while someone works, without them managing a timer.
Hours land against projects
Tracked time is attributed to projects and people, split into billable and non-billable.
Invoice the billable hours
If you also run the Finance app, tracked project hours convert into invoice lines at the project rate.