Everyday Mode
Normal daily phone use: banking, calls, messages, maps, and normal apps. Designed as the practical layer.
Alpha-stage concept
Mobile sovereignty, built in layers.
TridentOS is a secure mobile OS concept built around four device states: everyday use, hardened privacy, offline work, and duress response.
Why TridentOS exists
Most phones treat privacy as a setting. TridentOS treats privacy as a state.
Modern phones mix banking, browsing, identity, messaging, work, and tracking into one exposed environment. For privacy-focused users, the problem is not only which app is installed. It is whether daily life, sensitive work, offline notes, and duress response all share the same state.
TridentOS is being designed around different unlock states for different risk levels. The goal is practical separation: an everyday phone when needed, a hardened privacy state when appropriate, an offline workspace when network exposure is not acceptable, and a planned duress workflow for high-risk moments.
Four-state model
Different states for different risk.
These are planned development goals until implemented, tested, and documented.
Secure Mode
Private browsing and communications goals, privacy-routing where technically possible, an encrypted vault concept, and a hardened app environment goal.
Offline Mode
No network-dependent workflow, local files and notes, aggressive radio shutdown goals, and airgapped-style behaviour where hardware allows.
Killswitch / Decoy Response
Passcode-triggered duress workflow goals. Wipe or decoy behaviour is planned and depends on hardware, encryption state, implementation quality, and testing.
Second-state integration targets
Native privacy rails for Secure Mode.
Secure Mode gets stronger when privacy infrastructure is part of the device state, not scattered across separate apps. TridentOS wants serious conversations with the Monero, CakeWallet, Mullvad, and wider privacy ecosystem about what should be built into the second state from day one.
If you know a stronger privacy rail, bring it to the table. Better wallet, routing, relay, identity, encrypted storage, or communications infrastructure belongs in the conversation.
Monero
Private contribution flow, wallet-aware UX, and payment architecture that avoids unnecessary personal data collection.
CakeWallet
Mobile wallet ergonomics, recovery flows, and secure-state handoff patterns that feel usable under pressure.
Mullvad
VPN behavior, state-aware network policy, and leakage reduction where technically possible.
No partnership is implied unless formally confirmed. This is a direct invitation to discuss architecture, constraints, and what would make Secure Mode materially stronger.
Discuss Secure Mode on Signal @TheDevilsDev.01Project Progress Update
Initial Concept Proof v1.5
June 21, 2026
First Real-Device Prototype passed A11 testing
The first TridentOS control-layer prototype has passed real-device testing on a Samsung Galaxy A11 running LineageOS. It now installs, opens, switches between the four visible modes, and remembers the selected mode after close/reopen.
Read the full build updateCurrent build status
Honest project state.
Product conceptDefined
Four-state architectureDefined
Website/brandLive
First hardware targetBeing selected
Prototype buildFunding required
Public installerNot yet available
Security auditNot yet completed
DocumentationIn progress / planned
Architecture principles
No fake absolute-security claims.
- State separation
- Least exposure
- Offline-first option
- Privacy-routing where technically possible
- Encrypted local storage goal
- Duress-aware workflows
- Minimal data collection
- Future technical transparency
TridentOS is a separate concept from GrapheneOS. It explores a different multi-state device model and will avoid superiority claims until working builds, tests, and reviews exist.
Founder funding
Founder's Edition — Fund the Build
$500 equivalent in XMR
Founder's Edition exists to fund the development of TridentOS. It is a deliberate build contribution for people who want this operating system to exist, not the sale of a finished public OS.
This is not a lightweight website idea or a weekend ROM. Moving from architecture to a local build, prototype hardware, test devices, signing, tooling, documentation, and failure cycles can absorb serious money quickly. A single local build push alone could consume around $5,000 USD before wider engineering costs are counted.
Supporters can also donate above or beyond the Founder's Edition amount. Every contribution helps buy development time, hardware, build infrastructure, testing, and the first working branch.
Founder support funds development of the first working build, future Founder's Branch access when available, private founder updates, early testing access if/when builds are ready, name or alias recognition if the founder wants it, and no recurring fee for Founder's Branch access.
- No public installable OS is available yet.
- Device support is not final.
- The build timeline depends on funding and engineering progress.
- Donations of any size can support development, but $500 equivalent XMR is the Founder's Edition contribution level.
- Do not contribute unless you understand this is development funding.
Payment verification
Always verify payment instructions directly on this official website. If you need to verify instructions before contributing, contact the founder on Signal.
Never trust screenshots, forwarded messages, or random social posts claiming to change the TridentOS payment address. Always verify against the official website or ask directly via Signal.
Roadmap
Phases, not fake dates.
Founder funding
Publish concept, collect founder support, select first hardware target, and prepare the technical brief.
Prototype
Base OS build research, state-switching proof of concept, offline profile tests, and secure routing experiments.
Founder alpha
Limited founder testing, install documentation, bug reporting, and hardware compatibility notes.
Security review
Threat model publication, external technical feedback, hardening work, and clearer security claims based on evidence.
Wider release
Broader hardware planning, public documentation, installer improvements, and community testing.
Stay private
Contact via Signal
Signal is the correct route for direct contact.
Direct contact
Signal: @TheDevilsDev.01
For contributor conversations, founder enquiries, funding questions, or private discussion.
Contact on SignalFAQ
Straight answers before funding.
Is TridentOS available to install today?
No public finished build is available yet. TridentOS is currently a founder-funded development project.
What is the $500 for?
It funds development of the prototype, alpha build, documentation, testing, and Founder's Branch. It is not a finished-product checkout.
What do Founder's Edition backers receive?
Founder updates, future Founder's Branch access when available, and early testing access if/when suitable builds are ready.
Is TridentOS better than GrapheneOS?
TridentOS is a different concept. It will not claim superiority over mature projects without working builds, testing, and review.
Which phones will it support?
The first hardware target is still being selected. Early support will be limited.
Can a carrier still see my device?
If a phone connects to a mobile network, carrier-level metadata may still exist. TridentOS aims to reduce exposure where technically possible, not make impossible claims.
What is FREE mode?
FREE mode is the planned offline/local-only state for work that should not depend on active radios or network services.
What is the killswitch?
A planned duress workflow that may trigger wipe or decoy behaviour. Exact guarantees depend on implementation, encryption, hardware support, and testing.
Why Monero?
To avoid card processors and reduce unnecessary personal data collection during founder funding.
Are payments refundable?
Monero payments are irreversible. Contributions are not automatically refundable, and users should not contribute unless they understand the development-stage risk.
Legal / security disclaimer
Alpha-stage security project.
TridentOS is an alpha-stage security project seeking founder funding. No operating system can guarantee absolute protection against all adversaries, forensic methods, hardware compromise, user error, legal compulsion, or implementation flaws. Any feature described as planned, intended, designed, or proposed should be treated as a development goal until marked as implemented, tested, and documented.