Who took leadership of GrapheneOS after Daniel Micay stepped down?

1. What the record says about Micay’s departure

Daniel Micay founded GrapheneOS in late 2014 and served as the project’s lead developer; his role and authorship are recorded on the project history page ^[2]. In May 2023 Micay publicly posted that he had “stepped down as lead developer of GrapheneOS,” and that he “will be replaced as a GrapheneOS Foundation director,” according to discussion and community posts that cite his announcement ^[1]. Those community references make clear the departure was public and acknowledged within project forums ^[1].

2. What sources explicitly do — and don’t — name

The available documents plainly record Micay’s resignation as lead developer and mention a replacement at the level of the Foundation director role, but none of the supplied sources supply a name of an individual who took over the overall operational leadership of the GrapheneOS project after Micay stepped down ^[1]. GrapheneOS’s own history page documents Micay’s founding role but does not list a successor or current single leader in the excerpts provided ^[2].

3. Community and project governance context

GrapheneOS operates as a small, security‑focused open source project with discussion and governance taking place on project forums and social accounts; relevant forum threads and the project’s social posts surface community questions about management and transitions ^{[3] [4]}. The discussion forum thread requesting clarity about who controls or runs the project shows community interest in transparent governance, but that thread’s content in the provided snapshot does not resolve who assumed direct leadership after Micay ^[3].

4. Why the successor may not be obvious from public traces

Small open source projects sometimes evolve from a single‑maintainer model into a more distributed governance structure, where responsibilities are shared among core contributors or a foundation rather than vested in a named individual; the sources show Micay stepping down and mention replacement at the foundation level, which is consistent with a governance change rather than a single successor appointment ^[1]. The supplied materials do not include a formal announcement naming a replacement lead developer or describing concrete restructuring steps beyond that brief notice ^[1].

5. Additional reporting and product activity since the change

The available sources document ongoing GrapheneOS activity after 2023 — release notes, infrastructure moves, and public messaging about device support and server relocations — indicating the project continued shipping builds and making strategic decisions after Micay’s departure ^{[5] [4] [6]}. Those operational records imply active maintainers or a team carrying on development, but the supplied sources stop short of connecting those actions to a named successor to Micay ^{[5] [4] [6]}.

6. How to confirm who took operational leadership

To verify an individual successor, check primary GrapheneOS channels not included in these snippets: the official announcement thread on the GrapheneOS discussion forum referenced in community posts, the GrapheneOS.org site news or governance pages, and archived versions of the “stepping down” announcement that might list the replacement by name. The sources you provided include the forum pointer and community quotes but do not include a definitive successor name in the excerpts ^{[1] [3]}.

7. Caveats and transparency about source limits

This report relies solely on the set of supplied sources. Those sources confirm Micay’s stepping down and that the role was to be replaced at the foundation level, but they do not name an individual successor or detail a formal leadership handover ^{[2] [1]}. If you want a definitive name, the next step is to fetch the full GrapheneOS announcement thread and official GrapheneOS governance documentation beyond the excerpts provided here ^{[1] [3]}.