One family. Clear responsibilities.
Start with the common product API. Add storage, integrations and editor support independently.
What do these parts mean in practice? See each package in one monthly reporting example.
dataraft
A focused entry point to checked data products. The metapackage exposes 17 product verbs and dr_demo(); specialist functions stay in their component namespaces.
Explore ↗Coredataraft.core
Products, contracts, preparation and quality gates. Start in memory, compose ordinary R transformations, and inspect every execution result.
Explore ↗Storagedataraft.lake
Publish versioned data with DuckDB or DuckLake. Inspect release history, coordinate publication and recover interrupted operations.
Explore ↗Integrationdataraft.adapters
Sources, destinations and metadata publishers for databases, RDS, Parquet, pins, APIs, OpenLineage and OpenMetadata.
Explore ↗Experimentaldataraft.dbt
Configure dbt projects, run builds and inspect artifacts. Add managed publication when SQL results need DataRaft release governance.
Explore ↗Experimentaldataraft.metrics
Define metrics, evaluate checked inputs and retain frozen report evidence. A governed results layer, not a general-purpose semantic modeling engine.
Explore ↗Experimentaldataraft.ide
The optional R metadata bridge for Positron. Inspect an existing workspace or lake without transferring data cells to the extension.
Explore ↗