You can still use a graph offline. https://iris.to/note1tlzzsszhk5xaghfdeuvlewajrz0hvxnsgdtln7uv7jff6zhtpdxqt4ndzx

What if apps did not depend on a centralized backend? I am working on 2WAY, a local-first, peer-to-peer, open-source (MIT) application protocol and backend, designed to run on practically any device. The goal is to move core infrastructure concerns out of individual apps and into a shared system layer that enforces permissions, stores state as a cryptographically secured graph in a relational database, and synchronizes that state directly between peers. Apps focus on their data model and domain logic. The protocol handles persistence, ordering, synchronization, and trust between peers. This allows apps to work offline by default, survive node loss, and keep functioning without central servers or long-lived operators. This enables classes of apps that are difficult or impossible to build on centralized systems. Apps where users keep control of their data instead of handing it to a provider. Apps that rely on cryptographic proofs as the source of truth rather than trusted networks or intermediaries. Apps that keep working through network splits. Apps that can interoperate without shared infrastructure or federation. Apps that do not break when a service shuts down, changes terms one-sided, or disappears. The system is designed to fail locally and predictably under stress or abuse, with built-in resistance to Sybil attacks and denial-of-service. This repository is a work in progress. I am currently focused on the protocol and architecture, which are about 95 percent complete, unless someone points out a fundamental flaw. The rest of the repository already defines the full system surface, including data, interfaces, security, flows, and more. The structure is in place, but these sections still need to be written and fleshed out. Any questions, comments, or suggestions are welcome and appreciated. Design repository with specs: https://github.com/livegnik/2way-poc-design