Joe running in Slack is indeed a way to simplify and speed-up SQL optimization workflow for developers, as it takes seconds to get initial query execution plans and optimization recommendations.

>... With a Slack interface, so you don't need to bother with connection, provisioning, credentials and decommissioning.

It's worth noticing that Joe is a use case of Database Lab (https://gitlab.com/postgres-ai/database-lab) and it's still possible to use Database Lab features like thin-clones provisioning of production-sized databases and fast data state reset with Database Lab client CLI (https://postgres.ai/docs/database-lab/6_cli_reference) for purposes of SQL optimization without Slack integration. If a user has sufficient access to the data they can provision thin-clone with Database Lab client CLI and use psql to work with the clone.

Also, we have plans to add support of recommendations and statistics in CLI and REST API to the support of various messaging platforms in the future.

If you are using a PG client already you are probably not the target audience.

It's easier to tell someone to copy paste a query into Slack to get their weekly insights than teaching them how to set up pgcli or some other gui app. You'd also have to create tightly scoped permissions for everyone who only needs it from time to time.

I'd probably set up something like https://github.com/getredash/redash for these cases though, it's also very user friendly.

It's for SQL query optimization, not OLAP or similar, so it seems to me like the target audience probably already knows about the psql cli.

I do use command line clients, because I feel they are more available and convenient than GUI tools, but I'm not a PostgreSQL optimization wizard so I could be in the target audience. My customers probably are.