Fluree

P2P Platform

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 .

Empresa
Links
Visitar Comunidade

Detalhes

Licença AGPL (open source core, released Oct 2020) ; https://github.com/fluree/db
Status de Dev 🟢 Ativo
Detalhe do Status de Dev Production
Proprietário Fluree PBC (Brian Platz, CEO & Co-Founder; Andrew 'Flip' Filipowski, Co-CEO & Co-Founder)
País USA (Winston-Salem, North Carolina)
Ano de Início 2016
Stack Clojure/ClojureScript (core), Java runtime, JavaScript/Node.js/React client libraries
Financiamento VC-funded: $4.7M Seed (2019, led by 4490 Ventures), $10M Series A (April 2023, led by SineWave Ventures), plus additional rounds
Última Investigação 9 de mar. de 2026

Domínios de Caso de Uso

Co-Creation & Knowledge Platform Evolution & Sovereignty

Capacidades

Interoperable formats Provenance tracking Version history

P2P Platform Atributos

Origins Founded by Brian Platz and Flip Filipowski as a Public Benefit Corporation to pioneer data-first technology with blockchain-secured semantic graph databases
Database Native RDF triple store with blockchain-secured immutable ledger; AVL-tree indexes; optional Lucene full-text index
Query Language FlureeQL (native JSON), SPARQL, GraphQL, SQL (limited)
Data Formats JSON-LD, RDF (Subject-Predicate-Object triples), Turtle
Collaborative Live Editing No
Rich Text Editing No
Mobile Support No (server-side database)
Web Support Yes (REST API, JavaScript SDK, React libraries)
Native Apps No
Terms AGPL (open source core); Commercial/Enterprise license available
Funds $28.1M total raised (8 rounds, 14 investors; latest $3.77M Series A-III, Feb 2025)
Based On RDF/W3C Semantic Web standards; blockchain/ledger technology for immutability
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)