ObliviOS

Home / Status

Status

Where ObliviOS stands, and what is still open.

ObliviOS is source only. There are no images, no update service and no supported device.

262 decisions are on record: 176 accepted, 60 proposed, 26 superseded, dropped or closed. The bill of materials lists 1,238 components and the SHA-256 of 1,553 files. All of this is as of 18 November 2026.

Decision 171 defines this stage: source, records and a bill of materials, with no image, no update and no supported device.

What exists
Four repositories with the manifest, the platform patches, the services and the records.
Supported devices
None. A device counts as supported only after it passes the entry gate of the device support policy.
Phones that run it
The Pixel 10a (stallion), my daily phone, and the Pixel 7a (lynx), my development phone. This says which phones I use, not that they are supported: see Devices.
Images
None yet. If real interest in ObliviOS shows, I want to publish images for the Pixel 10a. I have set no date and I promise nothing: the gates below come first.
Upstream baseline
GrapheneOS manifest 2026100600

The nine parts and where they stand

The decision log gives every decision a status. Accepted means the decision is made. Proposed means it is written, often built, and not accepted yet. The bars count the decisions behind each part.

AcceptedProposedThe rest are superseded, dropped or closed.

Compartments 4 accepted · 8 proposed · 12 decisions
Network exit 1 accepted · 5 proposed · 6 decisions
Atlas 7 accepted · 1 proposed · 8 decisions
Duress Unlock 26 accepted · 12 proposed · 40 decisions
Passwords 4 accepted · 2 proposed · 6 decisions
Grab detection 3 accepted · 3 proposed · 6 decisions
App drawer 2 accepted · 2 proposed · 4 decisions
Keyboard 3 accepted · 1 proposed · 4 decisions
AirPods 13 accepted · 10 proposed · 23 decisions

The road to a public beta

A public beta with binaries has to pass five gates. None is met, and none has to be at this stage, because it offers no binaries. Images for the Pixel 10a would be that beta, so they wait for these gates.

Derivative identity

Do branding, naming and attribution clearly show that ObliviOS is a distinct product?

Source and notices

Does the release inventory meet every source, notice and attribution duty?

Worldwide distribution

Which distribution, privacy, export, cryptography and telecom rules apply?

Proprietary inputs

May every Pixel, vendor and third-party binary be distributed?

Public operations

Are support, disclosure, update and recovery processes live and accurately described?

What has not been reviewed

The legal review of this stage was done by an AI agent, not by qualified counsel. I build ObliviOS alone and without a budget, so counsel was not available. I accepted each risk myself, item by item, in the licensing and branding review. Nothing there is a legal opinion.