Bring your warehouse
closer to your team.
Let finance, sales and operations ask about revenue, retention and performance in plain English, using the tables your data team already maintains.
Free plan. No credit card required.
Analytics warehouse
finance / monthly_revenue3 rows
| month | revenue | accounts |
|---|---|---|
| Jul 2026 | $96,000 | 242 |
| Aug 2026 | $100,000 | 258 |
| Sep 2026 | $112,000 | 284 |
How much did revenue grow in September?
12%
Up $12,000 from August,
using your warehouse table.
product / account_retention3 cohorts
| cohort | started | active at 3 mo. |
|---|---|---|
| Apr 2026 | 100 | 82 |
| May 2026 | 100 | 86 |
| Jun 2026 | 100 | 91 |
Which cohort had the best three-month retention?
91%
The June cohort:
91 of 100 accounts still active.
Queries run in your warehouse, as your connected account.
Choose a table to explore a different question
Connect directly
- Snowflake
BigQuery
Redshift
Databricks
ClickHouse
MotherDuck
01 / Build on what’s there
Give business questions
the right context.
Connect the tables your team already maintains, then add definitions such as what counts as revenue or an active account. Your existing pipelines continue to prepare the data.
Add knowledge and rules- finance.monthly_revenue
monthrevenueaccounts
“How did revenue change last quarter?”
- product.account_retention
cohortstarted_accountsactive_at_3_months
“Which cohort kept the most accounts after three months?”
Illustrative table names
02 / Get connected
Give your team a way into the warehouse.
Connect an account
Use the authentication method your warehouse supports, with the intended read access.
Confirm the tables
Choose the relevant project, dataset, database or schema and let Supaboard discover its structure.
Set up the team’s agent
An agent is the AI analyst set up for your team’s data. Give it the tables and business context it needs, and choose who can use it.
Before you start.Ask your data team for the right account, data scope and compute configuration. Setup fields differ by warehouse. Read the setup guide
03 / Understand the connection
Queries run in your warehouse,
using the account you connect.
Supaboard queries through the account you connect and uses your warehouse’s compute. Scope that account to the data you want to make available.
Answers reflect the latest data available in your warehouse tables.
Your warehouse compute
Queries run there and can incur its usual usage costs.
The connected account’s permissions
Access is limited to what that account can read.
Your tables’ freshness
Answers reflect the data that has reached the warehouse.
A few practical details
Common questions
Does Supaboard replace our data pipelines?
No. Your pipelines continue to load and transform data into warehouse tables. Supaboard connects to those tables for analysis.
Whose warehouse permissions do queries use?
Queries run using the account connected to Supaboard. They do not automatically use each teammate’s warehouse identity. Limit the connected account’s access, then configure data-source and agent access in Supaboard.
Does Supaboard copy our warehouse?
Supaboard queries your connected warehouse without creating a full replica. Returned query results are saved with the conversation.
Does querying incur warehouse costs?
Yes. Queries use your warehouse’s compute, so the warehouse’s usual usage charges can apply. Your data team should choose an appropriate compute setup.
Can I compare warehouse data with an uploaded file?
Yes. For example, compare your revenue table with an uploaded forecast. Make sure the period and business definition match, and that the agent has access to the warehouse table.
Make your warehouse part of everyday work.
Connect the tables your team trusts. Start with their next question.
Start FreeBook a 30-minute demo
Free plan. No credit card required.