Murakumo
Model-first data engineering. Design the logical model (entities, relationships, mappings) on a canvas, and Murakumo generates and maintains everything downstream: DDL, dbt projects, Spark and Python jobs, streaming configs, tests, audit tables, data contracts and orchestration, on an open lakehouse.
Alpha. Working today: the model, importers, validation, the canvas, dbt and DDL generation, migrations, and builds verified on DuckDB and Snowflake. Source: github.com/murakumo-data/murakumo.
Install
pip install "murakumo[canvas,verify,duckdb]"
murakumo init my_platform # asks about your warehouse and orchestrator, then shows what to set up
cd my_platform
murakumo setup # checks drivers, variables, keys and connections; says what to do
murakumo canvas # the visual editor
Usage
murakumo init my_platform --target snowflake --yes # or answer with options, without questions
cd my_platform
murakumo setup --connect # also test the warehouse and source connections
murakumo validate # check the manifest and model; exits 1 on errors
murakumo validate --fix # write stable ids into hand-written YAML
murakumo validate --strict # fail on warnings too (useful in CI)
murakumo validate --format json # machine-readable diagnostics
murakumo schema entity # JSON Schema for editors: manifest, model, entity, source, relationship
murakumo import csv dictionary.csv # or: excel, database, file, openapi, json
murakumo import database env:ERP_URL --source erp # needs murakumo[postgres] or murakumo[duckdb]
murakumo import database env:ERP_URL --source erp --table sales.orders # only some tables
murakumo import # every source with a from: line in murakumo.yaml
murakumo add column dim_customer email string --pii # add or remove sources, domains, entities, columns, relationships
murakumo rename entity lineitem order_line # relationships, mappings and the file follow
murakumo move column dim_customer email --after name # reorder columns
murakumo add domain finance --owner "Finance team" # domains become dbt groups
murakumo lineage fct_trip.trip_id # where a column comes from; --down for what uses it
murakumo canvas # the visual editor, on http://127.0.0.1:8765
murakumo generate # generated/: dbt project and DDL for your warehouse
murakumo generate --check # fail CI if generated/ is out of date
murakumo migrate # ALTER statements for tables that keep data
murakumo add schedule nightly --cron "0 6 * * *" # schedules become pipelines for your orchestrator
murakumo schedules # when each runs, and what it refreshes
murakumo export sql # the project as plain SQL, without dbt
murakumo docs # pipeline docs: tables, columns, lineage, schedules
murakumo ci # a GitHub Actions (or GitLab) workflow for every push
murakumo sync # bring in main: merge, regenerate, re-plan migrations
murakumo diff # model changes since main, and what they reach
murakumo env # your own schemas; clone and drop them
murakumo runs # the latest runs, loads and failed tests
murakumo run --engine pyspark --sample 200 # the pipeline as PySpark (or Polars) jobs
murakumo verify # build and test it all on DuckDB, twice
murakumo verify --warehouse snowflake # or on Snowflake, in throwaway schemas
murakumo build --sample 200 # build into the project's warehouse and keep the tables
murakumo config --target snowflake # change the answers you gave init
murakumo --help # every command, with what it does
Extras: canvas (the editor), verify (builds on DuckDB), duckdb (files and DuckDB), postgres,
snowflake, polars and pyspark (the pipeline as Python jobs). murakumo setup tells you which a project needs.
Docs: starting a project and setting up, model files and validation rules, importing metadata, generating and verifying, Snowflake, the canvas, schedules, pipelines and CI, working as a team.
Development
uv sync
uv run murakumo --version
uv run pytest
uv run ruff check
uv run ruff format --check
Metadata
Release files for murakumo 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| murakumo-0.4.0.tar.gz | 384.9 kB | With provenance | Details for murakumo-0.4.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| murakumo-0.4.0-py3-none-any.whl | Python 3 | none | any | Details for murakumo-0.4.0-py3-none-any.whl |
Total release size: 758.9 kB
Release files / murakumo-0.4.0.tar.gz
| Download URL | murakumo-0.4.0.tar.gz |
|---|---|
| Size | 384.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
60d5c3b4beb0cab3797ad18c4dfc76b6f00c658694457bad4a3cb69c2df520d7
|
|
BLAKE2b-256 checksum How to use checksums |
75652788977b2601a6b340f7853d38bb977a5a355fc6e53b6deae78c1280da86
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logRelease files / murakumo-0.4.0-py3-none-any.whl
| Download URL | murakumo-0.4.0-py3-none-any.whl |
|---|---|
| Size | 374.0 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
05dae68a769a44830816364e6fea788f0f9d8e949599aec25fb451d7a377ea31
|
|
BLAKE2b-256 checksum How to use checksums |
fed9171224e494999f7859b27b638fd01675b57db216297d96b81a98cf3f39a5
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
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 30, 2026.
Transparency logSecurity for murakumo 0.4.0
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.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for murakumo-0.4.0.tar.gz
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 30, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.