DBT CORE & DBT OSS · INDEPENDENT ENGINEERING
Build maintainable, testable SQL transformation projects on dbt v1, dbt OSS or the free dbt distribution. Bassirah helps teams adopt modular modeling, testing, documentation, CI/CD and orchestration patterns.
Independent dbt engineering.
These are independent Bassirah engineering and support offerings. Bassirah is not a dbt Labs partner. They do not imply upstream vendor or foundation endorsement, official vendor support rights, enterprise feature entitlement or maintenance guarantees. Fixes to proprietary dbt components and any dbt Labs features come only from dbt Labs. Commercial dbt platform products are not part of this offering.
CLEAR NAMING
dbt Labs renamed its distributions when dbt v2.0 was released in September 2026. The Python-based 1.x line continues as dbt v1 (dbt Core 1.x). dbt Core v2 is now called dbt OSS and is licensed entirely under Apache 2.0. The former dbt Fusion engine is now called dbt: free to use, but not open source. We name the exact version, adapter and distribution in every project.
Supported releases.
Bassirah provides independent engineering for projects on dbt v1 (dbt Core 1.x) and dbt OSS (dbt v2), both licensed under Apache 2.0, and on the free dbt distribution (dbt v2), a dbt Labs product under the dbt Product Licensing Agreement. The adapters in scope are listed in each statement of work. Release scope is reviewed quarterly and when upstream naming, licensing or major versions change. Last reviewed: 20 October 2026.
| Name you may see | What it refers to | How Bassirah treats it |
|---|---|---|
| dbt v1 / dbt Core 1.x | The Python-based 1.x generation, installed with the dbt-core package. v1.12 is the current minor release; v1.13 is in beta. Licensed under Apache 2.0. | Supported for existing projects and planned upgrades, within the release scope above |
| dbt OSS (formerly dbt Core v2) | The dbt v2 distribution built only from the Apache 2.0 source in the dbt-core repository | Supported for new projects and migrations, within the release scope above |
| dbt (formerly the dbt Fusion engine) | The dbt v2 distribution dbt Labs recommends by default. Free to use, but not open source: it includes dbt-specific components under the dbt Product Licensing Agreement. | Supported for project engineering, within the release scope above. Fixes to its proprietary components come only from dbt Labs |
| dbt platform | dbt Labs' hosted, commercially licensed product | Not covered by this independent offering |
WHY IT MATTERS
dbt brings software engineering discipline to data transformation and enables standardized models and dependable deployment processes.
Instead of fragile scripts and undocumented stored procedures, dbt projects express transformations as version-controlled SQL models with declared dependencies, data tests and generated documentation. That makes changes reviewable, failures visible before they reach reports, and lineage clear from source to dashboard.
The tool alone does not create that discipline. Project structure, naming conventions, testing policy, environment promotion and ownership determine whether a dbt project stays maintainable at hundreds of models. That is where Bassirah helps.
WHAT BASSIRAH DELIVERS
DELIVERY PATTERN
We will review structure, tests and CI/CD and prioritize fixes.
USE CASES
Medallion-aligned analytics transformations, from raw sources through cleaned and conformed layers to business-ready marts.
Management reporting and finance reconciliation pipelines with tested control totals and documented logic.
Governed metric models and reusable dimensional datasets that give every team the same definitions.
COMPATIBILITY
dbt works through adapters for each SQL engine, and adapters are released and maintained separately from dbt itself. Before we advertise an integration, we confirm adapter version, supported materializations and runtime requirements for your target engine.
| Target engine | Typical role | What we validate |
|---|---|---|
| Trino OSS or Starburst | Transformations over federated sources and lakehouse tables | Adapter release vs. dbt release, supported materializations, catalog and table-format behavior |
| ClickHouse | Transformations for analytical serving tables | Adapter release, incremental strategies, engine and cluster settings for model tables |
| PostgreSQL | Transformations for operational reporting and smaller marts | Adapter release, transaction behavior, load on production instances |
| Other engines | Project-specific | Compatibility, licensing and support status before commitment |
WORKS WITH
ClickHouse or Trino/Starburst as query engines where current adapters work; DataHub for lineage and documentation ingestion.
Ingest dbt models, tests and lineage into a searchable catalog with ownership.
Build analytical serving tables with tested, versioned models.
The full solution pattern, from source mapping to governed marts.
Only for the 1.x line. Since dbt v2.0 (September 2026), dbt Labs calls the Apache 2.0 v2 distribution dbt OSS (formerly dbt Core v2) and the free, proprietary-licensed v2 distribution dbt (formerly the dbt Fusion engine). The 1.x line continues as dbt v1, also known as dbt Core 1.x. Bassirah names the exact version, adapter and distribution supported in every project.
Our current release scope is shown in the supported-releases note on this page and confirmed in each statement of work, together with the adapters in scope. We review it quarterly and whenever upstream naming, licensing or major versions change.
No. Bassirah is not a dbt Labs partner. Our dbt services are independent engineering and support for projects on dbt v1, dbt OSS and the free dbt distribution. They do not include vendor support or entitlements: fixes to proprietary dbt components and any dbt Labs features come only from dbt Labs, and commercial dbt platform products are not covered.
Yes. We inventory existing logic, map it to modular models, add tests, and run old and new pipelines in parallel until control totals reconcile. Cutover happens only after agreed validation.
No. dbt defines and tests transformations. Scheduling runs through your orchestrator, and enterprise discovery and ownership are better served by a catalog such as DataHub, which can ingest dbt metadata and lineage.
Tell us about your engines, models and delivery process. We will scope an assessment and a practical next step.
Operations & Reliability
dbt v2 reached general availability in September 2026. What strict validation, new commands and adapter coverage mean for an existing v1 project.
dbtdbt OSS
Read article : dbt v2 Is Generally Available: What the New Engine Changes for an Existing Project→
