Kernapplicaties and the pack around them¶

Municipal IT on the Disc is still remarkably concentrated at its centre. Centric and PinkRoccade Local Government remain the dominant suppliers of the municipal core applications used by most municipalities, particularly around burgerzaken and the administrative systems that sit closest to the BRP and the other national registrations. Centric’s burgerzaken platform, marketed today as Centric Burgerzaken though many practitioners still say Key2, and PinkRoccade’s equivalent back office together account for a substantial share of the market. Both vendors have modernised their product lines around APIs, SaaS and Common Ground integration rather than wholesale replacement.

PinkRoccade Local Government now operates within Total Specific Solutions, itself part of Visma. That acquisition reshaped the ownership tree without much changing the supplier landscape municipalities encounter day to day. Procurement documents written ten years apart often carry strikingly similar names.

Around those core systems sits a recognisable ecosystem. Decos JOIN and Visma Roxit commonly provide the zaakgericht werken layer that coordinates cases, documents and workflows across departmental systems, which is where the integrations increasingly accumulate. Vicrea remains a major supplier of geo information, BAG/BGT and object registration tooling. At the citizen-facing edge, suppliers such as Seneca, SIMgroep, Exxellence and CARE typically provide the websites, digital forms, portals, appointment systems, search and authentication entry points through which residents first meet the municipality.

This is the collection of suppliers that repeatedly turns up in procurement documents and architecture diagrams. The names recur because the integrations recur. The application landscape reads less as a set of isolated products than as a relatively stable ecosystem of specialist systems exchanging data through standard interfaces, proprietary connectors and locally accumulated customisations. Little of the risk lives inside a single application. It gathers at the seams between the core registries, the orchestration layer and the citizen-facing services.

The pack is arguably becoming less about applications than about integration hubs. Twenty years ago the interesting asset was the burgerzaken application itself. Today it is the APIs, message brokers, zaak and document APIs, identity federation, DigiD flows, Common Ground components and the dozens of point-to-point integrations wiring suppliers together. Vendors now advertise openness, API integration and Common Ground compatibility as primary selling points, a fair indicator of where the architecture has shifted.