FlureeDB is a temporal, verifiable graph database designed for data that matters, offering complete history, integrated search, and fine-grained access control within a single binary. It targets developers and power users needing a robust, standards-compliant data store capable of handling billions of triples on commodity hardware with high import and query performance, eliminating external dependencies.

How It Works

Fluree stores data as RDF triples, preserving every transaction immutably. This enables "time travel" querying to any historical state via transaction number, ISO timestamp, or commit ID, without complex dimensional modeling. It uniquely integrates BM25 full-text search and HNSW vector similarity directly into its query engine, allowing these search capabilities to participate in standard graph queries and joins. Access control is granular, enforced at the triple level through policies defined as data, and data management mirrors Git workflows with branching, rebasing, and merging.

Quick Start & Requirements

Installation is available via Homebrew (brew install fluree), Cargo (cargo install fluree), or Docker (docker run -p 8090:8090 fluree/server:latest). The core binary has no external dependencies. A quick start involves fluree init, fluree create <ledger-name>, fluree insert <data>, and fluree query. Full documentation is available in the docs/ directory.

Highlighted Details

• Time Travel: Query data as it existed at any historical point.
• Integrated Search: Built-in BM25 full-text and HNSW vector search.
• Git-like Data Management: Branch, rebase, and merge datasets.
• Triple-Level Access Control: Policies enforced at the fact level.
• Standards-First: Full SPARQL 1.1 compliance and native JSON-LD.
• Verifiability: Supports JWS-signed transactions and Verifiable Credentials.

Maintenance & Community

No specific details regarding maintainers, community channels (e.g., Discord, Slack), or roadmap were provided in the README excerpt.

Licensing & Compatibility

The project is licensed under the Business Source License 1.1, with a specified change date to Apache License 2.0. Users should review BSL 1.1 terms for potential restrictions on commercial use or modifications prior to the conversion date.

Limitations & Caveats

The provided README does not detail specific limitations, alpha status, or known bugs. The Business Source License 1.1 may impose usage restrictions until its conversion to Apache 2.0.