For teams on dbt

You built the models. Now everyone can ask them.

Keep dbt as your source of truth. Your definitions guide every answer in Claude or ChatGPT, queries only touch the tables you approve, and each team sees only what it should.

The bottleneck

Every question lands on your data team. They’ve become the bottleneck.

How it works with dbt

Your repo stays in charge. We read from it.

  1. Your dbt repo

    Models and semantic models

  2. dbt parse in CI

    Converted to open OSI

  3. Checked on the PR

    Before anything changes

  4. Live on merge

    In Claude, ChatGPT and agents

What changes

One dbt project. Your team asking its own questions.

Start with the questions your data team answers every week and the reports someone builds by hand. Then open it up team by team, on the same definitions.

Questions

What dbt teams ask first.

Do we need dbt Cloud?

No. The CI step runs dbt parse, which is part of dbt Core.

What if we haven’t defined semantic models?

AI drafts them from the tables your dbt project builds, and your team reviews them before anyone relies on them.

Which warehouses?

Snowflake, Redshift, Postgres and MySQL today. On BigQuery or Databricks? Tell us on the call and we’ll check your setup.

How does this fit with dbt’s own tools?

They work together. dbt defines your models. FrontierOps puts them next to your other systems, with access per team, an audit trail, reports and agents, in any AI client.

Bring your dbt project. Your team asks it questions in about a week.