Reference: European vehicle-data exchange

For a Dutch government implementation agency in the mobility sector, I work on modernising a European interface architecture for cross-border enforcement of traffic offences. Part of this is an API gateway built on Microsoft YARP: a consistent entry point for services with shared capabilities for routing, security, request/response transformation and observability.

Earlier work within the same ecosystem includes a National Access Point for processing and validating standardised vehicle information (IVI/XML) and electronic Certificates of Conformity (eCoC), and secure messaging via eDelivery/AS4(Domibus, P-Modes, certificates and encryption) for cross-border vehicle re-registration within the Once-Only Technical System (OOTS).

Security isn't a layer added afterwards but part of the architecture: certificate-based authentication, mTLS, Azure Application Gateway with Web Application Firewall, container scanning, and automated code analysis (SonarQube, Fortify) in the CI/CD pipeline.

Why this is relevant

  • BIO2 (Baseline Informatiebeveiliging Overheid 2) — the compliance framework Dutch government IT suppliers must demonstrably meet.
  • Cyberbeveiligingswet (the Dutch NIS2 implementation) — duty of care, incident reporting and registration obligations for critical-sector organisations.
  • NORA and European interoperability standards for interface architecture.
  • Procurement processes at Dutch public bodies, including screening (VOG, and where applicable a security clearance).

Working with public-sector clients

Neyon contracts on its own model agreement and delivers on a project basis, with a defined scope and delivery date — not as a stand-in for a vacancy. At peak load or unavailability, Neyon brings in a trusted partner, by agreement.

A public-sector question to discuss?

A no-obligation introduction call — a concrete answer, nothing more.

Plan an introduction call