Beta access · Updated

The JiggleGuard private beta

JiggleGuard is in a private beta for Windows computers. Here is what that means: who it's for, what's included, what isn't ready yet and what happens when you join the list.

How the beta works

  1. Join the list. Leave a work email. You'll get beta updates and launch news, nothing else, and you can unsubscribe at any time.
  2. We get in touch. We're inviting a small number of organisations and MSPs, in batches. We'll ask about your computers, how you deploy software and what you want to find out.
  3. Pilot. If it's a fit, we set up your organisation in the console and help you deploy the Windows agent to an agreed group of computers.
  4. Feedback. We'll ask what worked, what didn't and which flags were wrong. Beta feedback, especially false positives, shapes what we publish about accuracy.

Pricing hasn't been set. We'll tell you before anything is chargeable.

Who it's a good fit for right now

  • Organisations with company-managed Windows computers and a way to deploy an MSI (Intune, Group Policy or SCCM).
  • Teams willing to tell staff about the monitoring and review flags fairly.
  • MSPs who want to test it with one or two client organisations first.

Not yet a fit: Mac-only fleets (the macOS agent is in development), personal devices, or anyone looking for proof of misconduct from software alone.

What's included and what isn't ready

Included: the Windows agent, the web console (multi-tenant for MSPs), Slack, Microsoft Teams and webhook alerts, and CSV export.

Not ready yet: the macOS agent, email alerts, per-client billing and a code-signed installer. Field accuracy hasn't been measured; the beta is part of how we'll measure it.

Full details: feature status, IT deployment and data and privacy.

Join the beta list

We're inviting a small number of organisations to the private beta. Join the list for an invitation, or ask us a question first.