Fluree

P2P Platforms/Frameworks

Enterprise semantic graph database with blockchain-secured immutable ledger, W3C standards compliance (JSON-LD, RDF, SPARQL), and decentralized data composition capabilities . Note: Primarily a client-server database product with decentralized features, not a traditional P2P architecture. Classified as P2P Platform for tracking purposes within the CTA/OpenHaven context, but architecturally functions as an enterprise graph database akin to Neo4j or ArangoDB .

Híbrido Empresa Risco de captura médio
Links
Visitar Comunidade

Detalhes

Licença AGPL
Status de Dev Released
Proprietário Fluree PBC (Brian Platz, CEO & Co-Founder; Andrew 'Flip' Filipowski, Co-CEO & Co-Founder)
País USA
Ano de Início 2016
Stack Clojure/ClojureScript, Java runtime, JavaScript/Node.js/React client libraries
Financiamento VC
Última Investigação 10 de mar. de 2026

Domínios de Caso de Uso

Co-Creation & Knowledge Platform Evolution & Sovereignty

Affordances

Interoperable formats Provenance tracking Version history

P2P Platform Atributos

P2P Architecture Multi-node consensus (optional RAFT or PBFT); not P2P in traditional sense — nodes are server instances operated by administrators; decentralized federated query across distributed databases
Development Tools JavaScript/Node.js/React SDKs and libraries; Fluree CLI; REST API; Docker images; SPARQL and GraphQL endpoints auto-generated from schema
Deployment Options Single-node local (laptop), multi-node on-premise, cloud-native (any cloud), Docker/container, Fluree Cloud (hosted SaaS)
Authentication & Identity Data-centric security via SmartFunctions; SHA-256 asymmetric cryptography for ledger integrity; W3C Verifiable Credentials and DID registry support; zero-trust architecture
Storage Model Disk-oriented storage at ledger tier; in-memory indexes replicable to client via service worker for edge query; immutable append-only ledger with temporal metadata (time-travel queries)
Interoperability Native W3C compliance: JSON-LD, RDF, SPARQL, OWL/RDFS; federated query across disparate interoperable sources; data is FAIR (Findable, Accessible, Interoperable, Reusable); GraphQL API auto-exposed
Social Graph No native social graph (enterprise database; can model social relationships via RDF graph but no built-in social features)