FAQ

Q&A on where the data comes from, updates, and why it runs in the browser

Where does the data come from?

It is based on open data published by the national government, municipalities, and public institutions. Queria reshapes it into an analysis-friendly form and serves it. Each table’s original distributor can be found under “data source” on its detail page.

Is it free to use?

Browsing, querying, and connecting to the public open data are free. See Pricing for details.

Can I use it commercially?

Yes, as long as you follow the license each original provider has set for its data. Before use, check the license on the table detail page and Attribution and licensing.

Why does it work with just a browser?

Because DuckDB WASM, the SQL engine, runs inside the browser and executes queries by reading the published data files directly. Data is never sent to a server; computation completes on your machine. See How it works for details.

Which SQL can I use?

DuckDB’s SQL dialect. The browser and connections from the DuckDB CLI or Python all access the same catalog and the same data, so queries can be shared as-is.

Can I use it outside the browser?

Yes. Queria’s data is published as DuckLake catalogs, so any environment that can connect to DuckDB (the DuckDB CLI, Python, Tableau, and so on) can reference it directly. See the connection guide.

How often is the data updated?

Each dataset follows its source data’s publication cycle. Whether and when a dataset updates varies by dataset.

The data looks wrong

Queria never rewrites the source data’s actual values. To tell whether a difference comes from cleansing or from the source data, check the transformation logic via “source code” and the primary sources via “data source” on the table detail page. See the data quality and cleansing policy for the preprocessing approach.

Next steps

• Introduction: get hands-on and try it
• Connection guide: connecting from external tools
• About Queria: project background