ontobricks
Transforms Unity Catalog tables into a dynamic, understandable knowledge graph, with ontology design and reasoning exposed to AI agents as MCP tools
Safety scan
A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.
Check it deeper on your machine
It has changed since its scan on 19 Nov 2026.
As a Claude Code plugin, install it and then ask Claude Code:
/plugin marketplace add keithmackay/mackayi/plugin install scanskillsafety@mackayiDo a deep scan of https://github.com/databrickslabs/ontobricks with scanskillsafety
Or from a terminal, clone it and run it:
git clone https://github.com/keithmackay/scanskillsafety-skill ~/.claude/skills/scanskillsafetynode ~/.claude/skills/scanskillsafety/cli.cjs --deep 'https://github.com/databrickslabs/ontobricks'
It checks the exact commit: every file, its packages against OSV (api.osv.dev), how it compares with this page's scan (findsafeskills.com receives the repository's address), and, if you agree, Claude reading every file with your own Claude subscription. It never runs the code.
Badge for your README
Markdown
[](/listings/databrickslabs--ontobricks)HTML
<a href="/listings/databrickslabs--ontobricks"><img src="/api/listings/databrickslabs--ontobricks/badge.svg" alt="findsafeskills safety rating" /></a>Install
What was scanned
The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.
README.md · README · 262 lines
- <p align="center">
- <img src="src/front/static/global/img/ontobricks-icon.svg" alt="OntoBricks Logo" width="120" height="120">
- </p>
- <h1 align="center">OntoBricks 0.9.2</h1>
- <p align="center">
- <strong>Turn your Databricks tables into a living knowledge graph — in four clicks.</strong>
- </p>
- <p align="center">
- <a href="https://ontobricks.org/">Website</a>
- ·
- <a href="https://ontobricks.org/">Demos & Screenshots</a>
- ·
- <a href="https://github.com/databrickslabs/ontobricks">GitHub</a>
- ·
- <a href="docs/README.md">Documentation</a>
- </p>
- <p align="center">
- <img src="https://img.shields.io/badge/runs%20on-Databricks%20Apps-FF3621.svg" alt="Databricks Apps">
- <img src="https://img.shields.io/badge/python-3.11+-blue.svg" alt="Python">
- <img src="https://img.shields.io/badge/standards-OWL%20·%20R2RML%20·%20SPARQL-6E4AFF.svg" alt="Standards">
- <img src="https://img.shields.io/badge/AI-MCP%20ready-10B981.svg" alt="MCP ready">
- </p>
- ---
- ### What's new in 0.9.2
- - **Several datasets per class**: Ontology Studio links multiple Unity Catalog tables, views, or **metric views** to one class. Graph Explorer, Graph Chat, and MCP surface all of them.
- - **MCP identity and domain resolution**: graph tools run as the end user again, and domain-scoped tools work without a sticky session (`domain_name`).
- - **SPARQL value filters**: typed `FILTER(STR(?v) = …)` and `CONTAINS(…)` compile to SQL instead of returning unfiltered results.
- - **Apps deploy and local setup fixes**: identity scopes are no longer declared, and `./scripts/start.sh` works when the default `python3` is 3.9.
- - **Dependency security floors** raised (Authlib, dnspython, msgpack, nltk, pyasn1, graphql-core, joserfc); the MCP server now requires Python ≥ 3.11.
- Full details are in the [Release Notes](releases/ReleaseNotes_V0.9.2.md).
- ### What's new in 0.9.1
- - **Viewer search and Graph Chat**: Viewers can search / expand Explorer and chat over the graph; load and node-action writes stay blocked.
- - **SWRL builtins**: `swrlb:` filters apply on inference **and** materialization (Lakebase `TRY_CAST` included).
- - **Auto-Map Metric Views**: the agent emits `MEASURE(...)` + `GROUP BY` and rejects table-style `SELECT *`.
- - **Faster Data Quality**: bulk checks snapshot the gateway VIEW once, run in parallel, and stream a live activity log (entity checks too).
- - **Lakebase quality SQL** always uses the Build warehouse, not a Lakehouse//RT query warehouse.
- - **Security floors** raised (Pillow, certifi, GitPython, MLflow, …); `uv.lock` regeneration is still required.
- Full details are in the [Release Notes](releases/ReleaseNotes_V0.9.1.md).
- ### What's new in 0.9.0
- - **Lakehouse//RT graph queries**: Knowledge Graph reads can run on a serverless Lakehouse//RT warehouse, while builds keep a classic or serverless one.
- - **Three-stage Ontology Generate**: detect entities, lock the catalog, then complete relations, attributes and axioms. The result is appended to your ontology instead of replacing it.
- - **Knowledge Store**: parsed documents live in Lakebase and are shared by Generate and Mapping. No Volume grants are needed.
- - **Unity Catalog Metric Views**: Metric Views import as data assets with dimension/measure roles.
- - **Entity Data Quality Checks**: right-click a node in Explorer, or call it from MCP, to check that entity against every SHACL shape that applies, with gauges for each dimension.
- - **Entity business rules**: attach SWRL rules, aggregate rules and decision tables to a class, then run them on one entity from Explorer or MCP.
- - **Databricks Jobs as class actions**: trigger a workspace Job for an entity next to Unity Catalog functions.
- - **SPARQL playground**: query the graph in SPARQL and inspect the generated SQL.
- - **GitHub domain mirror**: push the domain configuration (OWL, R2RML, SHACL, rules) to a GitHub repository and restore it from there.
- - **OBX Import as**: rename a domain on import; a renamed copy does not reuse the previous graph objects.
- - **Faster Explorer**: indexed search, paged expansion and no blocking `COUNT(*)` on first load.
- - **Ontology Studio**: the renamed Designer adds multi-select, Business Views, cross-domain import, and OWL/R2RML export from the canvas.
- - **Load opens Domain → General**: opening a domain from Home, the navbar, Registry, or Versions lands on Domain → General instead of staying on the current page.
- - **Security hardening**: stricter CSRF, a `/health` that leaks no internals, dialect-aware SQL escaping and sanitised Markdown.
- Full details are in the [Release Notes](releases/ReleaseNotes_V0.9.0.md).
- ---
- Every enterprise has the data. Almost none have the **meaning**. Your Lakehouse
- stores billions of rows, but nothing captures what they *represent* — that a
- *Customer* holds *Contracts*, which contain *Invoices*, governed by rules only
- your senior engineers remember.
- **OntoBricks closes that gap.** It is a Databricks-native app that turns Unity
- Catalog tables into an explorable, queryable **knowledge graph** — design the
- meaning, let AI map it to your data, and navigate the result visually or expose
- it to your favorite LLM. No separate graph platform, no RDF expertise, no
- months-long integration project.
- ## Why OntoBricks
- - **From schema to graph in minutes, not months.** LLM-powered automation drives
- the whole pipeline — import metadata, generate the ontology, map the data,
- materialize the graph.
- - **Lives inside Databricks.** Deploys as a Databricks App and reuses what you
- already have: Unity Catalog, SQL Warehouse, AI Gateway or Model Serving,
- and Lakebase. Your
- triples stay in your Lakehouse.
- - **Standards under the hood, simplicity on top.** OWL, R2RML and SPARQL power
- the engine; everything executes as Spark SQL. Your users never touch RDF.
- - **Built for the AI era.** Publish any domain to LLM agents over the Model
- Context Protocol (MCP) and let them reason over governed, explainable
- business semantics.
- - **Governed by design.** Versioned domains, DRAFT → IN-REVIEW → PUBLISHED
- lifecycle, single-editor locking, and an append-only review audit trail.
- - **Parse documents once, reuse them everywhere.** Uploaded PDF, Office, image,
- and text sources are parsed into a versioned **Knowledge Store** (parsed text
- in Lakebase; originals are not retained) shared by ontology Generate and
- Mapping; failed parses are visible and retryable.
- ## From tables to a knowledge graph in four clicks
- | Step | Action | What happens | Powered by |
- |------|--------|--------------|------------|
- | **1** | **Import Metadata** — Domain > Metadata | Fetches table & column metadata from Unity Catalog | Unity Catalog |
- | **2** | **Generate Ontology** — Ontology > Wizard | The LLM designs entities, relationships & attributes from your metadata | AI Gateway / Model Serving |
- | **3** | **Auto-Map** — Mapping > Auto-Map | The LLM generates SQL mappings for every entity and relationship | AI Gateway / Model Serving |
- | **4** | **Synchronize** — Knowledge Graph > Status | Executes the mappings and populates the triple store | SQL Warehouse |
- Prefer full control? Every step is also available as a guided **manual
- workflow** — design, map, build, query, and reason at column-level precision.
- See the [User Guide](docs/user-guide.md).
- ### Run a domain without an LLM
- Selecting **No LLM** is a strict domain-level opt-out. LLM actions remain
- visible but unavailable and direct API calls are rejected with guidance to
- select a model in **Domain Information → AI**. Select and save an LLM there to
- make those actions available again without reloading the page. Deterministic
- reasoning and validation, including OWL/SWRL inference, ontology pitfalls, and
- SHACL data-quality checks, remain available while No LLM is selected.
- ## What's inside
- ### Design ontologies visually or with AI
- Drag-and-drop entities, relationships and inheritance on the **OntoViz** canvas,
- or import industry standards in one click (FIBO, CDISC, IOF, HL7 FHIR
- R4/R4B/R5) and your own OWL/RDFS. A floating **AI Assistant** edits your
- ontology through natural language. Catch design issues early with the built-in
- **Ontology Pitfalls Detector** (19 structural, logical and semantic checks).
- **Generate** drives that AI design through a resumable, human-in-the-loop
- wizard — **Detect** candidate entities from metadata and your parsed document
- corpus, **Review** them (include/exclude, edit labels, add your own), then
- **Complete** relations, attributes, and axioms in that order. Every run
- **appends** to your existing ontology — locked entities are never renamed or
- removed — and a stale draft (source changed since detection) is flagged with
- a one-click **Re-detect** instead of silently reusing outdated candidates.
- ### Map to your data — automatically
- Let the LLM generate SQL and column mappings for every entity and relationship,
- then refine with live data preview. Mappings compile to W3C-compliant **R2RML**
- you never have to write. Schema-drift warnings flag upstream renames and drops
- before they break your graph.
- ### Build, reason and explore
- Materialize triples incrementally, then **reason** over the graph with OWL 2 RL
- inference, SWRL rules and SHACL validation. Explore interactively: two-phase
- search, N-hop neighbour expansion, cross-domain bridge navigation, community
- detection (Louvain, Label Propagation, Greedy Modularity), and explainable
- **cohort discovery**. Lakehouse domains can optionally read from a **Lakehouse//RT**
- query warehouse while builds stay on a classic or serverless warehouse. Query
- everything through an auto-generated **GraphQL** API or open **Knowledge Graph
- → Query → SPARQL** for read-only SELECT queries, sample queries, CSV export,
- generated SQL inspection, and triple-shaped results that open in Explorer.
- See the [SPARQL Playground guide](docs/user-guide.md#sparql-playground),
- [Get Started](docs/getting-started.md), and
- [Cohort Discovery](docs/advanced_features.md#cohort-discovery).
- ### Publish to AI agents (MCP)
- Expose your knowledge graph to Cursor, Claude Desktop or the Databricks
- Playground over the [Model Context Protocol](https://modelcontextprotocol.io/).
- Each domain decides exactly **what it publishes** — which tools, which datasets,
- which class actions and virtual attributes — right down to ontology-only domains
- that expose a single `describe_ontology` tool. See
- [MCP Integration](docs/mcp.md).
- ### Govern the whole lifecycle
- Every domain version carries a **DRAFT / IN-REVIEW / PUBLISHED** status enforced
- server-side. A **single editor** holds a DRAFT at a time (auto-releasing leases,
- admin take-over), a business-friendly **review workflow** collects sign-offs
- with a configurable quorum, and every decision is persisted append-only. Move
- domains between environments with the **OBX** export/import (UI or
- [CLI](docs/advanced_features.md#registry-import-and-export)).
- ### Pluggable graph engine
- Pick a backend **per domain**: **Lakebase (Postgres)** by default,
- **Lakehouse** (governed Delta triple tables, zero extra infra), **Neo4j**, or
- **No Backend** for ontology-only domains that publish their ontology with no
- graph built (Mapping and Knowledge Graph are disabled and the MCP surface
- serves only ontology information).
- Connection config stays workspace-global. Lakehouse and Lakebase Build also
- materialise Explorer indexes (`_adj_out` / `_adj_in`, `_entity_search`,
- `_entity_search_asserted`, `_props`); Neo4j keeps native traversal. Full reference:
- [Lakebase Graph DB](docs/backend.md#lakebase-graph-store) ·
- [Graph DB Integration](docs/backend.md#engine-integration) ·
- [Graph Query Optimizations](docs/backend.md#graph-query-optimizations).
- ## Runs entirely on your Databricks
- OntoBricks is not a separate platform. It deploys as a **Databricks App** and
- uses the services you already run — Unity Catalog for storage and metadata, a
- SQL Warehouse for execution, AI Gateway or Model Serving for LLM automation, and
- Lakebase for the registry and graph store. Your data and your triples never leave your
- workspace. Architecture deep-dive: [architecture.md](docs/architecture.md).
- ## Get started
- **Try it locally**
- ```bash
- git clone <repository-url> && cd OntoBricks
- uv sync --frozen --extra lakebase # install the committed public-PyPI lock
- cp .env.example .env # set your Databricks host, token, warehouse ID
- scripts/start.sh # open http://localhost:8000
- ```
- Always use `--frozen` for routine `uv sync` / `uv run` commands. The lock
- records package indexes as `https://pypi.org/simple` and immutable artifact
- downloads on `https://files.pythonhosted.org`; do not commit internal
- `pypi-proxy.dev.databricks.com` URLs.
- **Deploy to Databricks Apps**
- ```bash
- databricks auth login --host https://<workspace>
- # edit scripts/deploy.config.sh (profile, warehouse, registry, Lakebase), then:
- make deploy
- ```
- Prerequisites (Databricks workspace with Apps enabled, a SQL Warehouse, a
- **Lakebase Autoscaling** database, and a Unity Catalog Volume) and the full,
- idempotent deploy checklist — including one-click graph-DB provisioning and
- permission bootstrap — are in the
- **[Get Started](docs/getting-started.md)** and
- **[Deployment Guide](docs/deployment.md)**.
- The bundle syncs only runtime source, the MCP and graph-job files, dependency
- locks, and the in-app Help Center set. `databricks.yml` `sync.exclude` is
- authoritative; `.databricksignore` is a reviewer/test mirror and is not read
- by the Databricks CLI.
- ## Documentation
- - **[Documentation hub](docs/README.md)** — start here
- - **[Value proposition](docs/product.md)** — the business case & go-to-market
- - **[User Guide](docs/user-guide.md)** · **[Feature inventory](docs/user-guide.md#feature-inventory)** · **[Architecture](docs/architecture.md)** · **[API](docs/api.md)**
- - **[MCP](docs/mcp.md)** · **[Graph DB](docs/backend.md)** · **[Import / Export](docs/advanced_features.md#registry-import-and-export)**
- - **[Developing OntoBricks](docs/development.md)** — build, test, contribute
- Product overview, screenshots and videos:
- [ontobricks.org](https://ontobricks.org/).
- ## License
- OntoBricks, including OntoViz, is source-available under the
- [Databricks License](LICENSE.txt).
- ## Project Support
- Please note that all projects in the /databrickslabs github account are provided
- for your exploration only, and are not formally supported by Databricks with
- Service Level Agreements (SLAs). They are provided AS-IS and we do not make any
- guarantees of any kind. Please do not submit a support ticket relating to any
- issues arising from the use of these projects.
- Any issues discovered through the use of this project should be filed as GitHub
- Issues on the Repo. They will be reviewed as time permits, but there are no
- formal SLAs for support.
Ratings and comments
Sign in to rate this skill.
Sign inFree to use. If it’s helped, pass it on.