Most BI tools added an AI feature.
Kater is BI your agent can build.
Your models, metrics, dashboards and apps are files in git. Your coding agent writes them. Kater compiles every change, and you approve the diff.
Everyone else reads the result in the browser, or asks in Slack, Claude or ChatGPT. Every answer uses the definitions your data team governs.
Compare the tool you use today- modeling/kater_objects/
- orders.sql
- workspaces/shop/
- query_contracts/
- monthly_revenue.sql
- charts/
- revenue_by_region.sql A
- dashboard.yaml M
- apps/weekly_brief/
- index.html
dashboard.yaml
tiles:
- chart: monthly_revenue_chart
section: overview
- span: 12
+ span: 8
+ - chart: revenue_by_region
+ section: overview
+ x: 8
+ span: 4
Added Revenue by region to the Shop dashboard. It reuses the shared Revenue measure. Both files compile.
The semantic layer
Most semantic models are YAML. Kater’s is SQL.
Data team
Business users and agents
Start with the SQL you already write. It runs on your warehouse as it is.
scratch.sql
- 1SELECT
- 2 s.region,
- 3 SUM(s.orders) / SUM(s.visits) AS conversion_rate
- 4FROM shop.web.sessions AS s
- 5GROUP BY s.region
Layers and promotion
Business users build in their own workspaces. Collaborate on what becomes shared.
A new metric starts in one query, and moves up a layer when it proves useful. Its meaning stays the same.
- 01
In a query.
A person or an agent declares a measure in one query. Only that query reads it.
- 02
In the workspace.
Promote it to the workspace root. Every query in the workspace reads one definition.
- 03
In the shared layer.
The data team approves the request. Every workspace on the connection reads it, and it shows as verified.
Kater finds the same formula in more than one place, and recommends a promotion for it.
How modeling worksMake it yours
Most BI tools ship an agent you cannot change. Kater gives you what works, and you own all of it.
-
0 + Agents -
0 + Skills -
0 + Workflows
ai_tools/skills/brief-me.mdChanged
- # Brief me
- Say what moved since the last brief.
Why teams switch
BI as code used to cost a lot of typing.
An agent now does the typing.
What is left is the part a person should do: decide what a metric means, read the diff, and approve the change. Software teams already work this way. Data teams are next, and Kater is built for it.
Everything is a file.
Models, metrics, queries, dashboards and apps live in git. Search them, review them, roll them back, and take them with you.
Your agent does the building.
Claude Code, Codex or Cursor works through the Kater MCP. Kater compiles every write and refuses one with an error.
One definition behind every number.
Revenue is defined once, in SQL. Every dashboard, app and agent answer reads that same measure.
Everyone else just asks.
Business users read dashboards and apps in the browser, or ask in Slack, Claude or ChatGPT. Nobody needs a seat in a BI editor.
Define each metric once.
Your agent builds the rest.
Start a 30-day free trial on your own warehouse, or book a demo.