Seed a graph
Paste CREATE statements, import a snapshot, or start from a saved query. The graph lives only in your browser.
Live · Public preview
LoraDB queries in your browser. Graph results included.
The LoraDB playground is a browser IDE for exploring connected data with the same Rust engine that powers the crate and bindings. Write a query, inspect the graph, review analysis, and share the exact query by URL.
0servers to start
4result views
1shared engine
play.loradb.com
How it feels
A short path from idea to graph.
Run and inspect
Use the graph canvas for shape, the table for summaries, JSON for exact tagged values, and Plan for parser/analyzer detail.
Share or export
Send a query URL when the data already exists, or pair the URL with a snapshot when someone needs the same graph.
Workbench
Built for the questions that tables make awkward.
LoraDB query editor
Monaco editing with LoraDB-aware highlighting, completion, diagnostics, formatting, and multiple query tabs.
Graph-first results
Switch between graph, table, JSON, and plan views without rerunning the query. Select a node or relationship to inspect its exact payload.
Local persistence
History, saved queries, snapshots, schema state, and preferences stay in browser storage for the playground origin.
Shareable query links
Encode the active query into a URL for documentation, issues, pull requests, and debugging conversations.
Snapshot bridge
Export a playground graph and load it from the Node, Python, Rust, WASM, Go, Ruby, or server surfaces that use the same snapshot codec.
Query analysis
Use the Plan tab for diagnostics, variables, labels, relationship types, and parameters while you edit.
What runs where
Static site, local engine, no backend queue.
The playground is exported as static assets. The LoraDB engine runs in a Web Worker, the graph stays in your browser, and snapshots are the portable handoff when you want to move the same data into application code.
EngineThe Rust parser, analyzer, planner, executor, and store compiled to WASM.
StorageOrigin-local IndexedDB and localStorage; no account and no shared backend.
SnapshotsExport and import the same snapshot format used by application bindings.
DocsExamples can link straight into a runnable browser workspace.
Honest preview boundaries
The playground is for learning, prototyping, reproducing, and sharing query shape. Production state still belongs in an app binding or the HTTP server.
- One browser-origin database per visitor.
- No hosted workspace, sync, or team database.
- No host-side parameter drawer yet.
- No browser WAL or filesystem paths.
Keep exploring
Docs that pair well with an open playground tab.
Open a graph database without opening a terminal.
Start in the browser, then carry the query or snapshot into the binding you ship. Same query engine, same planner, same result shapes.