Charts constructed for Chat · dbt Charts


AI for information is here, and the long-promised self-serve analytics is lastly
taking place. Anyone with an information connection can talk a report into presence in
an afternoon, and the very first outcomes are excellent.

The frictions appear quickly, though. By default a representative turns one easy report
into a stack of files: HTML, CSS, and JavaScript, a number of chart libraries,
and a React or Streamlit app once it needs to be live. Tracing an outcome back to
its source implies following it through a number of languages and files, which is
sluggish for individuals to examine and costs the representative time and tokens on every modification.

BI tools went the other method and bolted copilots onto their UI-first apps.That
keeps the AI on governed rails, however narrow ones: the representative can do just what the.
UI exposes.

So today you select in between the unpleasant flexibility of code and the narrow control.
of a BI tool.
We constructed a 3rd choice: skip ahead, or keep reading.
for how BI got here.

Unbundling BI

As dbt Labs creator Tristan Handy composed just recently in.
BI’s Second Unbundling:

When I began in information, BI tools were full-stack. Everything took place within.
one item: information consumption, change, calculate, caching, semantics,.
visualization, identity. The BI tool was the information stack. MicroStrategy,.
Cognos, and so on: they’re not simply visualization tools, they’re incorporated information.
platforms.

Then the contemporary information stack occurred. From ~ 2015 to 2022, the facilities.
layers of that BI package got taken out and became purpose-built.
facilities. Compute went to the Big 5. Ingestion went toFivetran
Transformation went to dbt. The BI tool was entrusted: visualization,.
interactive analytical user interfaces, semantic meanings (in some cases!),.
identity and gain access to management, and webhosting.


  1. Warehousing
    Big 5
  2. E
    L
    T
    Extract
    Load
    Transform

BI
whatever else

What that unbundling left is the BI tool we understand today, and charts.
are its greatest piece. They remained in the UI for excellent factor: for many people, clicking is quicker than composing YAML. But a growing number of charts will not be made by.
individuals. As the front end and user of whatever ends up being significantly a chat representative, this.
choice turns. Agents are proficient in code, SQL, and Git, and awkward in somebody.
else’s UI. So charts require to relocate to where representatives work: into code.

Today we’re taking the next action in unbundling BI: we’re open sourcing.
dbt Charts, which takes charts out of.
the BI tool and puts them in code, particularly a brand-new structured YAML language.
that can state a complete interactive control panel in one auditable YAML file.Chat
easily with a representative, and what it makes has the flexibility of code while remaining.
simple to check out.


  1. Warehousing
    Big 5
  2. E
    L
    T
    Extract
    Load
    Transform

  3. New
    C
    Chart

BI
a couple of bits

In dbt Charts, SQL stays the language for stating WHAT information you wish to see,.
and we cover that in YAML to state HOW you wish to see it.

We have actually invested a long period of time distilling the language to a couple of core, extensible.
components: deep in what they can reveal, simple to arrange and check out. The YAML.
covers more than SQL. Markdown brings the prose, and Jinja, as in dbt, brings.
variables and macros.

Here’s a little example: one variable (a UI filter), one inquiry and one chart.

 variables: 
   status: 
     column:  main.documents.status

 questions: 
   doc_growth: |
     SELECT  DATE_TRUNC(' month',  created_at)  AS  month,
            AMOUNT( COUNT( *))  OVER ( ORDER  BY  month)
              AS  num_docs
     FROM  primary files
     WHERE  { {  filter(' status',  status) } } 
     GROUP  BY  1

 charts: 
   development: 
     title:  Documents developed, perpetuity
     type:  location
     inquiry:  doc_growth
     x:  month
     y:  num_docs

 rows: 
  -  development

That file is the entire board. The CLI renders any board file to fixed SVG,.
or to HTML, PNG, PDF, and even the terminal, on your laptop computer or in CI, and.
serves a folder of them as a website:

 dct render charts/documents. yml-- format svg  # or html, png, pdf, terminal
 dct serve

Those couple of components go deep: over 1,100 config alternatives today, throughout.
sixteen chart types and the.
composed charts
constructed from them. And like any excellent language, it can reveal complex designs.
and visuals.

You seldom set those alternatives by hand. Styles waterfall: a chart acquires from its.
board, the board from its style, and a style is one line to change. A board can.
likewise extends: another board, so a home design or a basic report is composed.
as soon as and acquired all over. Boards remain short, and theming stays low-cost.

A complete commercial performance board with KPIs, bars, a donut, a line chart, and a table

A total dbt Charts board, rendered from one easy-to-read YAML file.

