The whole product

Seventeen capabilities. And only these.

This is the entire product surface for the first release — nothing hidden in a roadmap, nothing padded to look complete. Deep on capture and sign-off, and deliberately finished at approved hours.

01

Tracking modes

4

Four ways to capture time, under one policy engine.

01

Manual start/stop timer

Nothing is captured until you press Start, and nothing after you press Stop. No confirm step, no arm state — the clock begins the instant you click.

02

Automatic 24/7 tracking

Continuous, zero-action capture — bounded by policy, and the member always knows the boundaries. Available continuously or inside a working-hours fence.

03

Scheduled auto-start

Tracking reaches its running state within seconds of login, inside the capture window — no button, no daily ritual, no member action required.

04

Silent / windowless agent

No tray, no window, no notifications. Off by default and heavily gated: Business+, permitted region, company-owned device, a signed Owner acknowledgement, and an audit entry — blocked outright in the EU and every safe profile.

02

Capture

11

What the agent records — counts before content, scores before screenshots.

05

Screenshots

Captures at a policy-set rate, offset so you are never photographed mid-click, and cancelled the instant you stop — no screenshot can land after Stop.

06

Screenshot-free "score only" mode

The image-free alternative that deploys where every screenshot vendor is banned. Nothing to blur, redact, subpoena or leak. Ships on every plan, including Free.

07

Employee can delete own screenshot

Where policy allows it, you delete your own captures. Your manager sees that a slot was removed, with count and timestamp — never what was in it.

08

Live screen view

A manager can view a live screen only with scoped permission — behind a persistent, non-dismissible indicator the whole time, and every session is audit-logged.

09

Webcam verification

Optional presence-of-person verification, blocked without a stored written consent record wherever biometric law (such as Illinois BIPA) requires one.

10

App & website tracking

The foreground app and site, with duration, categorized productive / neutral / unproductive per role and department — the foundation of every activity report.

11

URL / search-query capture

Capture depth is a policy field, capped by your compliance profile — domain-only under GDPR-safe, full URL only where the profile permits it.

12

Keystroke / mouse counts

We count key and mouse events to compute activity level. Keystroke content is never recorded. There is nothing typed to read, index or leak.

13

Idle detection

No input for a while becomes idle, then away. Idle minutes are always stored and always visible to the member, and never silently deleted.

14

Offline tracking & sync

The agent keeps tracking and buffering with no connection, then uploads the backlog chunked and idempotently — no lost minutes, no duplicate entries.

15

Manual offline-time entry

Record time spent off-device — a client meeting, a site visit. Labelled self-reported, counted in tracked time, never counted as active input.

03

Attribution & sign-off

2

Where the time went, and the hours someone signs off on.

16

Projects & tasks

Attribute every entry to a project and task — by hand, by app-pattern rule, or from a running timer — so both modes answer where time actually went.

17

Timesheet approval workflow

The sign-off step and the hand-off point: submit, review, approve, lock the period, and export approved hours as CSV, XLSX or over the API.

Seen in the product

How the marquee features actually work.

The capabilities above, shown the way they behave in the app — the policy engine, capture, live view and the sign-off that exports clean.

One policy engine

Two modes, resolved to one effective policy

Every capability is a field on a versioned policy that resolves across five scopes — workspace to device — and is validated against the jurisdiction before it can be saved.

  • Most-specific scope wins, field by field
  • Compliance rules subtract, never silently add
  • Simulate a change before it reaches a single device
How the modes work
Effective policyHybrid
Workspacebase policy
Department
Team — Designscreenshots 6/hr
Member — Karanhybrid mode
Device — MacBook
GDPR-safe profile forces screenshots ≤ 4/hr, blur on — resolved, not overridden.
Capture, your way

Screenshots — or a real number with no image at all

Run periodic, jittered, optionally-blurred screenshots, or switch to score-only mode and deploy where every screenshot vendor is banned. Both ship on every plan.

  • Employees can delete their own captures
  • Score-only leaves nothing to blur, redact or leak
  • Keystrokes are counted, never recorded
See the analytics
Screenshots6/hr
74%
33%
88%
12%
Score-onlyno image
82
screen productivity
Nothing unseen

Live view that the member always sees

A manager can view a live screen only with scoped permission, behind a persistent, non-dismissible indicator the entire time — and every session is audited.

  • A red banner shows the whole time it is active
  • Off by default; enabled per policy
  • Actor, target, duration and reason are logged
Security & compliance
Live screen view● Live
Your screen is visible to a manager right now
Every session is audit-logged with actor, target, duration and reason.
The hand-off

Timesheets that export clean and stop there

Submit, review, approve, lock the period, and export approved hours as CSV, XLSX or over the API — into whatever you already use to invoice or pay. We compute hours; we don't compute money.

  • Immutable before/after audit on every edit
  • Locked periods can't be quietly changed
  • Approved hours are the product's only output
Compare plans
Week of Sep 22 Approved
M
T
W
T
F
S
S
36h 30m · signed offCSVXLSXAPI
Deferred versus never

There's a difference between not yet and not ever — and we're clear about both.

Some things are legitimate later, and will be built when they're ready. Others will never exist, because they'd pull us into a different product with a different legal regime. Both lists are public.

Deferred — legitimate later

Not in the first release, but on the table.

  • AI app classification
  • Distraction & burnout signals
  • Anomaly detection
  • Goals & leaderboards
  • Configurable alert rules
  • Custom report builder
  • Client portal
  • Third-party integrations (Jira, Slack, Teams)
  • Mobile apps
  • Browser extension
  • Webhooks
  • SSO / SCIM
  • White-label
  • On-prem

Never — permanent non-goals

A stated boundary reads as confidence.

  • Attendance— Punch in/out, presence, punctuality and absenteeism pull us into HR system-of-record territory and country-specific labour rules.
  • Invoicing— A finance workflow with tax, currency and compliance surface far beyond our value.
  • Payroll— Statutory exposure and per-country rules — a system-of-record obligation we will not carry.
  • Budgets vs estimates— A project-management concern that belongs to Jira, Asana or ClickUp.
  • Shift scheduling— Rostering is its own product category.
  • Leave & holiday management— HRIS territory.
  • Geofencing— Location enforcement is a distinct legal regime and a different product. No GPS, no IP-based location, ever.
We compute hours. Other systems compute money. Why we drew the line here.