How it works

How Queria runs your queries on your side

Queria has no server that processes queries. The data is published as static files, and the DuckDB SQL engine runs on your side — inside the browser, or on your machine — reading those files directly. Keep this one fact in mind and the connection guides and limits become much easier to understand.

SQL runs on your side

In the browser, the WASM build of DuckDB processes queries on the spot; from the CLI or Python, the native build does. Your SQL statements and results are never sent to a server, so what you analyze stays private.

Even for large tables, only the parts a query needs are read from the data files — there is no need to download a whole table.

Having no compute servers is also what sustains free access.

All you need to connect is the catalog URL

Each dataset is published in DuckLake format under https://data.queria.io/<dataset>/, and the only thing you specify when connecting is the catalog URL.

Browser, CLI, and BI tools all reference the same catalog, so you get the same data and the same results everywhere, and the SQL you write can be shared as-is.

How data gets published

Source data (open data in CSV and other formats) is transformed and normalized into an analysis-friendly shape, then registered in the catalog along with its table definitions. For the preprocessing policy, see Data quality.