When you inherit someone else's SQL, you spend an hour just figuring out what it is supposed to do. The visual lineage answers half the question; Query Lens™ answers the rest.
Step 1: see the lineage
Paste the query. The graph shows source tables, intermediate CTEs, joins, and the final projected columns. Click a column to trace it back to its source columns.
Step 2: Query Lens™
From any node, request a Query Lens™ explanation. You get a short summary of what the SQL does plus a list of potential issues (missing GROUP BY columns, suspect joins, unused CTEs, etc.).
Step 3: share or save
Save the diagram with the explanation pinned, or share a public link with the explanation visible. Great for handoffs and code reviews.
What it looks like
Frequently asked
Is my SQL sent to a third-party LLM?
Only when you explicitly request a Query Lens™ explanation. Visualization itself runs entirely on our own parser; nothing is sent to any LLM.
Does it explain just one node or the whole query?
You can request an explanation for a single object (one view, one procedure) or for the whole graph.
Does it suggest fixes?
Yes. Query Lens™ flags likely issues alongside the explanation when it finds them.