Buy when you are ready
Pick a licence and a device count, see the total, pay by card. Past a set device count it stops being self-serve and becomes a conversation.
Editions
The edition decides what the agent is allowed to do.
Guard Essentials
Small teams starting with AI safety
See what is actually happening.
For a team that needs an evidenced answer to “is our data going into AI?” before it can argue for anything else.
- Guard on the AI websites staff already use
- Pattern and contextual detection on the device
- Log and warn, with alerts and a weekly summary
- Industry templates, so the first policy is not a blank page
No blocking and no desktop apps. Alerts live in the console.
Guard Pro
Most deploymentsCompanies using AI daily
Stop it, and prove you stopped it.
For a security team that has to prevent something, map it to a framework, and show an auditor that the control was running.
- Everything in Guard Essentials, plus:
- Desktop AI apps as well as the browser
- Redact and continue, not only block
- AI tool approval, so a new tool is a request rather than a surprise
- Compliance evidence packs: HIPAA, GDPR, PCI DSS, SOC 2
The edition most teams start on once discovery has run.
Itzal Business
One product for AI and everyday leaks
The other doors out of the laptop, too.
For an organisation that has decided AI is not the only way data leaves, and would rather run one agent than three.
- Everything in Guard Pro, plus:
- Shield: uploads anywhere, USB and sync folders
- Mail: Outlook and Gmail, checked while it is still a draft
- One policy and one console across all of it
Lens is available as an add-on rather than included.
Itzal Enterprise
Mid-market with a compliance team
Find it before it moves, and keep the evidence.
For a regulated estate with a compliance function: discovery as well as prevention, dedicated tenancy, and a named contact.
- Everything in Itzal Business, plus:
- Lens: which AI tools are in use, and where sensitive files sit
- Text in images, and Microsoft Purview labels honoured
- Dedicated tenancy, longer retention and legal hold
- A named contact for rollout
Local proxy mode is opt-in and installs a device-trusted CA.
Not a paid feature
The privacy architecture is not an upgrade.
On-device detection, irreversibly masked snippets, mutual TLS with no plaintext fallback and the encrypted local buffer are how the product works, at every tier, including the cheapest one.
There is no configuration in which raw content is transmitted, so there is no plan in which it is. A vendor who sells you privacy as an add-on is telling you what the default does. Read the architecture.
Compare
Every difference between the editions.
| Included | Guard Essentials | Guard Pro | Itzal Business | Itzal Enterprise |
|---|---|---|---|---|
| Guard on AI websites | ✓ | ✓ | ✓ | ✓ |
| Guard on desktop AI apps | – | ✓ | ✓ | ✓ |
| Redaction, and AI tool approval | – | ✓ | ✓ | ✓ |
| Alerts, weekly summary, industry templates | ✓ | ✓ | ✓ | ✓ |
| Compliance evidence packs | – | ✓ | ✓ | ✓ |
| Shield: uploads, USB and sync folders | Add-on | Add-on | ✓ | ✓ |
| Mail: Outlook and Gmail | Add-on | Add-on | ✓ | ✓ |
| Lens: AI tools in use, and where files sit | Add-on | Add-on | Add-on | ✓ |
| Dedicated tenancy, longer retention | – | – | – | ✓ |
In detail
| Feature | Guard Essentials | Guard Pro | Itzal Business | Itzal Enterprise |
|---|---|---|---|---|
| Capture | ||||
| Browser extension Chrome, Edge and Firefox, MV3 | ✓ | ✓ | ✓ | ✓ |
| Desktop AI apps the assistant installed beside the browser | – | ✓ | ✓ | ✓ |
| Clipboard and window-title fallback | – | ✓ | ✓ | ✓ |
| Uploads, USB and sync folders Shield | Add-on | Add-on | ✓ | ✓ |
| Outlook and Gmail Mail, while the message is still a draft | Add-on | Add-on | ✓ | ✓ |
| Local TLS proxy desktop AI apps, internal tools calling model APIs | – | – | – | Opt-in |
| Detection | ||||
| Pattern layer card numbers with Luhn, national IDs, IBANs, passports, cloud keys, private key headers | ✓ | ✓ | ✓ | ✓ |
| Contextual layer names and addresses in free text, rule-based | ✓ | ✓ | ✓ | ✓ |
| Custom patterns project codenames, customer ID formats, encrypted under your own key | – | ✓ | ✓ | ✓ |
| Model-based name detection recall on names in running prose, which the rules deliberately give up | – | ✓ | ✓ | ✓ |
| Text in images OCR on pasted screenshots and on the pictures inside documents | – | – | – | ✓ |
| AI tooling inventory Lens: which MCP servers, desktop apps and IDE assistants each device carries | Add-on | Add-on | Add-on | ✓ |
| Sensitivity labels honoured Microsoft Purview, in place of inference | – | – | – | ✓ |
| Policy and enforcement | ||||
| Framework mapping | PCI DSS, Internal | All eight | All eight | All eight |
| Actions available | Log, warn | Log, warn, redact, block | Log, warn, redact, block | Log, warn, redact, block |
| Policy scope org-wide, by department, by group | Org-wide | Per department | Per department | Per department |
| Sanctioned-tool exemptions and allowlists | – | ✓ | ✓ | ✓ |
| AI tool approval a new tool is a request, not a surprise | – | ✓ | ✓ | ✓ |
| Console and reporting | ||||
| Dashboard, alerts and case triage | ✓ | ✓ | ✓ | ✓ |
| Coverage reporting whether each capture path is currently working | ✓ | ✓ | ✓ | ✓ |
| Audit log and export records who looked at whose data | ✓ | ✓ | ✓ | ✓ |
| Compliance evidence packs HIPAA, GDPR, PCI DSS, SOC 2 | – | ✓ | ✓ | ✓ |
| Retention control per framework, clamped to your contract | Fixed | Per framework | Per framework | Per framework, with legal hold |
| Access and notifications | ||||
| SSO and RBAC OIDC or SAML, with group-to-role mapping | – | ✓ | ✓ | ✓ |
| Notifications email, Slack, Teams | ✓ | ✓ | ✓ | |
| Deployment and tenancy | ||||
| MDM packaging Intune, Jamf, Kandji | ✓ | ✓ | ✓ | ✓ |
| Data residency US or EU, immutable once provisioned | US | US or EU | US or EU | US or EU |
| Tenancy model | Pooled | Pooled | Pooled | Dedicated |
| Staged rollout controls ring-based, with a kill switch | ✓ | ✓ | ✓ | ✓ |
| Support | ||||
| Named contact and rollout assistance a person who knows your deployment | – | – | – | ✓ |
Response-time commitments are set in the contract rather than published here: they differ by region, and by whether proxy mode is in play.
Add-ons
Anything an edition leaves out is sold on its own.
Each product is a licence on the same install, so adding one is a line on the same invoice rather than a second rollout. An add-on is priced per device, like the edition it sits on.
Shield
Every other door out of the laptop: uploads to any site, USB, sync folders, printing.
Included in Itzal Business and Itzal Enterprise.
Outlook and Gmail, checked while the message is still a draft rather than after it is sent.
Included in Itzal Business and Itzal Enterprise.
Lens
Which AI tools are already in use, and where sensitive files are sitting on the devices you manage.
Included in Itzal Enterprise.
Built on request
SIEM delivery, SCIM directory sync and ITSM write-back are built for the customer who asks, against the system they actually run, rather than sold as a tier. Splunk, Sentinel, Google SecOps, Elastic, a webhook or syslog on the SIEM side; ServiceNow or Jira on the ticketing side.
That is a deliberate choice. These integrations are a day of work against a known target and a quarter of work against an unknown one, and a tier that promises them in general is promising the second. Ask during the evaluation and it is scoped before you sign.
What a plan actually is
Bought, switched on, and present are three different things.
A capability runs on a device only when all three are true. Collapsing them is how a console ends up green over a control nothing is running, which is the specific failure this product exists to prevent, so it is the one it refuses to produce.
-
01
Entitled: what you bought
Named by your licence. Nothing is implicitly included: a licence names what it grants and you get exactly that, so anything mandatory is mandatory because every licence includes it rather than because the code refuses to gate it.
-
02
Enabled: what you switched on
Your own admin’s decision, in your policy. Entitled but not enabled is a perfectly good state, and the console says so rather than reporting a gap.
-
03
Available: what the installed build carries
A property of the binary on each device, learned from heartbeats rather than decided centrally, because it differs across a fleet mid-rollout. Enabled but not available is the dangerous one, and the console renders it as an unfinished rollout rather than as coverage.
Unlicensed is quiet, not broken. A surface you have not bought is sent to the device as log‑only (still recorded, nobody warned, nothing blocked) and what you configured stays in your policy untouched and returns the moment the licence does. Frameworks and connectors are licensable individually, so packaging can be moved for one customer without a release.
What the console exposesBook a demo
See it stop a real one.
Forty-five minutes on your own data, run by one of our engineers. Bring something you would not want leaving the building.
Book a technical demoBefore you pay anything
Every organisation starts on a pilot, at no charge.
The pilot is a real contract with a length and a device count, not a demo account, and it ends by asking rather than by switching off: administrators are sent to the billing page, and the week before it lapses every page carries a reminder. It can be extended, or reopened after it has lapsed.
Billing periods
Monthly, quarterly, half-yearly or yearly. Each of the longer three is discounted against the monthly price; nothing about the product changes.
Change it mid-term
Add or remove devices, move licence, switch period. An increase is prorated and invoiced now, and applies once it is paid. A decrease applies immediately and the unused part becomes credit.
Every change is a new contract
The old one is closed rather than edited, so what you were paying for on any given day can be read off the record instead of reconstructed.
What drives cost
What moves the number.
Worth knowing before a conversation, so nobody is surprised by the shape of the quote.
Device count
Priced per device carrying the agent, not per person. Somebody with a portable and a desktop machine needs it on both, and a seat licence would quietly leave one of them uncovered.
Which licence
Guard Essentials, Guard Pro, Itzal Business or Itzal Enterprise, which is what decides the capabilities your devices are entitled to. Any product an edition does not include can be added on its own.
Residency and tenancy
A dedicated regional deployment costs more to run than a pooled one, and proxy mode carries a real support burden on top.
Billing period
The longer three periods are discounted off the monthly price. Nothing about the product changes.
Reducing a plan
Taking devices off is deliberate, and reversible.
Dropping below the number of devices already enrolled needs the box ticked, and the page names the devices that would go before you tick it.
What happens to a device that comes off
- The oldest enrolments are kept. The newest beyond the new count are revoked.
- Those devices stop reporting and stop receiving policy. Nothing on them is deleted.
- One audit entry lists every device revoked, so the change is on the record rather than inferred.
- Re-enrolling brings a device back as soon as the count allows it.
Straight answers
Why per device rather than per user?
Because coverage is a property of a device, not a person. Somebody with a device and a workstation needs the agent on both, and a seat licence would quietly leave one of them uncovered while the invoice said otherwise.
Can we start on one team?
Yes, and we would recommend it. Rollout is ring-based with a kill switch, and coverage is reported per device, so a pilot tells you what your real exposure looks like before you size the rest.
What happens if we stop paying?
Agents receive a back-off response and keep buffering locally rather than discarding events, so a billing dispute does not become a coverage gap. The console goes read-only, and your data is exportable throughout.
Does a cheaper plan mean weaker privacy?
No. On-device detection, masked snippets, mutual TLS and the encrypted local buffer are how the product works at every tier. The plans differ in what Itzal can detect and do: never in what it transmits.
Does Itzal see the message itself?
No. The check runs in a small program on the device, and the raw text is never transmitted, stored off the device, or written to a log. Your console receives finding types, frameworks and the action taken.
How long does deployment take?
One installer, pushed by your existing MDM. There is no appliance, no proxy and no certificate to distribute, and turning on another product later is a licence change rather than a second rollout.
What does Itzal not see?
Plenty, and we publish it rather than wait to be asked. Coverage is reported per surface and the uncovered ones are named. Surface coverage.
Is there a minimum?
No. Pricing is per device per month and the device count is the only number that changes it.
What happens if our fleet grows mid-term?
You add devices and the next invoice reflects them. Nothing needs redeploying.