What Paradime is, for you
The data team builds pipelines in Paradime; you consume their output with context. Instead of asking “is this dashboard number right?” in Slack, you can check the definition, the freshness, and the pipeline behind it yourself. You’ll use four apps:Concepts you should know
- Models are the products. The data team ships “models”: governed tables built with dbt™, each with documentation and tests. The Catalog is the index of them. Curious how they’re made? See what is dbt™.
- Lineage answers “where does this come from?” Every model traces back to raw sources and forward to dashboards, so you can judge whether a number is safe to use, and what’s affected when something upstream breaks.
- Freshness comes from schedules. Data updates when a Bolt schedule runs. If a dashboard looks stale, check the schedule’s last run before assuming the data is wrong. See what is Bolt.
- Your access is read-only by design. You see production data documentation, lineage, run logs, and cost metrics; editing code and running pipelines require the Developer role. See roles and permissions.
Your first session
1
Find a dataset you use
Catalog
Search for a table or metric you already know from a dashboard, and read its documentation.
2
Trace where it comes from
Lineage
Open its lineage and follow it back to the raw sources.
3
Check the pipeline behind it
Search Bolt schedule status
See when it last refreshed and whether it succeeded.
4
Look at cost and health
Radar
Browse warehouse spend and pipeline health metrics.
Go deeper
Monitoring and discovery
How Catalog, Lineage, and Radar fit together.
Key terms
The vocabulary you’ll see across the app.
How Paradime works
The full picture: workspace, apps, and roles.
Need to build models?
Ask your Admin for the Developer role, then start here.