DataJunction
Introduction
DataJunction (DJ) is an open source metrics platform that allows users to define metrics and the data models behind them using SQL, serving as a semantic layer on top of a physical data warehouse. By leveraging this metadata, DJ can enable efficient retrieval of metrics data across different dimensions and filters.
Getting Started
To launch the DataJunction UI with a minimal DataJunction backend, start the default docker compose environment.
docker compose up
If you'd like to launch the full suite of services, including open-source implementations of the DataJunction query service and
DataJunction reflection service specifications, use the demo profile.
docker compose --profile demo up
DJUI: http://localhost:3000/ DJ Swagger Docs: http://localhost:8000/docs DJQS Swagger Docs: http://localhost:8001/docs Jaeger UI: http://localhost:16686/search Jupyter Lab: http://localhost:8888
How does this work?
At its core, DJ stores metrics and their upstream abstractions as interconnected nodes. These nodes can represent a variety of elements, such as tables in a data warehouse (source nodes), SQL transformation logic (transform nodes), dimensions logic, metrics logic, and even selections of metrics, dimensions, and filters (cube nodes).
By parsing each node's SQL into an AST and through dimensional links between columns, DJ can infer a graph of dependencies between nodes, which allows it to find the appropriate join paths between nodes to generate queries for metrics.
AI Integration
DataJunction provides an MCP (Model Context Protocol) client that enables AI assistants like Claude to interact with your semantic layer.
The MCP client is part of the DataJunction Python client package.
For installation and setup, see the MCP documentation in the client package.
Documentation
For more detailed documentation, visit datajunction.io.
Release files for datajunction-server 0.0.262
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| datajunction_server-0.0.262.tar.gz | 9.7 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| datajunction_server-0.0.262-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 1.4 MB
Release files / datajunction_server-0.0.262.tar.gz
| Download URL | datajunction_server-0.0.262.tar.gz |
|---|---|
| Size | 9.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
6be8c2b49256365ab280706e2cddebc099c367d0877031773225b0ad461a7a35
|
|
BLAKE2b-256 checksum How to use checksums |
565a4c5e1bf03c11fedf837df3fd9b031167edb7a97a3eb421344bca849da863
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency logRelease files / datajunction_server-0.0.262-py3-none-any.whl
| Download URL | datajunction_server-0.0.262-py3-none-any.whl |
|---|---|
| Size | 1.4 MB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6ada64247e48e03e81eaf4e2123c62ddcfac8fec5098a0bb2b40d0a49ee1cc14
|
|
BLAKE2b-256 checksum How to use checksums |
3f1fa8aa7e127920148d708f100875158e255c9882dd650051377bd00274beee
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 15, 2026.
Transparency log
