This repository has been archived.
As a result all of its historical issues and PRs have been closed.
Please do not clone this repo without understanding the risk in doing so:
- It may have unaddressed security vulnerabilities
- It may have unaddressed bugs
Click for historical readme
<p align="center"> <img src="https://raw.githubusercontent.com/dbt-labs/dbt/ec7dee39f793aa4f7dd3dae37282cc87664813e4/etc/dbt-logo-full.svg" alt="dbt logo" width="500"/> </p> <p align="center">
>
> dbt Server supported our legacy Semantic Layer, which was fully deprecated in December 2023.. In October 2023, we introduced the GA of the revamped dbt Semantic Layer with significant improvements, made possible by the acquisition of Transform and the integration of MetricFlow into dbt. The dbt Semantic Layer is now independent of dbt Server and operates on MetricFlow Server, a new proprietary technology designed for enhanced connectivity and scale.
Welcome to the dbt-server repository! The dbt Server is intended to provide a web API for dbt operations and replace the dbt-rpc Server.
Important: this is major version zero software and APIs should not be considered stable. If you do take a dependency on this software we recommend an exact version pin.
dbt is typically used through its command line interface (CLI). The source code of dbt is almost all Python. dbt Server uses FastAPI to create a web API from a thin wrapper around dbt-core and its adapter plugins.
Familiarity with dbt is assumed for dbt Server -- check out how to get started otherwise.
See the developer setup in the contributing guide to get started with dbt Server.
The dbt-server repository uses the Business Source License (BSL). That makes the repository "source available", unlike most of our repositories which are "open source". See the license and our blog on licensing for details.
Everyone interacting in the dbt project's codebases, issue trackers, chat rooms, and mailing lists is expected to follow the dbt Code of Conduct.
