Theta SentinelOffline AI watching the system
ThetaSecurity OS
Stock on the outside. Hardened all the way down.
A complete operating system built on the GrapheneOS hardened base. It has an offline AI security engine, live attack detection, honeyfile tripwires, and a post-quantum vault. To anyone looking at it, it is an ordinary Pixel.
- Device package, from
- $1,365.60
- Sentinel cloud calls
- Zero
- Telemetry
- None
IMSI watchForced 2G downgrades flagged
MTE armedMemory corruption faults in silicon
PQC vaultKyber and Dilithium at rest
Not a skin
An operating system, not a feature pack on someone else’s.
Most “secure phones” are a stock ROM with an app on top. ThetaSecurity OS is built upward from the GrapheneOS hardened base. The allocator, the permission layer, the network stack, and the storage vault are part of the system image, signed with our keys, and checked by Titan M2 at every boot. Sentinel watches all of it: the radios, the apps, and the mistakes people make.
What runs underneath
Six layers. None of them visible.
Camouflage outside. An on-device analyst inside. Live detection, zero-knowledge checks, defenses no other phone ships, and a hardware foundation under all of it.
01 — Camouflage
Nothing on the outside gives it away.
ThetaSecurity OS keeps the standard Pixel boot animation, the default Google and Pixel themes, and the stock interface chrome. There is no shield icon, no custom launcher, and no security branding. A border agent, a colleague, or a thief sees a retail Pixel. The defenses run behind the scenes, and nothing about the device signals that it is a high-security handset.
- Stock visual identityBoot animation, wallpapers, and system UI match a retail Pixel.
- No markersNo app, icon, or label announces what the phone is.
- Silent defensesAlerts appear only to the holder, in ordinary notifications.
02 — Theta Sentinel
A security analyst that lives in the phone.
Sentinel is a small language model that runs entirely on the device. It is a quantized GGUF build of SmolLM2-360M, executed by native llama.cpp through Android NDK and JNI bindings, in roughly 300 to 500 MB of RAM. It makes no cloud API calls and no server round-trips. It reads the hex logs and raw system events that no person should have to parse, and turns them into plain guidance in the notification shade.
It also watches the holder. Joining an unknown network, enabling installs from outside the shipped set, pairing a new Bluetooth device, letting the tunnel drop, or attaching a photo that still carries a location: Sentinel says so before it becomes a leak.
- Offline modelInference happens in device RAM. Nothing about your logs leaves the phone.
- Plain-language alertsCryptic events become a short warning and a clear next step.
- Human-error guardThe mistakes that undo careful devices are caught as they happen.
03 — Live detection
It notices the attack while it is happening.
The system is instrumented, not just locked. Radio state, tunnel integrity, and every sensitive permission request are watched continuously. Sentinel correlates the events and reports what they mean.
- IMSI-catcher defenseTelephonyManager is monitored for forced downgrades from 5G or LTE to the legacy 2G and 3G protocols that Stingray-class interceptors rely on.
- Tunnel watchdogConnectivityManager tracks routing integrity, so a Tor circuit drop, an unexpected disconnect, or an IP leak is caught immediately.
- AppOps auditingBackground attempts to reach the camera, microphone, or clipboard without real-time consent are intercepted and reported.
04 — Zero-knowledge checks
Protection that never learns who you are.
Two defenses that would normally mean trusting a server. On ThetaSecurity OS, the decision happens on the phone.
Breach and dark-web scanning
Check an email address or a password against breach databases with k-anonymity. The phone hashes the value with SHA-1 and sends only the first five characters of the hash. The matching happens locally. Neither ThetaSecurity nor the lookup server ever learns the credential or the identity behind it.
value → SHA-1 → 5-char prefix → local match
Zero-hop malware and phishing defense
A local VPN loopback service intercepts every DNS query on the device. Each domain is checked against an encrypted, offline Bloom filter of known phishing and malware hosts. A match is blocked before a single packet leaves the phone. There is no cloud filter, and no record of where you browse.
DNS query → loopback → Bloom filter → block
05 — Elite defenses
Defenses you will not find on another phone.
Built for the people who are targeted by name. These ship in ThetaSecurity OS, not in any stock or community build.
Honeyfiles and canary tokens
The system seeds invisible fake credentials and decoy documents in local storage. Nothing legitimate ever opens them. When spyware in the class of Pegasus, or a forensic extraction tool such as Cellebrite, touches one, the tripwire fires: a silent panic lock or a switch into a decoy profile.
decoy touched → tripwire → lock or decoy mode
Post-quantum vault
Sensitive files are sealed with post-quantum algorithms. Kyber (ML-KEM) protects keys, and Dilithium (ML-DSA) signs the vault. Both are layered over classical encryption. Data copied today against a “harvest now, decrypt later” plan stays sealed when large quantum computers arrive.
ML-KEM + ML-DSA · hybrid with classical crypto
Mesh emergency broadcast
When the cellular network is jammed, shut off, or blacked out, devices route encrypted SOS signals peer to peer over Bluetooth Low Energy and Wi-Fi Direct. Each handset relays the next. No tower, no internet, no server is required.
SOS → BLE / Wi-Fi Direct → peer → peer
Acoustic and optical side-channel shielding
Gyroscopes, accelerometers, and microphones can leak speech and keystrokes through vibration. The sensor arrays are monitored. High-rate sampling by apps that have no reason to need it is capped or refused, so side-channel harvesting does not get a clean signal.
sensor request → rate audit → cap or deny
06 — Hardware foundation
Under all of it, hardware that checks itself.
Every layer above rests on the Pixel’s security silicon, on memory that faults when it is corrupted, and on a base system with Google Play Services telemetry, background diagnostic logging, and cloud reporting stripped out by default.
Root of trust
An unbroken chain into Titan M2.
Pixel hardware is used because Titan M2 is a discrete security chip and Verified Boot is hardware-backed. ThetaSecurity OS binds its own keys into that chip, and the bootloader is locked. Each power-on rechecks the chain from silicon to system. A substituted image does not boot as a Theta device.
- SiliconThe root of trust is not a file the operating system can rewrite.
- Titan M2Theta keys are sealed in the security chip.
- Verified BootEvery power-on is checked against that hardware.
Memory hardening
A corrupted allocation faults. It does not run.
Pixel 8 and later ship the ARMv9 Memory Tagging Extension. Every allocation carries a tag, and the pointer must match it. A mismatch faults in the processor before injected code can execute. That stops buffer overflows, use-after-free, and injection exploits. Above the silicon, hardened_malloc splits size classes and places guard pages, so an overflow dies in the allocator.
- Tag matchThe pointer and the allocation agree, or the access faults.
- Size classesAdjacent objects are not one shared heap.
- Guard pagesA write past the object hits an unmapped page.
Provisioning custody
The image has one writer.
Devices are sourced factory-sealed and opened by Theta, not by a reseller chain. While the system and keys are written, the radios are held down and the bench is RF-isolated, so no nearby transmitter can interact with the handset. Verified boot is confirmed before the device is released.
- Factory sealChain of custody starts at the sealed carton, not at a shop counter.
- Radios held downNothing on the air is a peer of the provisioning host.
- Attest, then releaseThe boot state is checked before the handset leaves.
Communications
The baseband is not a trust boundary.
Data is routed through Tor or a zero-log VPN before it is useful to an observer. SIP signaling uses TLS 1.3. Media uses SRTP. An IMSI catcher can still see that a radio is present, and Sentinel tells you when one tries. It does not receive readable sessions, contact graphs, or call audio.
- TunnelTor or a zero-log VPN in front of application traffic, watched by the tunnel watchdog.
- Encrypted SIPTLS 1.3 for signaling. SRTP for the voice.
- Hostile basebandThe cellular radio is not asked to authenticate the user.
Guarantees
What the platform stands behind.
Properties of the device and of the order. They hold for the build we hand over. The safety rules are the operator actions that keep them true, and Sentinel reminds you of them.
Stock appearance
Boot animation, themes, and interface match a retail Pixel. No branding marks the phone as a security device.
Offline intelligence
Sentinel runs on the device. Its analysis, your logs, and your alerts never reach a cloud service.
Hardware-checked boot
Keys bound in Titan M2. Verified Boot intact. A replaced system image fails the check.
Memory faults closed
MTE and hardened_malloc crash memory corruption before it becomes code execution.
Zero telemetry
No Play Services telemetry, no diagnostic logging, no cloud reporting, and no account required.
Private settlement
Monero on every invoice. Bitcoin and USDT remain options. The order stores contact and configuration, not a dossier.
Hardware fleet
Pixel 8 through Pixel 11.
ThetaSecurity OS and the same key policy on every generation. The invoice rises with the silicon and the storage. Prices below are the 128 GB floor for each model.
Pixel 8
Tensor G3. First fleet generation with ARM Memory Tagging Extension.
From $1,365.60
Pixel 9
Tensor G4. Same Titan M2 key policy on a newer radio.
From $1,585.60
Pixel 10
Later silicon. Verified boot and MTE held to the same policy.
From $1,845.60
Pixel 11
Current flagship. Same key binding, more memory headroom.
From $2,145.60
Provisioning
From sealed carton to a checked boot chain.
Source
Factory-sealed Pixel hardware. Not opened along a reseller chain.
Install
ThetaSecurity OS is written with radios held down. One host. No peer on the air.
Bind and arm
Keys locked to Titan M2. Sentinel, canary files, and the vault initialized.
Attest
Boot state confirmed. No account. No telemetry. Then it leaves.
Services
When the work is a specific device.
Audit, private voice, and a custom build sit beside the fleet. The hardening engagement is $599.00 and does not include hardware.
Documentation
Every layer is written down.
How Sentinel reasons, what the detectors watch, how the vault and the tripwires work, and the safety rules that keep a careful device from being undone by an account, a SIM, or a backup.
Open the documentation- ThetaSecurity OSPlatform overview
- ThetaSecurity OSTheta Sentinel
- ThetaSecurity OSHoneyfiles and canaries
- OperationSafety rules
ThetaSecurity is operated under the corporate framework of CODES LTD. All rights reserved.
Order portal
Choose the silicon. Lock the invoice.
Pixel 8 at 128 GB starts at $1,365.60. Later models and larger storage are priced above that. Pay in Monero, Bitcoin, or USDT on the invoice that follows.
Open the order portal