Show HN: Trilogy Studio, open-source browser-based SQL editor and visualizer https://ift.tt/6h2luOW

Show HN: Trilogy Studio, open-source browser-based SQL editor and visualizer SQL-first analytic IDE, similar to Redash/Metabase. Aims to solve reuse/composability at the code layer with modified syntax, Trilogy, that includes a semantic layer directly in the SQL-like language. Status: experiment; feedback and contributions welcome! Built to solve 3 problems I have with SQL as my primary iterative analysis language: 1. Adjusting queries/analysis takes a lot of boilerplate. Solve with queries that operate on the semantic layer, not tables. Also eliminates the need for CTEs. 2. Sources of truth change all the time. I hate updating reports to reference new tables. Also solved by the semantic layer, since data bindings can be updated without changing dashboards or queries. 3. Getting from SQL to visuals is too much work in many tools; make it as streamlined as possible. Surprise—solve with the semantic layer; add in more expressive typing to get better defaults; also use it to wire up automatic drilldowns/cross filtering. Supports: BigQuery, DuckDB, and Snowflake. Links [1] https://ift.tt/M6SlZk1 (language info) Git links: [Frontend] https://ift.tt/6mhjuYN [Language] https://ift.tt/ALXkT1r Previously: https://ift.tt/LvXxRIB (significant UX/feature reworks since) https://ift.tt/K63t4On https://ift.tt/QJj2xmS November 10, 2025, at 12:26AM

Commentary:
What makes Trilogy Studio interesting isn’t just that it’s “another SQL IDE”—it”’s an attempt to rethink how analysis is composed and reused at the code layer. Traditional SQL forces analysts into endless boilerplate: CTE chains, manual joins, and fragile references to ever-changing tables. Trilogy’s semantic layer is a bold idea because it shifts the unit of work from tables to concepts. That means queries can be written against business semantics rather than raw schema, and when sources of truth evolve, the analysis doesn’t break.

The other big win is bridging SQL and visualization. Most tools bolt visuals on top of queries, but Trilogy treats visualization as a first-class outcome of the language itself. By embedding expressive typing and semantics directly into the query, you get better defaults, automatic drilldowns, and cross-filtering without the usual friction. It’s not just about saving keystrokes—it’s about making iterative analysis faster, more composable, and less brittle.

The open-source angle matters too. Tools like Redash and Metabase are great, but they don’t fundamentally change the language. Trilogy is experimenting with syntax itself, which is a much harder but potentially more transformative path. If this experiment succeeds, it could inspire a new generation of analytic IDEs where SQL isn’t just a query language but a semantic modeling and visualization language.

In short: Trilogy Studio isn’t just solving analyst pain points—it’s probing whether SQL can evolve into something more expressive, resilient, and visual. That’s a conversation worth having, and contributions from the community could shape where it goes next.

---