NextGraph
Integrated P2P RuntimeDecentralized and local-first web 3.0 ecosystem
Fully P2P Community Low capture risk
Links
Details
License Apache 2.0 / MIT / Permissive
Dev Status Alpha
Owner Niko Bonnieure (European/French software engineer)
Country France
Start Year 2021
Stack Rust
Funding NGI
Last Investigated Mar 10, 2026
Integrated P2P Runtime Attributes
P2P Architecture Byzantine causal broadcast
Overlay Network Store-wide two-tier (pub/sub based)
Content Addressing Yes
Local-First Yes
E2EE Yes
CRDTs Lib Automerge + Yrs/Yjs + RDF Graph CRDT (custom, based on Oxigraph triplestore)
Byzantine Fault Tolerance Yes
Signature BLS Threshold signature
Permissions Cryptographic Capabilities
Semantic Web Compatability RDF
Smart Contract Planned for future
Protocol Stack Position Application-layer (built on TCP/IP)
Asset / Value Embedding None — NextGraph is a local-first, E2EE protocol with no native token or economic layer. The project is funded by NGI Assure and NGI Zero Commons grants (public European research funding); node operation and brokering are not governed by tokenomics.
Development Tools NextGraph SDK/Framework for building decentralized web apps; Rust-based libraries with JavaScript/TypeScript bindings; SPARQL query interface (fork of Oxigraph triplestore); reactive store with JavaScript objects (POJOs) for data access; CRDT integration (Yjs, Automerge); SDK in preview alpha with continuous improvements planned for early 2026; ELFA consortium (EU-funded) building local-first workspace suite on NextGraph
Deployment Options Self-hosted brokers + edge devices + web apps + native apps (Windows, macOS, Linux, Android, iOS); ELFA consortium developing workspace suite (documents, spreadsheets, email, calendar, chat, video calls); backward-compatibility with Web 2.0 planned (gateways, URL-based RDF, server-side rendering, static HTML hosted on domain)
Authentication & Identity DID (Decentralized Identifiers) for users and documents; cryptographic capabilities for access control; DID scheme used instead of HTTP for more decentralized approach and access control; W3C Data Integrity 1.0 proofs and threshold signatures for data verification
Storage Model Local-first with E2EE sync via brokers; RDF/SPARQL graph database with CRDTs (Yjs for structured data, Automerge for structured data, RDF SU-set CRDT for graph data); documents stored locally ensuring availability and privacy; sync occurs automatically when connectivity established, without conflict risk; Oxigraph-based triplestore
Interoperability RDF/Semantic Web compatible (core design principle — linked data with DID URIs); SPARQL queries including 'Social Queries' for federated-style querying of other users' data; ActivityPub integration planned; portable across apps/domains; compatible with Solid; GraphQL support planned; data not tied to specific app, format, domain name or server
Social Graph Yes (decentralized social network features: DM, timeline, sharing; ActivityPub compatible; 'Social Queries' enable SPARQL-based aggregation of data stored by other users in the social network, gathering results locally)
Protocol Maturity / Standardization Community Standard (open protocol specification; CRDTs + semantic web integration; developed by NextGraph project)