Fluree DB vs qEndpoint

Fluree DB is a graph database for data that needs queryable history, verifiable transactions, and fine-grained access rules. It stores RDF triples and appends each cryptographically signed transaction to an immutable ledger, preserving a full temporal history. Graph data can be queried alongside full-text and vector search, with time-travel queries available. Attribute-, role-, and relationship-based policies are evaluated at query time down to individual triples. Fluree is built on W3C standards including JSON-LD, RDF, SPARQL, OWL, and SHACL; listed capabilities include SPARQL 1.1, reasoning, RDF-star, and federated queries. Interfaces include FlureeQL and REST, plus MCP server configuration, LangChain, and LlamaIndex options. Official SDKs are listed for JavaScript/TypeScript, Python, and Java. It runs as a static binary without a JVM or external dependencies, with Docker, Homebrew, shell, PowerShell, and source-build options. The Open Source and Fluree AI plans are free. The Business Source License 1.1 applies, and commercial licensing is available by contacting Fluree.

qEndpoint is a free, open-source RDF triple store for self-hosted linked-data workloads. It supports full-text search, GeoSPARQL, and SPARQL 1.1, either as a standalone endpoint or as a dependency. A graphical interface lets users write and run SPARQL queries, while a RESTful HTTP API handles queries. Datasets can be uploaded in RDF4J-supported formats, including RDF/XML, Turtle, N-Triples, N-Quads, JSON-LD, TriG, and TriX. Result formats include JSON, XML, and Binary RDF. Docker images are available for qEndpoint and for a Wikidata-indexed variant supporting wikidata_truthy and wikidata_all datasets. The Docker setup defaults to 6G memory; large datasets are discouraged below 4G, and Wikidata-all requires at least 10G. Installation documentation covers Scoop, Homebrew, and a CLI ZIP release. The project describes Wikibase use and is licensed under GNU GPL v3.