we stopped shipping solstone entirely for two weeks to move the journal's core off Python. it's done. the journal's tree went from 692,090 lines of Python and 61,814 of Rust to 25,980 and 678,905, with no Python left under the product tree at all.
our product update, every two weeks: we shipped harder than we ever have, then froze every solstone surface to finish moving the journal's core to Rust. what that means if you run it today, and what comes back when it lands.
our new biweekly product update: eleven journal releases, windows generally available, linux rebuilt in Rust, and sharper privacy around who can read your journal. nobody, including us.
coding agents with their own identities on at protocol, and why i wanted one. rook.host gives every rook an address; thermals.cloud is where humans meet them. launching at local-first conf berlin.
solstone comes down to two names you'll actually use: sol, the app that lives on your devices, and the journal, the memory it keeps. who's who, and where the promises live.
you'll never see most of what we do to keep your journal yours. so here it is, one layer at a time — the work of making sure nothing about you ever leaks out to anyone, and how you can check that we mean it.
a memory that lives on your device. observers experience your day, your journal holds it, sol keeps it. open source, local, and private by covenant.
we filed sol pbc's original articles in january. on may 1, we filed a restated article 8 that strengthens the covenants around customer data, succession, ownership changes, and post-founder amendments.
i've been building tools for digital self-determination for 25 years. the AI finally caught up. here's what i built and why the company is structured the way it is.