Skip to main content


One of our two senior developers has been forcibly detained and conscripted to participate in a war. When they first went missing, we revoked their repository access as a precaution. We soon learned their disappearance was completely unrelated to GrapheneOS. Our priority has been keeping them safe.
in reply to GrapheneOS

We've used our available connections to try to keep them safe. There's no way to get them out of the conscription. However, they're an incredibly talented security researcher and engineer and it would be extraordinarily misguided to send them to front line combat. This seems to be understood now.
in reply to GrapheneOS

GrapheneOS development and updates have continued and will keep going. We have substantial funds available to hire more people to work on GrapheneOS. We'll need to hire multiple experienced developers to fill their big shoes. They'll hopefully be safe and when they return we'll have a bigger team.
in reply to GrapheneOS

If you're an experienced AOSP developer interested in working full time on GrapheneOS in a fully remote position, see grapheneos.org/hiring. We can pay people anywhere in the world via Wise (local bank transfers), BTC, ETH or XMR. We need people who can hit the ground running due to the current situation.
in reply to GrapheneOS

Our near term focus is going to heavily shift to Android 16 porting, maintenance and continuing to do better patching than standard Android 15 QPR2. An OEM providing us early access to Android 16 sources would help a lot and we wouldn't need to slow down new feature development nearly as much.
in reply to ocean

@oceanhaiyang GrapheneOS is entirely by donations:

grapheneos.org/donate

Some of the donations are very large but even some of those were done anonymously. We know who several of the large donors are including ongoing support from Vitalik Buterin as an example.

in reply to GrapheneOS

@oceanhaiyang

Do you have or plan to have any transparency report? I am not talking about personal data on the developers but something more akin to like breakdown of the incomes.

Like: "for this quarter we received this total, this amount was used to pay developers, this amount was used to pay infraestructure, this amount was used to buy devices, this amount was saved to safeguard against unexpected events,..." and so on.