The poison0 agent's detection engine runs CPU-only by default: a minimal, locked-down trusted computing base. GPU acceleration is an optional speed choice you turn on deliberately. Here is exactly what it changes, and how we keep the GPU path safe.
The detection engine runs CPU-only by default, the smallest and most auditable setup; GPU acceleration is a separate build you switch on deliberately for more speed.
The GPU path ships as its own build; the CPU-only install is untouched.
It adds the graphics driver and compute runtime to the trusted path, and VRAM is less tightly bounded.
On every platform the engine has no network access at the OS level, re-validated under the GPU stack before shipping.
To reach the GPU the engine leaves the AppContainer and drops the integrity lowering; restricted token, job object and network block still apply.
The engine is signed and hash-pinned, and GPU mode needs an explicit, verified opt-in.
We ship GPU support platform by platform, only once its network isolation is re-validated under the GPU stack.
| Platform | Status |
|---|---|
| macOS (Apple Silicon, Metal)Shipping | Same kernel-enforced isolation as the CPU path. |
| Linux (Vulkan)Shipping | Same kernel-enforced isolation as the CPU path. Warm analysis 698 ms. |
| Windows (Vulkan)Shipping, with a stated trade-off | Warm analysis 224 ms against 7,454 ms on the CPU. The GPU start leaves the AppContainer and drops the integrity lowering; restricted token, job object and the App-ID network block still apply. See the sandbox article. |
Install the daemon and it runs CPU-only out of the box. Opt into GPU acceleration later, deliberately, when it ships for your platform.
Get the daemon