Folders by domain
Reconciliation, finance, support, on-call. A folder per topic, queries with descriptions, the team finds what they need.
Shared SQL query library
A shared SQL query library the team will actually use.
The diagnostic query that untangled last month's outage, the reconciliation the back office runs every morning, the cleanup probe nobody remembers writing. Save each of them once, run them through the agent, and every execution leaves a record behind it.
Variables for the bits that change
Typed variables (string, number, date, datetime, json, guid, boolean) with defaults at the query level and overrides per user.
Versioning per query
Every save is a checkpoint you can go back to, with a diff that shows what moved and who moved it.
Read-only via agent
A classifier rejects anything that writes before it is sent, the connection points at a read-only role, and the agent enforces its own timeout on top of both.
Every run is a row
Rendered SQL, variables applied, who, when, on which connection, row count, duration. Compliance and post-mortems happy.
One click to a recurring export
A saved query becomes a schedule that delivers CSV or Excel to email or Slack. The recurring extract automates itself.
Why teams move off the alternatives
The places SQL hides today.
pgAdmin and DBeaver tabs
Personal, gone the day the laptop is reimaged, impossible to share without pasting, and nothing about the run is recorded.
GitHub gists
Shared, but disconnected from the database, with no variables and nothing to run. Half of them turn out to be private anyway.
Slack threads
Searchable for two weeks then buried. The link to the message dies when the channel rotates. No variables, no audit.
Notebooks and dashboards
Heavyweight for an operational query. Often want cloud DB access. Not the right tool for a quick reconciliation extract.
Query workflow guides
Use the library as the source of truth for operational SQL.
SQL query repository for small teams
Folders, variables, audit, and private execution without a heavy catalog process.
Read the guideStop sharing SQL in Slack
Move incident and support SQL into a shared workspace once it becomes repeatable.
Read the guideSave and reuse SQL queries
Create reusable team queries with descriptions, variables, and visible run history.
Read the guideParameterized SQL queries
Make customer, date, and status inputs explicit for operational reruns and schedules.
Read the guideCompare
Compare private SQL collaboration workflows.
PopSQL alternative
Compare collaborative SQL editing with a private operational workspace for saved SQL, agent execution, and schedules.
Read comparisonMetabase scheduled reports alternative
Compare BI dashboard subscriptions with scheduled SQL exports from a shared query library.
Read comparisonFAQ
Shared SQL query library: save, share and audit team SQL
Can the team see and edit queries together? +
Yes. Save a query under the company scope and the team sees it. Personal scope keeps it private. Versioning means edits are not destructive.
Are variables required? +
Optional. Plain SQL works. When a query needs a customer id or a date range, mark it as a variable and the runner prompts for it. Defaults at the query level, overrides per user.
Can I run write queries? +
No. DML and DDL are rejected before dispatch. Use a read-only database role for the connection. To write to the database, use a migration tool and let Taavik observe the result.
Move it in
Save the first query the team keeps re-writing.
Free forever for personal use, Pro for shared workspaces and unlimited library size.