Behavioural engine

An engine that
reads intent.

Every new file is judged on what it would do, on your machine, and every verdict comes with its reasons.

How a verdict is made

Judged on behaviour,
not on a list.

Three files go through the engine. Each behaviour adds weight until the score settles on a verdict.

invoice_0423.exeunsigned · 2.1 MB · first seen now+14enumerates 1,204 documents+32deletes volume shadow copies+28renames files to *.locked+12writes a Run key+8contacts 185.220.101.4700risk scorereading intent…EVIDENCERules…Hash…Intel…

An unsigned download reads every document, deletes the backups and renames files. It is quarantined before it encrypts one.

Download for Windows
  • Intent scoring

    Behaviour is simulated and scored, so an unknown file is judged on its actions.

  • Layered evidence

    Rules, reputation and threat intelligence add weight. The verdict never depends on them.

  • Works offline

    Analysis runs on the machine. Losing the network never lowers protection.

Built to decide
on the machine.

  1. 1

    Runs on the machine

    Analysis happens on the endpoint, so a file never has to leave it to be judged.

    How your data is handled
  2. 2

    Explains every verdict

    A verdict lists the behaviours that decided it, in plain language, so you can see why a file was held.

    Understanding verdicts
  3. 3

    Never waits on the network

    Losing the connection never lowers protection. Detection updates arrive in the background and are verified before they load.

    How updates work

Every hold comes
with a reason.

When a file is held, you see what it is, what it tried to do and what you can do next.

  1. What it is

    The file's name, its signer, its size and when it first appeared.

  2. Why it was held

    The behaviours that decided the verdict, most serious first.

  3. What you can do

    Keep it in quarantine, restore it, or delete it. Every decision is kept in a local history.

invoice_0423.exe

Unsigned · 2.1 MB · first seen now

Malicious · quarantined

Why it was held

  • Deleted volume shadow copies, so files could not be restored
  • Renamed documents to *.locked, which is what encryption looks like
  • Read 1,204 documents in bulk straight after launch
Keep in quarantineRestoreDelete
Illustration of a held file.

Why before matters

By the time an alert fires,
the damage has started.

How we measure the engine

FAQ

Questions about
the engine.

No. Analysis runs on your machine, and losing the network never lowers protection. Detection updates download in the background whenever a connection is available.

No. Files are judged where they are. Crash reports, metrics and threat sharing are separate settings, and threat sharing starts off.

That is the case it is built for. An unknown file is judged on what it would do, so it does not need a signature to be stopped.

It waits in quarantine, where it cannot run. You can keep it there, restore it if the verdict was wrong, or delete it, and every decision is kept in a local history.

The engine stays under 150 MB of memory, so it fits alongside everyday work on Windows 10 and 11.

Detection updates refresh in the background and are verified before they load. Application updates are never installed silently: you choose when to apply them.

Nothing runs until it has been read.

Free for 14 days, with no card required.

Available for Windows 10 and 11.