Reports on the warehouse you already trust
Dashboards and scheduled reports read straight from Snowflake, so leadership sees the numbers your data team already models instead of an export someone rebuilt by hand.
Go Fig reads your Snowflake warehouse where it sits, so the tables your data team already trusts feed your reports, dashboards, and AI agents.
If your data team already runs Snowflake, your data foundation can start there. They connect it once with a solutions engineer. Your data stays in your Snowflake. Go Fig reads it there and doesn't copy it into its own storage, then sets it next to every other system you connect. Leadership gets dashboards and scheduled reports built on the tables your data team already maintains. Celeste, Go Fig's AI analyst, answers questions from them and shows which table each number came from. AI agents read the same tables when they do their work. Go Fig only reads. It never changes or deletes anything in Snowflake.
Dashboards and scheduled reports read straight from Snowflake, so leadership sees the numbers your data team already models instead of an export someone rebuilt by hand.
Product usage, contracts, or billing history from Snowflake sits next to the customer in your CRM, so an account that is slipping shows up before the renewal, not after it.
Ask Celeste, Go Fig's AI analyst, about revenue, usage, or a single customer and see which Snowflake table each number came from.
Your data team creates a dedicated Snowflake user and a role for it. The role gets USAGE on the warehouse, database, and schema, and SELECT (read access) on the tables and views you want Go Fig to see. Don't grant ACCOUNTADMIN or SYSADMIN. A read-only role is all Go Fig needs.
Choose the warehouse (the Snowflake compute that runs queries) Go Fig should use. A dedicated small warehouse keeps Go Fig's usage easy to see on your Snowflake bill.
With a solutions engineer, enter the account, username, password, warehouse, database, schema, and role. Once it connects, they walk through what Go Fig can see.
Your tables show up in Go Fig and are read straight from Snowflake each time they are used, so there is no copy to keep in sync.
Your data stays in your Snowflake. Go Fig reads it there and doesn't copy your tables into its own storage. So it can find the right table, it keeps field names, descriptions, and a few sample rows in its search index, as our security page explains.
No. Go Fig only reads from Snowflake, and the role you give it should be read only, so it can look but never change or delete anything.
As current as your Snowflake. Go Fig reads the data where it sits each time it's used, so there is no separate update schedule.
Someone on your data team who can create a Snowflake user and role, and a solutions engineer from Go Fig. After that, the rest of the company just uses the reports, dashboards, and answers built on it.
Point Go Fig at its own small warehouse. Every query Go Fig runs then shows up under that warehouse on your Snowflake bill, apart from your data team's work.
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.