Hardened foundation
Built on GrapheneOS and AOSP security engineering rather than relying only on application level privacy settings.
SECURITY & TRUST
Security should be inspectable.
Obris SecureOS is built around explicit security boundaries, signed releases and controls that can be independently checked.
Mobile security is a system of hardware, operating system integrity, authentication, compartmentalisation, networking and user behaviour. No single feature makes a device secure.
DEFENCE IN DEPTH
No single feature is the security model.
Obris SecureOS combines a hardened Android foundation, operational separation, physical activation controls and verified software delivery. Each layer protects a different boundary.
Operational separation
The Security User keeps sensitive applications, accounts, sessions and credential protected data separate from everyday Owner use.
Physical activation
An enrolled FIDO2 YubiKey forms part of the protected Security User workflow instead of relying only on another remembered secret.
Verified software
Signed release metadata and images are verified before installation, and the supported device returns to a locked bootloader state.
SECURITY USER CONTROLS
A separate environment with separate operational rules.
The Security User is intended for sensitive work that should not inherit every capability of the everyday Owner environment.
YubiKey controlled activation
The enrolled physical key is required through the supported workflow to activate the protected Security User.
Communication restrictions
Cellular SMS and outgoing cellular calls are restricted so sensitive communications can remain inside approved encrypted applications.
Duress controls
The duress workflow removes the protected Security User and returns to the ordinary Owner environment without requiring a reboot.
Obris CHAT
Separate content encryption from network path protection.
Obris Chat protects message, voice and video content independently of the VPN transport layer, while the production service is designed to operate through the Obris VPN path.
End to end messaging
Message content is end to end encrypted independently of the VPN tunnel.
Encrypted voice and video
Calls use encrypted WebRTC media between the communicating endpoints.
TURN relay architecture
Call media is designed around relay candidates rather than intentionally exposing a direct peer to peer media path.
Obris VPN required
If the required VPN path is unavailable, communications are designed to stop rather than intentionally fall back to direct internet access.
RELEASE TRUST CHAIN
The download server is not the root of trust.
Release authenticity is anchored in cryptographic verification. A compromised download location should not by itself create a valid Obris release.
01
SecureOS build
Controlled build and release process.
02
Release validation
Release metadata and expected images are validated.
03
Signing identity
Private signing authority remains under controlled Obris custody.
04
Browser verification
The installer verifies release material before flashing.
05
Locked device
The supported device returns to a locked bootloader state.
RESPONSIBLE CLAIMS
What Obris does and does not claim.
Security claims are useful only when their limits are stated clearly.
Reducing exposure and increasing control.
- Strong separation between ordinary and sensitive environments
- Signed release verification and a locked device state
- Reduced exposure of sensitive data during everyday use
- Physical security controls where appropriate
- Clear installation and release trust boundaries
An unhackable or universally anonymous phone.
- Protection from every vulnerability or physical attack
- Anonymity against every adversary or operational mistake
- Security when credentials or security hardware are intentionally disclosed
- That one feature replaces disciplined mobile OPSEC
- That secrecy of implementation is itself a security control
Security review status
Security critical SecureOS modifications are intended to be inspectable. Independent security review and a formal vulnerability disclosure programme remain roadmap items and are not represented as completed.
Open where trust matters. Protected where security requires it.
See exactly which parts of the Obris platform are intended to be public, which operational systems remain proprietary, and why real secrets never belong in either repository.