Supported devices

WraithLink runs on Google Pixel phones, and only on Pixel phones. That is a deliberate security decision, not laziness - the guarantees WraithLink makes depend on hardware that, in practice, only Pixels ship.

Why Pixel-only

Three hardware capabilities make WraithLink's design possible, and all three are rare outside the Pixel line:

• A relockable bootloader that accepts a custom key. This lets WraithLink turn verified boot back on after installation, signing the OS with its own key. Almost every other Android phone either can't be unlocked at all, or can be unlocked but never relocked - which means no verified boot and a permanently tamperable device.
• A dedicated secure element. Pixels include a discrete security chip that enforces attempt throttling and, crucially, can destroy key material on command. WraithLink's duress and panic actions rely on that hardware guarantee - the keys are gone, not merely "marked deleted".
• Long, prompt firmware support. Coercion resistance is worthless if the device is trivially exploitable. Pixels receive timely monthly firmware and driver patches, which WraithLink ships promptly.

What you lose on other hardware

On a phone without custom-key verified boot, an attacker who has the device can modify the system partition undetectably. On a phone without a secure element, "wiping" is a software promise that a forensic tool can often ignore. Either way the duress feature - the entire reason WraithLink exists - stops being trustworthy. We would rather support fewer devices properly than many devices badly.