System requirements
The on-device engine needs modern CPU vector instructions and a kernel-enforced sandbox. This page lists the CPU baseline, supported hardware, and the per-operating-system prerequisites.
CPU baseline
- x86-64: AVX2 (Intel Haswell/2013+, AMD Zen+).
- ARM64: i8mm / Int8 matmul (Apple M2+; Apple M1 is not supported).
Hardware below this line is not supported. The installer warns early; the daemon enforces the same check fail-closed before the engine starts.
Supported hardware
| Platform | Hardware |
|---|---|
| macOS (Apple Silicon) | Apple M2, M3, M4 and newer |
| macOS (Intel) | Macs with AVX2 (Intel Haswell/2013 or newer) |
| Linux x86-64 | Intel Haswell/2013+, AMD Zen/2017+ - all with AVX2 |
| Linux ARM64 | AWS Graviton 3/4, Ampere One and others with i8mm |
| Windows x86-64 | Intel Haswell/2013+, AMD Zen/2017+ - all with AVX2 |
| Windows ARM64 | Snapdragon X (Copilot+ PCs) with i8mm |
Not supported
| Platform | Hardware | Reason |
|---|---|---|
| macOS (Apple Silicon) | Apple M1 | no i8mm |
| x86-64 (any OS) | Intel before Haswell, AMD before Zen, many Atom/Celeron/Pentium | no AVX2 |
| Linux ARM64 | AWS Graviton 2, Ampere Altra | no i8mm |
| Windows ARM64 | Surface Pro X (SQ1/SQ2) and older ARM devices | no i8mm |
Operating system requirements
The inference engine runs in a kernel-enforced sandbox. The one honest platform prerequisite is on Linux:
| Platform | Requirement |
|---|---|
| macOS | Kernel Seatbelt sandbox, always available. |
| Linux | Kernel ≥ 5.13 with Landlock active: Ubuntu ≥ 22.04, Debian ≥ 12, RHEL ≥ 9.6 out of the box. Otherwise enable it via the boot parameter lsm=landlock,…. |
| Windows | Network-isolated AppContainer (no network capability), layered with a restricted token (all privileges stripped, low integrity) and a Job Object; the data directory must sit on an NTFS volume. With GPU acceleration (Melira Enterprise Ultra) the AppContainer falls away - the graphics driver does not start inside it; network block, token, integrity and Job Object remain. |
| Containers | The default Docker seccomp profile blocks the Landlock syscalls - an adjusted profile is required. |
| No Landlock | No on-device analysis on this host: suspicious changes are recorded and surfaced, never waved through unsandboxed. |
Windows: NTFS data directory
On Windows the model is materialised into a hidden NTFS alternate data stream, so the data directory must sit on an NTFS volume:
- exFAT and FAT32 have no alternate data streams at all.
- ReFS imposes a stream-size limit too small for the model.
- The system volume is NTFS on effectively all Windows installations (the default); the installer verifies the file system up front and stops with a clear message if it is not NTFS.
Check it yourself
bashTerminal
# Apple Silicon: 1 = supported sysctl hw.optional.arm.FEAT_I8MM # Intel Mac: sysctl -a | grep AVX2
bashTerminal
grep -o 'avx2\|i8mm' /proc/cpuinfo | sort -u
powershellPowerShell
# Check the CPU model against the tables above. Get-CimInstance Win32_Processor | Select-Object Name
Strictly fail-closed. If the sandbox is not available, the engine does not start - suspicious changes are recorded and surfaced, never waved through unevaluated. How the engine sandbox works →
Was this helpful?
Check the box, then protect the device.
Free for Linux, macOS and Windows. Install once, updates run automatically.
Sign me up