// how it works
No infrastructure to stand up and nothing to configure before it is useful. Four steps, and the fourth one is just using it.
Take the client package from this page. Windows and macOS, Python 3.9 or newer.
Paste your licence key on first launch. The local database and your settings are created for you.
Install Mail Shield on every employee machine with one shared company key. Point workers at the hub.
Run scans, review reports and hand out training from a dashboard on your own network.
// download
Download the client package, run it, and paste your activation key. There is no installer wizard, no cloud tenant to provision and no IT ticket — the whole thing is a folder on a machine you already own.
One platform key per company. One extension key per company.
// questions
No. Scans, reports, training records and game scores are written to a local database on the hub machine. Licence keys are verified with a signature check that happens on the client. There is no account to create and no endpoint to call.
Workers keep working. Anything they would have pushed is queued and retried, and if the hub has moved to a different address they rescan the subnet and reconnect to it.
It runs as a Chrome extension inside the tab you already have Gmail open in, and scores the message there. What leaves the machine is a report you chose to file, and it goes to your own hub.
Only the ones on your licence's allowlist. That is a deliberate limit: a scanner that will point anywhere is a scanner someone will eventually point at something they do not own.
Nexara checks for a newer release on startup and shows a banner in the dashboard. One click applies it, and your database and licence carry across untouched.
One employee machine running the Mail Shield extension. There are no per-user logins to provision — the company key covers everyone up to the seat count on your plan.