SaturnSQL

Shared connections plus scheduled Slack and Sheets delivery solve real ops friction. For production use, the deciding features would be role-based permissions at the connection and query level, query audit logs, and enforceable read-only access. Surfacing those clearly in onboarding would make a team's security review much easier.

Scheduled delivery to Google Sheets or Slack is a practical bridge between an SQL workspace and the people who consume recurring reports. The shared connection model could simplify handoffs, but I’d want per-query parameter support so one saved query can serve different teams or date ranges without duplicating it. How do you handle long-running jobs or schema changes when a scheduled delivery fails?

One shared SQL workspace for Postgres, MySQL, BigQuery and the rest, where a saved query can run on a schedule and land in Google Sheets or Slack, cuts the monthly report export grind. If you want to spend less on AI at work, take a look at pzero.studio.

A strong competitor to Supabase

As a dev-tool builder, the collaborative angle here stands out — most SQL editors are great for individuals but fall apart for teams. Shared connections plus a shared query library directly addresses the 'tribal knowledge in everyone's head' problem. The scheduled delivery to Sheets/Slack is the feature that would have sold my team — it replaces a surprising amount of manual export-and-email. Curious whether you support query parameters or variables in scheduled runs. Congrats on the launch!

Can a scheduled report be pinned to a query version so later edits do not change it?