Product activity in leadership reporting
If your product runs on PostgreSQL, usage and activity can sit on the same dashboard as the numbers from your other systems, so leadership sees which customers are growing and which are going quiet.
Go Fig + 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.
Key facts
What you can do with PostgreSQL in Go Fig
PostgreSQL often sits behind a company's own software and internal tools, which makes it the record of what customers and teams actually do. One setup session with a solutions engineer and your data team connects it. Go Fig reads your tables in PostgreSQL itself and doesn't copy them into its own storage. The connection is read only, and a read-only database user, which we recommend, means PostgreSQL itself blocks any change. Those records then sit next to every other system you connect, ready for dashboards, scheduled reports, and questions to Celeste, Go Fig's AI analyst.
Internal tools out of the spreadsheet
Orders, jobs, or projects kept in an internal tool's database show up in Go Fig with everything else, so nobody exports them to a spreadsheet each week.
Questions without writing SQL
Ask Celeste, Go Fig's AI analyst, a question in plain English and get the answer from your PostgreSQL tables, with no SQL (the language databases are queried in) to write.
What Go Fig reads from PostgreSQL
How to connect PostgreSQL
Create a read-only user
Your data team creates a PostgreSQL user for Go Fig and grants it read access (it can look but never change anything) to just the tables and views it should see.
Make the database reachable
Go Fig connects to the host and port you give it. If a firewall sits in front of the database, your data team works through what to allow with your solutions engineer.
Enter the connection details
Add the host, port, database name, username, password, and SSL mode (whether the connection is encrypted) in Go Fig.
Check the tables
Make sure the tables you expect appear in Go Fig. After that, Go Fig queries PostgreSQL directly whenever the data is used.
Questions about Go Fig + PostgreSQL
What usually lives in PostgreSQL that Go Fig can use?
Often the records your own software or internal tools keep, like customers, projects, orders, and usage. Go Fig reads the tables you grant it, so that data shows up in reports and Celeste's answers next to your other systems.
Is our PostgreSQL data copied anywhere?
No. Your tables stay in PostgreSQL and Go Fig reads them there. Its search index does keep field names, descriptions, and a few sample rows so it can find the right table, as our security page explains.
How current is the data?
As current as the database itself. Go Fig reads PostgreSQL each time the data is used, so there is no separate copy falling behind.
Could Go Fig write to our database?
No. The connection is read only. A read-only user is the second lock we recommend, so PostgreSQL itself refuses any change.
What connection details does Go Fig need?
The host, port, database name, a username and password, and the SSL mode, which sets whether the connection is encrypted.
Ready to connect PostgreSQL?
A solutions engineer connects it with you on the call. Then you see Go Fig work on your own data.