About this event
Most databases store records. FlureeDB stores knowledge — and the proof of where it came from. In this hands-on session, we'll go past the pitch and actually build with it.
Starting from a clean install, we'll stand up a FlureeDB ledger, load real data, and query it two ways — SPARQL 1.1 and idiomatic JSON-LD — against the same engine.
From there we'll exercise the features that make a knowledge graph verifiable: an immutable ledger you can query at any past moment, per-triple access control enforced inside the query engine, git-style branch and merge for data, and cryptographically signed commits.
We'll wire up the bundled MCP server so an AI agent can query the graph directly — governed by the same policies — and close on deployment: the same single binary as a CLI, an HTTP server, an embedded Rust library, or fully serverless.
Bring a terminal if you want to follow along.
You'll leave with a working mental model of FlureeDB, the install + quickstart links to reproduce everything, and a clear sense of where it fits next to a triple store, a vector DB, and a stitched-together governance stack.