WorkMonitor for IT & Security
Deploy to the whole fleet, then prove where the data went
Agents that roll out without a hand on every laptop, tenant isolation enforced in the database rather than promised in a diagram, and a tamper-evident trail of who saw what.
Free for two seats, no card.
- Rolling an agent out means touching machines you will never see.
- Admin or nothing, so half the company can read the other half.
- A log an insider with admin rights can quietly edit.
IT & Security
What changes for IT and security
Pick a line and the page it happens on opens on the right.
Rollout
Standing this up without a desk visit
- 1
Enrol the fleet remotely
The enrol → session → ingest protocol plus signed release packaging and an appcast auto-update, so the rollout does not require touching a machine.
- 2
Wire identity to what you already run
Okta, Entra and Google are among the nine connectors, with SSO over SAML/OIDC and SCIM v2 provisioning configured from Settings.
- 3
Scope roles to the org tree
Custom roles bind to a node rather than to the whole tenant, and the scope is enforced on the server against the session rather than against the URL.
- 4
Turn on the signals, then the export
Egress and integrity signals feed the anomaly feed, and SIEM export carries them into the stack your team already works in.
A tool you have to trust vs. one that proves itself
workmonitor.vsAgent tooling as it usually ships
Rollout
With WorkMonitor
Remote enrolment, signed packaging, and auto-update through an appcast manifest.
Agent tooling as it usually ships
Ship laptops, or talk somebody through an installer on a call.
Tenant isolation
With WorkMonitor
Composite foreign keys make a cross-tenant row a database error, not a code-review question.
Agent tooling as it usually ships
Enforced in application code, which means enforced until somebody forgets.
Access scope
With WorkMonitor
Roles scoped to a node in the org tree, with every access to a person’s data written to a hash chain.
Agent tooling as it usually ships
Admin or nothing, so the blast radius of one compromised login is the whole company.
Tamper evidence
With WorkMonitor
Append-only and hash-linked, so a removal breaks the chain and the break is detectable.
Agent tooling as it usually ships
Deleting rows from a log table leaves no evidence that rows were deleted.
Insider signals
With WorkMonitor
Egress and integrity signals with the surrounding activity attached, and the day reconstruction one click away.
Agent tooling as it usually ships
An alert with a number in it and nothing behind it.
Automation
With WorkMonitor
A typed v1 REST API, scoped keys, OpenAPI spec and HMAC-signed partner webhooks.
Agent tooling as it usually ships
A CSV export and a scheduled job somebody wrote once.
What IT and security get to work with
- Enroll→session→ingest protocol
- Device enrollment & pipeline
- Agent auto-update (appcast/Sparkle, signed manifest)
- Signed release & packaging
Ask AI
Ask AI about your fleet
Answers drawn from the device inventory, the access log and the anomaly feed.
Pick a question above and WorkMonitor AI will answer from your team's real numbers.
The status meeting, already written
Status is normally assembled by asking. Here it is already: hours, activity, attendance and risk on one board, for one person or the whole company. Set the thresholds once and it tells you who needs you.
Jobs to be done
The jobs a security team runs here
- Catch insider threats earlyEgress signals, anomaly detection and integrity checks on a hash-chained trail that records the investigators too, so the finding survives being examined.
- Monitor apps & websitesEvery app and site classified, every day replayable as a timeline. You see which tools are eating the week and which teams they are fragmenting.
- Monitor legally & stay compliantVersioned consent, a capture scope that cannot quietly widen, retention and DSAR handling, and written guidance for 32 jurisdictions before you roll out in one.
- Catch anomalies with smart alertsAnomaly detection against your own baseline, six named agents on specific jobs, evidence-cited summaries, and delivery to a channel your team already reads.
Straight answers
The questions we would ask in your position
Every answer here is the one you would get on a call. Open as many as you like; they stay open, so two can be held side by side.
Active application and window titles, input activity as a signal rather than keystrokes, and screenshots when your capture policy asks for them. Per-app privacy deny-lists stop named applications entering the record at all, and the agent applies those rules on the device, before anything is transmitted.
Isolation is enforced at the schema level: composite (id, orgId) foreign keys mean a record cannot be joined across organisations even if application code asks for it. On top of that, 310 server-side checks confirm a record belongs to your organisation before it is returned, and the scope comes from the credential rather than from the request path.
Yes, and it is the default posture rather than an add-on. Roles are scoped to a node in the org tree, so a team lead sees their team and a regional manager sees their region. Access itself is recorded, so "who looked at this" has an answer.
Native agents for macOS, Windows and Linux, a browser extension, and a VS Code companion with a developer self-view. All of them enrol once and write into the same ingest pipeline, so a mixed fleet produces one record shape rather than four.
Nearby
Teams with the same problem, from another angle
Take these with you
The software is the easy part of a rollout
Here is what we would send a manager doing one for the first time: how to read a productivity number, what to say to a remote team before anything is installed, and a policy you can adopt as written.
Point it at one team for a week.
Create the account, put the agent on a handful of desks, and leave it alone. On Friday you read the week instead of reconstructing it: hours against their projects, focus and idle per person, and the timesheets already filled in.
Free for two seats. No card, and no sales call to sit through.