Deep combination with dbt

You do not need to utilize dbt Charts with a dbt job, however when you do, a lot.
opens. The chart layer sits straight on the change layer, and the much deeper.
the combination, the simpler it is to alter both.

With dbt Charts, your charts/ directory site lives beside your designs/ in the.
very same Git repo, so a modification to a design and its charts ships on one branch,.
through one CI run, and breaks before it reaches production.

 your_dbt_project/.
 git/.
 dbt_project. yml.
 designs/.
 charts/ # brand-new folder in a dbt repo for your control panels.
 revenue.yml

Queries reach designs through ref(), dealt with from your manifest, so a relabelled.
design or a missing out on column stops working the pull demand that broke it,.
before dbt run restores the storage facility:

 dbt parse &&& & dct validate charts/

Support for the dbt Semantic Layer is prepared, so a board can utilize a metric as.
the job specifies it rather of reiterating its SQL. Follow
dbt-labs/dbt-charts#1.

Built for chat

Agents can be rather blind, and they do best with a tight feedback loop.
dbt Charts provides one: rigorous recognition of both the YAML and the SQL, and.
a comprehensive set of visualization checks that flag issues before anybody sees.
the board:

$ dct render charts/revenue. yml
 WARN-BAR-BAND-WIDTH-TOO-NARROW
 182 bands x  2 series throughout  640px
Fix:  roll up to a coarser grain.

 WARN-TABLE-COLUMNS-OVERFLOW
Table requires  980px however just  640px is readily available.
Fix:  drop columns or expand the slot.

A lovely, cohesive reporting system

We hope dbt Charts, like dbt before it, ends up being the open basic language for.
its layer of the information stack. We developed it for a future where people and AI.
develop together, and we desired it to appear like that future, not like another.
control panel grid. We hired RJ Andrews, a.
information graphic designer, author, and historian, to create the charts. His grasp of the craft’s history is what makes the outcome feel brand-new: it reaches past the control panel period to.
what charts appeared like when individuals drew them with care.

Many tools cheat with cards and boxes that phony positioning at the expense of visual.
sound and lost area. We exercised the spacing, sizing, and design of every.
chart, by itself and beside its next-door neighbors.

A dbt Charts board: showcase/general/dundersign-commercial-financeA dbt Charts board: showcase/general/one-dataset-nine-waysA dbt Charts board: showcase/boards/dundersign-support-operationsA dbt Charts board: showcase/boards/quarterly-business-reviewA dbt Charts board: showcase/charts/composed-chart-shapes

The result is a cohesive system of charts that feels a level above existing BI.

Alongside the open-source language, today we’re releasing.
dbtCharts.com in public beta: a hosted platform for the.
rest of BI. With charts took out, what stays is mainly hosting, gain access to.
control, and a UI. By their nature these maybe can’t be unbundled, or a minimum of.
should not be, so the platform manages them on top of the open-source language.

variables: questions: charts: rows: Chat UIHosting & &Access dbtCharts com BI platform dbt ChartsOpen chart language: YAML and SQL Semantic layerOptional dbt designsTransformation Your storage facilityData very same dbtGit repo(* )platform links to your storage facility and includes conversational analytics, a visual.
editor for the completing touches, variation history, and showing approvals.
for users and groups, so individuals checking out a board do not require a storage facility.
login.

The obviously, these charts were constructed for chat.

And platform has superior.
conversational analytics: like The or Claude GPT, however with permissioned.
read-only access to your storage facility and a professional analyst’s abilities and tools.
integrated in.
Chat by talking with charts, and at any point click in to tweak and.
conserve the board.Explore it’s constructed on the open language, every modification, from chat, the visual.
editor, or code, lands in the very same YAML in your

Because repo. Git is secured: the very same board works on your laptop computer, in CI, and on.
the platform, and groups can self-serve, representative in hand, without producing a.
2nd, concealed information stack.Nothing the beta

Try dbt

The language is open source under the Charts 2.0 license, and you can.
author, render, and serve boards in your area without producing an account. Apache it.
yourself, or hand your coding representative one line: Install uv tool set up dbt-charts

Terminal
/ AI
Claude charts of this with dbt
Make Charts with: uv tool set up dbt-charts && & dct abilities introductionStart dbt

is pre-1.0 and still altering. Charts the grammar modifications, boards.
move as they parse, so the boards you compose today keep rendering. When it, inform us what is missing out onTry, sign up with the conversation in [1][2] on #dbt-charts, and assist us develop the chart layer.
that open information facilities has actually been waiting on.Slack