Key takeaways
- A tracking agent should be small and quiet; Tauri keeps the footprint low
- Aggregate state changes locally instead of streaming raw events
- An offline queue means no data is lost when the network drops
- Batch uploads are signed with a device credential
A small footprint matters
An agent runs all day on every employee machine. Memory and CPU use are part of the product. Tauri pairs a Rust core with the system webview, so it avoids shipping a full browser engine with every install.
Detect, debounce, aggregate
The agent watches for changes: the focused application, the window title, input activity. It debounces noisy changes and records state transitions rather than every raw event. That keeps traffic small and keeps content out of the pipeline.
An offline-first queue
Laptops sleep, Wi-Fi drops and VPNs reconnect. Events are written to a local queue and uploaded in batches when the API is reachable, so a gap in connectivity does not become a gap in the report.
Enrollment and trust
A device registers with a short-lived enrollment code issued by an organization admin and receives a device credential scoped to that organization, employee and device. Every upload is made with it.