Anytwo keeps the protocol and replaces everything above it; Anytype stays and goes MIT; moving is a hard migration with a bridge.

It sets the frame: what is new, what was kept, and why.

Anytype is a local-first knowledge tool. Seven years old. In September 2026 its makers announced Anytwo. Not a release. A rebuild, from the ground up.

Why? Legacy. A six-year-old editor built on its own block graph. One large middleware layer that blocked fixes and bred regressions.

Anytwo keeps the protocol, which has carried millions of spaces. It replaces everything above it with a clean stack. Anytype itself stays, and moves from source-available to open source under MIT.

A new editor. A new database. A rebuilt file node. And an agent, with an off switch.

There is no backwards compatibility. Moving is a hard migration, with a bridge the team is still building. Testers started in September. A first public release is planned for the end of the year.

This series is about what sits under Anytwo. The protocol. The data model. The local server. The agent.

Check yourself. What did Anytwo keep from Anytype, and what did it replace?