The archive · Developer & Business Tools · Product decision · 2022–2026
PRQL bets readable pipelines beat SQL, open-source and refusing all seed money
PRQL compiles pipeline-style queries to SQL; its Jan 2022 HN proposal drew 650 points, its 0.2 launch 378, and the repo shows 10.9k stars in 2026
PRQL
What the business is
PRQL ('Pipelined Relational Query Language') is an open-source project whose Rust compiler turns readable, linear query pipelines — with variables, functions, ranges and windowing — into SQL. Because it compiles to SQL, it works with any SQL database through language bindings and integrations such as Jupyter, VS Code, QStudio, ClickHouse and DuckDB.
How it started
In January 2022 PRQL's maintainers posted a design proposal on Hacker News with a prototype repo; the thread drew 650 points and 292 comments, the project reached #2 on HN for a day and gained roughly 2.5k GitHub stars in the following days (per the 0.2.0 release notes), turning a language sketch into a build sprint.
What happened
A worldwide group of contributors built the Rust compiler during evenings and weekends, evolved the language and added Python and Jupyter bindings. On 2022-06-27 they shipped 0.2.0 — 'the first version of PRQL you can use in your own projects' — via a Show HN that drew 378 points and 159 comments, announcing that PRQL would always be open-source with no commercial product despite outside interest in funding a seed round. Later years brought native PRQL support in ClickHouse and Databend, a DuckDB community extension, and VS Code and QStudio integrations.
How it ended up
PRQL is still live as of the 2026-09-05 snapshot: the repo shows 10.9k stars, 255 forks and 4,513 commits, and the README's July 2026 status says development has slowed while the team designs a new resolver to fix bugs and simplify the compiler. The project still has no commercial product and no company behind it.
Background
PRQL ('Pipelined Relational Query Language') is an open-source project whose Rust compiler turns readable, linear query pipelines — with variables, functions, ranges and windowing — into SQL. Because it compiles to SQL, it works with any SQL database through language bindings and integrations such as Jupyter, VS Code, QStudio, ClickHouse and DuckDB.
The bet, made public in January 2022 and repeated at the June 2022 0.2.0 release, was that developers and analysts would write analytics as pipelines if the language compiled to the SQL they already run — and that the project should stay open-source with no commercial product, despite outside interest in funding a seed round.
PRQL is still live as of the 2026-09-05 snapshot: the repository shows 10.9k stars, 255 forks and 4,513 commits, and the README's July 2026 status says development has slowed while the team designs a new resolver to fix bugs and simplify the compiler. It remains a project with no company behind it.
What has to be true
- Compiling to SQL removed the adoption tax: any SQL database, driver and tool keeps working while the language improves.
- A pipeline of transformations is how analysts already think, so PRQL examples read as intent rather than nested clauses.
- Building in public on Hacker News gave the design rapid, harsh feedback before the compiler got deep — the January thread shaped the 0.2 release.
- Refusing a commercial product neutralized the fear that a startup would abandon or lock a language after adoption.
What can be applied
When the thing you replace is a standard nobody trusts a vendor with, staying open-source and refusing seed money is the pitch itself — and HN threads double as user research
Aftermath
As of the 2026-09-05 GitHub snapshot PRQL is still maintained open-source: 10.9k stars, 255 forks and 4,513 commits, with native PRQL support in ClickHouse and Databend and community integrations for DuckDB, VS Code, Jupyter and QStudio. The README's July 2026 status reports the compiler still has bugs and missing features, and that development has slowed while maintainers decide how to build a new resolver that will simplify the code and resolve many bugs; it remains a project, not a company, with no commercial product.
Sources
spotted an error? The archive wants to know.
Your turn
You just read one. Describe what you are building, and see who is betting on the same thing.
Free account · 3 free questions · no card