# Dashboards as Code: Version-Controlled BI | Silicon

URL: https://meetsilicon.com/product/dashboards-as-code/

> Every Silicon dashboard and chart lives as YAML next to your dbt models: branched, reviewed, tested and rolled back like the rest of your code.

silicon/dashboards/revenue-overview.yml
1 name: Revenue overview 2 slug: revenue-overview 3 tiles: 4 - type: saved_chart 5 properties: { chartSlug: net-revenue-by-month } 6 - type: saved_chart 7 properties: { chartSlug: arr-by-segment }
Reliability / Dashboards as code
# Dashboards as code, reviewed like software
Every dashboard and chart lives as YAML next to your dbt models. Your team commits, branches and reviews changes in pull requests, and tests run before anything reaches production.
Book a demo
30-minute demo with the founder
Works with the stack you already run.
dbt
Snowflake
BigQuery
Databricks
Redshift
Postgres
ClickHouse
GitHub
Slack
dbt
Snowflake
BigQuery
Databricks
Redshift
Postgres
ClickHouse
GitHub
Slack
dbt
Snowflake
BigQuery
Databricks
Redshift
Postgres
ClickHouse
GitHub
Slack
Problem
## Click-built dashboards have no history
When BI lives only in a UI, changes skip review, nobody knows who changed what, and a broken dashboard is fixed by hand.
- 01 Changes go live without anyone reviewing them.
- 02 There is no record of who changed a chart, or why.
- 03 Rolling back a broken dashboard is a manual rebuild.
How it works
## Version, test and roll back your dashboards
Version
Test
Roll back
01 Dashboards as code
### Version-controlled YAML
Dashboards and charts are files in your repository. Branch them, review them and merge them like any other change.
silicon/charts/arr-by-segment.yml
1 name: ARR by segment 2 tableName: fct_subscriptions 3 metricQuery: 4 metrics: [fct_subscriptions_arr] 5 dimensions: [fct_subscriptions_segment] 6 chartConfig: { type: cartesian }
Features
## Software workflows for analytics.
### In your repository
BI that lives next to the models it depends on.
- Dashboards as YAML
- Charts as YAML
- Pull request review
### Before merge
Problems caught before anyone sees them.
- Automated validation
- Preview environments
- Schema mismatch checks
### After merge
Confidence that you can always go back.
- Version history (30 days Team, 60 days Pro)
- Audit trail
- One-click restore
FAQ
## Questions, answered
### Which git hosts are supported? +
GitHub on every plan, and GitLab, Azure DevOps and Bitbucket on Pro and Enterprise.
### Can people who don't write code still edit dashboards? +
Yes. Dashboards can be edited in the Silicon UI too. Teams that want review on every change can manage them as code.
### How long is version history kept? +
30 days on Team, 60 days on Pro, and a custom period on Enterprise.
## Related
- Schema protection ->
- Semantic layer ->
- dbt is where data work becomes software work ->
## Tell us where your data lives today.
Book 30 minutes with the founder. Tell us where your data is today, and see Silicon running on sample data.
Book a demo
30-minute demo with the founder