Datost connects directly to PostgreSQL as a read-only query client. Once connected, the Slack agent introspects your schema, writes SQL, and returns answers in-thread.Documentation Index
Fetch the complete documentation index at: https://datost.com/docs/llms.txt
Use this file to discover all available pages before exploring further.
Before you connect
Gather the following from your database administrator:- Host (e.g.
db.example.com) - Port — defaults to
5432 - Database name — defaults to
postgresif left blank - Username and password
- SSL mode —
disable,require,verify-ca, orverify-full
Create a read-only role
Datost only needsSELECT. Create a dedicated role so the agent cannot mutate data.
Tables you never grant
SELECT on stay invisible to the agent. You can further hide specific tables from the admin panel under Data sources → Table preferences.Connect from the admin panel
Enter connection details
Fill in host, port, database, username, password, and SSL mode. Paste a connection URL if you prefer — Datost will parse it into fields.
Test the connection
Click Test connection. Datost runs
SELECT version() against your database and reports latency and server version.Public vs private databases
If your PostgreSQL instance is reachable over the public internet (with SSL and IP allow-listing), the direct connection above is all you need. For databases on a private VPC, behind a bastion, or otherwise unreachable from Datost’s servers, install the Tunnel Agent inside your network. The agent opens an outbound connection to Datost and proxies queries to your database — no inbound firewall changes required.Limitations
- Datost executes
SELECTqueries only. Writes, DDL, and transactions are blocked. - Connection pools cap at 5 concurrent connections per data source with a 15s connect timeout.
- Queries run against your live database; budget accordingly or point Datost at a replica.
- Tables excluded via table preferences are omitted from schema introspection and query planning.