Credits
Who makes this site
The code is open and the data belongs to the state. Here is who put in each part: the people who wrote the code, the public registries every figure comes from, and the free software it all runs on.
People
Eduardo Airaudo
Built the site and maintains it: the Compras Estatales open-data ingest, the anomaly detection, the investigations and the public API.
eduair94Nahuel Lopez
Regrouped the site's navigation into intent-based sections and built the local development bootstrap, which brings the dashboard up from scratch with no database.
NasvekL
Development is done with AI assistance: most commits in the repository say so in their history. Review, decisions and responsibility for what gets published are human.
Data sources
This site produces no data — it organises it. Every figure here traces back to one of these public registries.
- Compras Estatales (ACCE)
- The primary source. Every figure on this site comes from its OCDS open-data publication.
- Banco Central del Uruguay
- Historical exchange rates and the Unidad Indexada. They convert every amount to pesos of the month it happened and re-express it in today's pesos, which is what makes cross-currency and cross-year comparison possible.
- World Bank Open Data
- GDP, population and central-government expenditure, used to put the figures in context. It in turn republishes BCU national accounts, INE population and IMF statistics.
- Registro Industrial (DEI) — MIEM
- Industrial registry, cross-referenced by RUT against state suppliers.
- RUPE
- The state supplier registry, published as open data.
- geoBoundariesCC BY 4.0
- Uruguay's departmental boundaries, the geometry behind the department map.
Free software
Built on other people's work, published under licences that allow it.
- NuxtMIT
- VueMIT
- VuetifyMIT
- MongoDBSSPL
- MongooseMIT
- Material Design IconsApache 2.0
- LeafletBSD-2-Clause
- driver.jsMIT
- Archivo · Public Sans · IBM Plex MonoOFL 1.1
Contributing
Bug reports, data corrections and pull requests are welcome. If you find a wrongly-loaded expense, the most useful route is to report it to the agency that loaded it; if you find a bug on the site, it goes to the repository.