Which open-data sources can you connect?
In practice, we work most with PDOK for geographic data, CBS StatLine and the CBS Open Data Portal for statistics, Open Spending for government expenditure, Eurostat and OECD.Stat for European and international comparisons, the EU Open Data Portal for everything the Commission publishes, INSPIRE for standardised spatial data, OpenStreetMap for map content and geocoding, Wikidata for linked open data, and sector-specific sources such as Luchtmeetnet, ENTSO-E, NDW, KvK Open Data, BAG and BRO. For research projects, also Common Crawl and the Internet Archive. If you have a specific source in mind that is not listed here, almost any open API with a licence can be integrated, and we will discuss that in the first conversation.
How stable are open-data APIs, really?
Honestly, it varies. PDOK, CBS Open Data and Eurostat are production-grade stable, with versioning and clear change logs. The EU Open Data Portal and some municipal open-data portals are less predictable: datasets can be moved, renamed or quietly withdrawn. That is why we always build an ingestion layer with validation, version pinning and our own snapshot archive. If a source API goes down temporarily or makes a major change, your app keeps running on the last valid snapshot while we adapt the pipeline.
What about personal data in open data?
Open data is not automatically free of personal data. An open BAG address combined with an open WOZ value and an open permits register can identify a specific household. CBS data at small-neighbourhood level can lead to individuals through statistical triangulation. For every project we run a GDPR pre-assessment: which combinations of sources could lead to re-identification, which aggregation thresholds are appropriate, and which disclosure controls we apply. For projects with serious privacy implications, we carry out a formal DPIA together with your data protection officer or privacy officer. For government data, the Open Government Act (Woo) and the re-use regime under the Open Data Directive are also relevant.
What is INSPIRE, and do we need to comply with it?
INSPIRE is a European directive that requires public-sector organisations to publish certain spatial datasets in a standardised format with standardised metadata. If you want to offer data yourself in addition to what you consume — for example, a citizen tool that enriches government data and exposes it again as an open service — INSPIRE may apply to you. We provide metadata in ISO 19115 format, GML or GeoJSON export, and an integration with the Nationaal GeoRegister (the Dutch national geo-register). INSPIRE usually doesn't apply to private and research parties, but interoperability with INSPIRE-compliant datasets is often still desirable. For the overlap with geospatial questions, see our page on
geographic apps.
Which licence terms apply to open data?
Most Dutch open data falls under CC0, CC-BY-4.0 or the Open Government Licence. CBS data is generally CC-BY with an attribution requirement, PDOK varies per dataset, and Eurostat has its own open-data licence that is comparable in practice. OpenStreetMap data falls under the ODbL, which carries share-alike obligations for derived datasets. We build attribution and licence notices directly into the app, with the correct source credit for each visualisation and, where the licence requires it, a downloadable data export with the accompanying licence text. That saves a lot of work later in legal reviews.
How do you make sure our app is accessibility-compliant?
We build in WCAG 2.2 AA from the design stage, not as an afterthought. For public-sector and citizen-facing apps this is mandatory under the Dutch Temporary Decree on Digital Accessibility of Government (Tijdelijk besluit digitale toegankelijkheid overheid) and, since 2025, under the European Accessibility Act (EAA), which also covers many private providers. Concrete measures include: alternative text presentations of visualisations (a map also gets a structured data-table mode), high contrast and dark mode, keyboard-only navigation, screen-reader-friendly charts via ARIA attributes, avoiding colour-only encoding, and captions for any video content. In the final sprint we run an audit with an automated tool plus a manual check with a screen reader.
Do you host the app, or do we do that ourselves?
Either works. For public-sector and research organisations we often host in a European cloud (Google Cloud Frankfurt, AWS Frankfurt, or a local provider). If you have your own cloud tenant, we deploy to your GCP, AWS or Azure environment. The codebase is the same; only the deployment target differs. You are not locked into our hosting, and handing over hosting is part of the final delivery.
Which tech stack do you usually use?
For the app: Flutter or React Native for cross-platform mobile, Next.js or Astro for web. For data: PostgreSQL with PostGIS, DuckDB on Parquet, and optionally Snowflake or BigQuery for heavy research workloads. For pipelines: Python with dbt and Airflow, or Dagster for more complex DAGs. For visualisations: Plotly, Observable Plot, ECharts or D3, and Mapbox GL or MapLibre for maps. We choose what fits your engineering capacity and source data, not what we happen to be used to.
Can you also build an internal BI tool on open data?
Yes, it is actually one of the most requested variants. Policy teams, communications departments, sales teams in the public sector and consultancies often want an internal tool that helps them quickly consult government data for quotes, policy advice or market analyses. We build it as a web app with SSO via your Azure AD or Google Workspace, a query builder on top of an internal data warehouse, and export functions to PowerPoint or Word. This type of project draws on our experience with
BI and dashboard tooling and can also remain purely internal, without a public-facing layer.
How do you handle data quality and outliers?
Open data always contains exceptions: a Eurostat series in which zero means "no data" rather than "zero", a PDOK layer with duplicate geometries after a dataset migration, a CBS table in which a revision appears only in the footnotes. We build automated validation checks: range, type, completeness and outlier detection. Findings are logged and flagged in the app, so end users can recognise a suspected outlier instead of presenting it uncritically. For research, we report issues back to the source owner.
How do you combine open data with AI or language models?
More often than before, clients want users to be able to query an open-data app in natural language, for example "show me Dutch municipalities where the housing stock is growing faster than average but the population is shrinking". We build this as an AI layer on top of a structured query layer: the language model translates the question into a validated query, the query runs on the open-data backend, and the result comes with an AI-generated explanation that the user can verify. For our approach and its responsible use, see our page on
AI development and our broader work on AI apps.
Do you work with our own developers or data analysts?
Yes, in open-data projects that is more the rule than the exception. Many organisations have a data team that handles the analysis side, while we build the app layer, ingestion pipelines and visualisation layer. We work in the same Git repository, align with your data schemas, and do pair programming where it speeds up knowledge transfer. By the end of the project, your own team can maintain the codebase entirely independently, with no lock-in to us as a supplier, because in open-data projects transparency and repeatability are where all the value lies.
What if we already have a data engineering platform?
Good news: then the step to an open-data app is shorter. We connect to your existing data platform (Snowflake, Databricks, BigQuery, your own Postgres cluster) and use the data already processed there as a starting point. We then don't need to rebuild the ingestion and transformation layer, or only partly; the focus shifts to the app and visualisation side. If you don't have a data platform yet, we often combine the project with the approach from our
data engineering platform practice.
Do you also build open-data apps for municipalities or government organisations?
Yes, it is actually an important part of our open-data practice. We work with municipalities, environmental services, provinces and implementing organisations that want to open up their data to citizens, council members or their own organisation. This calls for extra attention to INSPIRE compliance, audit logs, administrative-law traceability and integration with DigiD or eHerkenning for resident functionality. For the overlap with municipal software challenges, see our page on
software for municipalities.