Knitweb in practice
Real-world cases where peer-to-peer, local-first knowledge graphs and version control make the difference.
Decentralised chemistry education
A classroom of students builds a shared chemistry knowledge graph without relying on a central server. Each device keeps its own copy; concepts and relationships sync peer-to-peer during class.
molgang education offline-firstRemote teams with poor connectivity
Developers in areas with intermittent internet use Gither to commit, review and merge code offline. When connectivity returns, changes sync directly between peers—no lost work, no platform lock-in.
gither devops resilienceAI-agent provenance
AI-generated code changes are signed and stored in a verifiable P2P history. Teams can trace which agent proposed a change, who reviewed it, and when it entered the canonical graph.
agents verifiability complianceCensorship-resistant open source
Open-source collectives mirror their repositories across many peers. If one seed goes down or is blocked, the project remains available and forkable by anyone in the network.
sovereignty open source resilienceCompliance-heavy research
Research labs keep sensitive datasets and analysis code on local-first infrastructure. Signed artifacts and audit logs satisfy regulatory requirements without surrendering data custody.
enterprise compliance local-firstCommunity knowledge networks
Local communities curate multilingual knowledge graphs—chemistry terms, biodiversity, languages—that sync across villages and cities without depending on a single cloud provider.
knowledge graph multilingual communityExperience P2P in your browser
Open the P2P demo and connect directly with another visitor—no server in between.
Try the P2P demo