Team and authors

Biography

I have worked with software, data and web products for more than ten years. My background spans both product companies and consulting for small and medium businesses that needed automation, system integration, data sourcing and technical SEO. Over the past few years my focus has narrowed to open data: structured datasets published by public institutions, machine-readable, legally reusable, often hiding in plain sight under hostile interfaces.

The European Union is unusual. The legal framework that mandates open data is one of the most advanced in the world (the PSI Directive, the Open Data Directive of 2019, the Data Governance Act of 2022). The portals exist: EUR-Lex for legislation, CORDIS for research, the Joint Transparency Register for lobbying, Kohesio for cohesion funding, TED for tenders. The datasets are of good quality. And yet the average citizen, journalist or small business owner still cannot answer simple questions like "what EU funding has my region received in the past five years" or "which lobby organisations registered the largest meetings with the Commission last year" without spending an afternoon on six different websites.

eupublicdata.eu was born from that observation. It pulls every dataset I could find into a single SQLite database, builds cross-references between them, and renders one consistent interface in English on top. The intermediate cost — six scrapers, one schema, one render layer — is mine to pay so that the end-user does not have to.

Role on the project

I personally cover every layer of the site:

• I write and maintain the scrapers for each vertical (legislation, research, tenders, funds, grants, lobby);
• I choose which sources to aggregate and I map their native taxonomies onto the site schema;
• I write the editorial content visible on the site by hand (this page, the methodology page, the introductory blocks on each category hub, the deep-dive guides);
• I review the AI-assisted summaries that appear on the highest-traffic records (top legislation by impressions, flagship CORDIS grants, largest Kohesio projects) before they go to production;
• I handle error reports, takedown requests and GDPR enquiries;
• I monitor data quality through the public validator (/transparency/);
• I run the commercial side: Premium subscriptions, the relationship with Google AdSense for display advertising, and the API plan.

No employees, no co-founders, no investors. Every editorial and technical decision is mine. If you want to know who is responsible for a piece of content published here, the answer is simple: me.

Transparency on commercial relationships

To be unambiguous with readers: eupublicdata.eu is a revenue-generating activity. The revenue sources are public, disclosed, separated from editorial content.

• Google AdSense display advertising: the sponsored ads visible on site pages are served by Google. They only load after explicit consent to the profiling cookies banner (for users who do not accept, ads remain present but non-personalised, as required by GDPR). I do not choose which specific ads are shown.
• Optional Premium subscriptions: paid services (personalised alerts on tenders, watchlists for funding calls, API access) for users who want advanced features. The site remains free to browse for anyone who does not subscribe.

I do not receive commissions from tenders, from funding awards, from public bodies, or from auction sales. I have no affiliate relationships with consultants who sell services around EU tenders or grant applications. I do not sell collected data to third parties for marketing purposes.

Editorial principles

Four rules I have imposed on myself and to which I hold every page published here.

Institutional sources only. No data from blogs, forums or private commercial sites. Whenever you see a record on this site, there is a linked official source that you can verify yourself. If the link is missing, report it as a bug.

Transparency on AI use. Part of the technical content (scraper code) and the automatic summaries (the description_enriched field in the database) are produced with assistance from language models. I declare this explicitly on the methodology page. The editorial content you see on hub and information pages is written, reviewed and edited by hand.

No dark patterns, no hidden paywall. Browsing is open. No page asks you to register to read. No invasive pop-ups occluding content.

Fast error correction. When you find a mistake and report it, I fix it within seven working days.