Amazon S3
Go Fig reads CSV, Parquet, and JSON files straight from your Amazon S3 bucket, so exports and file-based data feed the same reports as everything else.
5 of 40 integrations
Database integrations
Warehouses, databases, and file storage you already own. Read where they sit, so your data foundation starts from tables your team already trusts.
Azure SQL Server
Bring the records your own applications keep in Azure SQL into Go Fig's dashboards, reports, and answers, read where they sit and never changed.
Google BigQuery
Put the tables your data team keeps in Google BigQuery behind your dashboards, scheduled reports, and Celeste's answers, read in place and never changed.
PostgreSQL
Go Fig reads your PostgreSQL tables in place, so what your own software records about customers and work sits next to every other system in your reporting.
Snowflake
Go Fig reads your Snowflake warehouse where it sits, so the tables your data team already trusts feed your reports, dashboards, and AI agents.
On the roadmap
Not available yetWhen your company already keeps data in a warehouse
Set up once by whoever owns it
A solutions engineer connects the warehouse with your data team. After that, nobody else has to touch it.
Read where it sits
Go Fig never writes to these sources. Data in Snowflake, BigQuery, PostgreSQL, Azure SQL, and S3 is read in place rather than copied into Go Fig's storage.
One set of numbers
Go Fig works from the tables your data team already reports from, so the figures in a report or an answer match what everyone else sees.
Questions that span both
Celeste can answer a question that needs the CRM and the warehouse together, and she shows where each number came from.
The agents read it too
Usage, contract terms, or service history that already sits in a table can show up next to the account, so the brief before a renewal starts from how the customer uses what they bought.
Don't see a tool your team uses?
Tell a solutions engineer what your team uses. You'll see what connects on the call.