Web development · Municipalities & government

Custom municipality website development.

A custom municipality website that does more than act as a brochure: main website, digital counter with DigiD and eHerkenning login, e-forms, council information and public space reports, all in one coherent platform that fits your existing GEMMA architecture and doesn't lock you in to a single supplier. Built on Common Ground principles, BIO-compliant, and accessible to WCAG 2.1 AA.

Target groupMunicipalities & government
TypeMain site + counter + portal
ArchitectureCommon Ground · NLX
ComplianceBIO · GDPR · WCAG 2.1 AA
IntegrationsDigiD · eHerkenning · MijnOverheid
OwnershipCode owned by the municipality

What does building a municipality website involve?

A municipality website is long past being a static brochure. It is the digital counter of a public organisation: the channel where residents report a house move, request an extract, submit a permit application, report a broken streetlight, search council documents or object to a decision. Building a municipality website means making all of those functions, each with its own security and accessibility obligations, work together in a single platform that is recognisable to residents and manageable for the organisation.

We design and build these platforms to order. No standard CMS template in which every municipality gets stuck in the same way, and no single-vendor suite that turns every extension into a debate about extra costs. We work according to Common Ground, the VNG reference architecture in which data and functionality are separated and integrations run through standardised APIs, and we connect to the existing GEMMA building blocks your organisation already works with. That gives you the technical room to move with the times without having to migrate again every four years.

Our background is in custom software for municipalities: case management systems, e-form engines, integrations with basic registers, permit workflows and domain-specific applications. A municipality website is therefore not a brochure project for us but a front office on top of a serious process architecture. You notice that difference in every choice we make: in the information architecture, in how we design DigiD logins, in how we connect e-forms to your case management system and in the way we set up content management for your own editorial team.

Suitable for municipalities of any size, from the G4 with hundreds of e-forms to smaller municipalities that want an honest, accessible site without package lock-in. Also for provinces, water boards, regional environmental agencies and joint arrangements: the same architectural principles and compliance requirements, with different processes on top.

Common Ground
VNG architecture as the starting point: separated data and functionality, integrations via standard APIs
BIO & GDPR
Information security and privacy as a design requirement, not an afterthought
WCAG 2.1 AA
Accessibility in line with the Digital Accessibility Decree for government: testable and verified
Vendor-independent
Code owned by the municipality: no renegotiation for every new feature

When does a new municipality website make sense?

01
Expiring contract

Your current CMS supplier's contract is coming to an end

The licence for a large existing suite (BCT, PinkRoccade, Seneca, Tribe, GX or similar) is expiring, prices are rising, or the package no longer scales with your needs. Rather than locking yourself into a single supplier for another four years or more, this is the natural moment to move to a Common Ground set-up. Together we look at which components you really need to replace and which you can decouple and reuse, keeping the migration manageable.

02
Accessibility

Your accessibility statement no longer scores well enough

The Digital Accessibility Decree for government bodies requires WCAG 2.1 AA compliance on all municipal websites and apps. Many older sites run into reports with a large number of outstanding issues, especially on forms, PDFs and interactive components. A new website is then often cheaper and more honest than continuing to patch. We build accessibility in as a design requirement and have an independent audit carried out before the site goes live.

03
Digital counter

The counter is overflowing, and the website doesn't solve it

Residents have to go to the town hall for matters that could be handled online. E-forms exist, but they land with a civil servant instead of in the case management system. DigiD is integrated for some applications but not for others. The result: duplicate work, long turnaround times, dissatisfied residents. A well-designed digital counter relieves the customer contact centre without requiring extra custom work for every new service.

04
Compliance

A BIO audit or GDPR improvement plan calls for a new architecture

An audit by your CISO, a DPIA finding from the Data Protection Officer, or a report from the Netherlands Court of Audit or the Dutch Data Protection Authority can make a thorough overhaul of the website platform unavoidable. For structural GDPR and BIO issues, patching the old stack rarely helps. A newly built platform with a proper separation of data and presentation solves the problem at the root, and is a far easier answer to explain to regulators. See also our approach to compliant software.

What sets our municipal websites apart.

Difference 01

Common Ground as a principle, not a brochure

We work with the VNG reference architecture as our basis. Data and functionality are kept separate, integrations run through standard APIs (NLX, Haalcentraal), and case-oriented working is fully built in. That sounds abstract, but the effect is concrete: you are not tied to one supplier for one set of functions, and extensions become simpler rather than more expensive.

Difference 02

Builders of municipal software

We come from software development, not from an advertising agency. The team building your site is the same team that is used to working with custom municipal software, DigiD/eHerkenning integrations, case management systems and base registries. For us, the website is the front office on top of processes we understand, and you feel that difference in every choice we make.

Difference 03

Ownership stays with the municipality

The code lives in a repository belonging to your municipality, not in a closed supplier environment. Documentation is complete and in Dutch. If the supplier changes, whether that's us or a successor, someone else can take over without data or logic being held hostage. For public organisations that is not a marketing advantage but a basic requirement you can readily justify. Also read our information security policy.

The components of a municipal platform.

In practice, a municipal site is a collection of connected components. We build them as modules on a single platform, so you don't have to explain four different login environments to residents, while still being able to replace or extend components individually.

Main website (gemeente.nl)

The public information layer: governance, organisation, news, policy, regulations, contact details, opening hours. A headless CMS in which editors and chief editors publish themselves, with workflow and archive.

Digital counter & DigiD portal

The logged-in area where residents handle their affairs. DigiD integration, session management, authorisation checks, registration in the case management system and feedback to MijnOverheid.

E-forms platform

A forms engine that your editorial team manages themselves, from simple reports to multi-step applications with attachments, conditional logic, fields pre-filled automatically from basic registers and direct routing to the right case type.

My Municipality resident portal

A portal where residents can view their cases: ongoing cases, payment status, permits, reports and correspondence. Securely accessed via DigiD and synchronised with MijnOverheid and the case management system.

Public space reports

Quick and mobile: residents can submit a report with a photo and location, whether it's a broken streetlight, overhanging greenery or illegally dumped waste. It is routed straight to the right team, with feedback on every status update.

Permit applications

Application flows for events, tree felling, environmental permits and alterations to existing buildings. Integrated with DSO, BAG and, where needed, your own permit software, with guided pre-filled fields and a transparent indication of processing times.

Council information

Council calendar, meeting documents, executive board decisions, motions and amendments. Integrated with iBabs or an equivalent council information system, with detail pages that residents and the press can search in full.

Search & optional AI assistant

A proper search function across the whole site, plus an optional AI search layer for frequently asked questions, provided it stays within a responsible scope. Application classification and objection decisions remain human work; here, AI is only a guide.

Which public organisations do we work for?

Municipalities are the main context, but the architectural principles (Common Ground, BIO, WCAG 2.1 AA, code ownership) apply across the entire public sector.

G4 & G40

Large municipalities

Hundreds of e-forms, multiple case types and editors spread across departments. Decomposition is crucial: one main site with separate, self-contained modules in which teams work in parallel without getting in each other's way at release time.

G50 & mid-sized

Mid-sized municipalities

Often the sharpest trade-off between an off-the-shelf package and custom software. Our approach works well here because we build modularly: no more functionality than you need, and expandable later as the organisation grows.

Smaller municipalities

Smaller municipalities and joint arrangements

A tighter budget, a smaller editorial team and a need for a low-maintenance platform. We build a lighter variant with the same compliance foundation, and where it makes sense we work with neighbouring municipalities on shared infrastructure.

Provinces

Provinces

Policy information, subsidies and provincial council documents. Similar architectural principles, different processes, with specific integrations with provincial registers, environmental plan instruments and the Provinciaal Blad.

Water boards

Water boards

Tax assessments, notifications, water permits, flood defence communication. Their own levy systems, cooperation with BsGW and GBLT, their own election moments: everything calls for custom UX and integrations.

Partnerships

Joint arrangements

Joint arrangements for social services, ICT, taxes or the environment serve multiple municipalities with different house styles and processes, so a multi-tenant platform is often a better choice than a separate site for each partner.

Compliance: the framework we work within.

A municipal website operates within a denser regulatory framework than a corporate site. That is no side issue; it determines what the platform looks like on the inside.

The Baseline Informatiebeveiliging Overheid (BIO) is the shared standards framework for central government, municipalities, provinces and water authorities. It sets requirements for logging, authorisation management, vulnerability policy, data classification and incident handling. We design the platform with BIO in mind from the very first sketch: separate environments, audit logs at the right level, no unnecessary storage of personal data and a hardened hosting layer.

The GDPR overlaps with BIO but has its own emphases: purpose limitation, data minimisation, data subject rights and DPIAs for high-risk processing. For every new feature, we work with your data protection officer to check whether the existing DPIA is sufficient. We actively document which data is stored where, on what legal basis, and how a request for access or erasure is handled technically.

The Wet digitale overheid (Digital Government Act) and the Besluit digitale toegankelijkheid overheid (Digital Accessibility Decree) require WCAG 2.1 AA compliance and an accompanying accessibility statement. This is not a box to tick at the end but a design requirement that touches every component: colour contrast, focus management, semantic HTML, assistive-technology-friendly forms, screen reader support, alternative text. We commission an independent audit before go-live.

The AI Act applies to the platform as soon as you add AI components: a chatbot, a classifier for incoming reports, a pre-assessment AI for permits. We treat this as a separate decision chain: for each AI function, risk classification comes first, then registration in the Algoritmeregister (the Dutch algorithm register) where applicable, and only then implementation. For organisations that want to actively explore what AI can do here, see our AI workshop for municipalities.

Finally, we work with the VNG and Geonovum standards: GEMMA for architecture, NLX for integrations between organisations, Haalcentraal for querying basic registers (BRP, BAG, BRK, BGT), and the standard case and document types for case-based working.

Our guiding principles.

Principle 01

Accessibility is a design requirement

WCAG 2.1 AA built into every component, not a round of testing at the end. Keyboard navigation, screen reader support, contrast and reading level are part of the delivery, independently verified before the site goes live.

Principle 02

Headless and modular

The CMS and the presentation layer are separate. Content can also go via API to a mobile app, a resident portal or a new front end without migration. Building blocks connect via NLX to existing GEMMA systems.

Principle 03

Ownership and explainability

Code in a repository owned by the municipality, documentation in Dutch, transparent data flows. No black box, no lock-in. A far easier story for regulators and councillors than a closed supplier environment.

Not sure about a large project yet?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we make your idea tangible in a single day for €1,150, so you know whether further development is worth the investment. Decide to go ahead with the full build? Then we deduct the cost in full.

View OneDayBuild →

How a project works in practice.

We start with an intake. Around the table there are usually the communications or customer service adviser leading the project, the CIO or a representative from the CIO office, a representative from Information Services and, depending on scope, the Data Protection Officer and the CISO. The goal: which problem is most urgent right now (an outdated CMS, poor accessibility, e-forms that go nowhere, council information that cannot be searched) and what constraints apply to architecture, hosting, maintenance and integrations.

A discovery phase follows, in which we map the problem from the outside and the inside. Outside: who your residents are, which types of requests dominate, where people get stuck. Inside: which registers, case types, processes and integrations already exist. The end result is a functional and architectural design that we discuss with you, and with your audit function, before we start building in earnest.

The build phase runs iteratively in sprints. Every sprint delivers something tangible: a working module, an editorial environment, an integrated DigiD flow, a completed form. Code lives in a repository owned by the municipality, with an acceptance environment for editors and testers and a production environment that we only open once the accessibility and security audits have been approved.

Before go-live we commission an independent WCAG audit and, depending on scope and BIO impact, a penetration test and/or a DPIA update. The report goes to you and serves as the basis for the accessibility statement and the in-control statement. For projects with a larger security impact, see also our approach to ISO 27001-compliant software.

After go-live we either handle maintenance ourselves or hand over to your IT department or a third party. On handover we deliver full documentation, a runbook and a repeatable deployment pipeline. The code is yours.

Integrations we build as standard.

Integration 01

DigiD & eHerkenning

Authentication for citizens and organisations. Application, session management, fallback mechanisms and authorisations. We also handle the routing of your application to Logius if you need a first DigiD connection.

Integration 02

MijnOverheid & Berichtenbox

Status updates and messages to residents via MijnOverheid, respecting each citizen's preference (digital or still on paper). Integrated with your case management system so that status changes automatically go to the right channel.

Integration 03

Basic registrations via Haalcentraal

BRP, BAG, BRK, BGT: the standard queries run via Haalcentraal APIs. This gives you pre-filled fields in forms, automatic validation of address data and consistent data between front office and back office, without having to build your own copies of the basic registrations.

Integration 04

Case management & document management

Routing of e-forms to case types, status feedback and archive integration. We integrate with the common case management systems via standard APIs and build in handover moments that logically support your case handling.

Integration 05

iBabs / council information

The council calendar, agendas, documents, decision lists and motions are published automatically from your council information system to the site. Not as an embedded iframe but fully in your own UI, with a good search function and a permanently searchable archive.

Integration 06

Environment and Planning Act / DSO

Connection to the Digital System for the Environment and Planning Act (DSO) for applicable rules, permit checks and environmental plan queries. Preliminary-assessment and check flows on the website are supported with the right DSO connections.

Anti-lock-in: how we prevent vendor dependency.

For municipalities, vendor dependency is a serious and recurring pain point. A suite vendor that raises the licence fee every year without migration being realistic. A CMS whose data can only be retrieved through paid exports. A service-desk component that only works in combination with other components from the same vendor. It is not ill will; it is simply how things work commercially when the architecture is not open.

Our counter-strategy is deliberate and simple: no pre-selected vendor stack. We build on an open architecture with code ownership on your side, using proven open-source building blocks as the foundation and municipality-specific logic on top. For every integration with a commercial package (council information, permits, case management) we use standard APIs rather than vendor-specific interfaces, so replacing such a package does not mean rebuilding your website.

In practical terms, that also means you are not tied to us. The code sits in your repository, the documentation is complete and in Dutch, and if you change supplier, someone else can take over without your data or logic being held hostage. For the broader context, see also our web development approach and the custom offering for municipalities.

Frequently asked questions.

Do you build on an existing package (BCT, PinkRoccade, GX, Tribe) or completely from scratch?
Neither as dogma. We work on an open architecture with proven open-source components as the foundation (a serious headless CMS, a forms engine, a search platform) and build municipality-specific logic around them. No pre-selection of a single commercial suite, and no "everything from scratch" romanticism that would needlessly spend public funds. We choose the building blocks based on your existing landscape, your IT department and what your editorial team can comfortably manage. For inspiration on architecture choices, we benchmark against Common Ground reference implementations.
How do you handle the DigiD application with Logius?
We guide the application and provide the technical assessments Logius requires (security statement, pentest, BIO justification), but the application is formally submitted in the name of the municipality. eHerkenning works in much the same way. If you already have a connection, we migrate it as part of the project; if you don't, we schedule the process in parallel with the build phase.
Does this also work if we are a joint arrangement or a tax collection partnership?
Yes. Where it makes sense, we build multi-tenant: one platform serving several municipalities or partners, each with its own branding, processes and regulatory scope. For a joint arrangement in the social domain, an ICT partnership or a tax collection partnership, this saves each partner a considerable amount in management costs without losing their individuality. The same approach applies to independent implementing organisations (environmental agencies, regional implementation services (RUDs), public health services (GGDs)): the same architectural principle, with different domain-specific processes on top.
How long does your team take to launch a municipal website?
That depends heavily on scope, the volume of e-forms, the number of integrations and how ready your own editorial team and case management system are for the transition. A minimal version with a main website plus a set of frequently used forms can reach a working state in a few sprints; a full migration of a large G40 environment with hundreds of forms, council information and a citizen portal is a multi-sprint project with agreed interim milestones. We never work with a one-time big-bang delivery; we deliver iteratively in pieces that each add value on their own, so you can adjust course along the way.
What do you do with our existing content?
Content migration runs as a separate track alongside the build: inventory, clean-up (many old pages are removed or merged), automatic conversion where possible and manual curation where necessary. We pay close attention to 301 redirects so that search engine visibility and inbound links are not lost. PDFs from the archive remain available, but wherever possible we add an accessible HTML version alongside them.
How does this fit our GEMMA architecture?
For us, GEMMA is a guiding framework, not decoration. We build on the components your municipality already recognises: case-oriented working, NORA principles, KING/VNG standards where applicable. For integrations between organisations (municipality to SVB, the Tax Administration, BsGW, other municipalities) we use NLX as the routing standard. For querying base registries we use Haalcentraal APIs. No shadow architecture, no idiosyncratic front-end layer, just the standards the sector has agreed on itself.
What if we want to use AI: a chatbot, search assistant or classification?
Then we treat it as a separate decision chain. For every AI function: first the risk classification under the AI Act, then an assessment against the Algorithm Register, then a DPIA update, and only then implementation. Many public-sector AI applications fall into the high-risk category, and social-domain applications call for extra caution given the lessons of SyRI and the childcare benefits scandal. For organisations that want to explore the possibilities before building, we recommend our standalone AI workshop for municipalities as a starting point, though it is not a requirement for a website project.
Do you guarantee the accessibility statement?
We deliver a platform whose building blocks have been tested against WCAG 2.1 AA by an independent audit at handover. The accessibility statement itself is the municipality's responsibility; we provide the supporting evidence. We also make no secret of the fact that editorial content (PDFs, video subtitles, reading level) remains the bottleneck that your own organisation has to manage. We provide instructions and checklist components in the content management system to help, but the content discipline rests with your people. For ongoing audits and periodic re-testing, we work with the same external parties.
Can our own developers get involved?
Absolutely. For municipalities with their own development team or an ICT partnership, it is a healthy way to safeguard knowledge. We work openly, with code reviews your developers take part in, and with support during handover so that your people are comfortable with the platform in the first months after go-live. For smaller municipalities without their own team, we handle maintenance ourselves or hand over to a third party of your choice.
What if we want to switch to another supplier later?
You should be able to, and we work towards that. The code sits in your repository, the documentation is complete, and the architecture follows open standards. If you switch, we provide a clean handover to your new partner: no withholding of files, no artificial barriers, no migration fee. For public organisations this is a matter of principle, not a marketing claim. For more on our wider approach, see our web development practice and the information security policy.
What is the difference with your municipal software practice?
The software practice is broader: case management systems, integration platforms, and domain-specific applications such as a permits back office, a debt assistance tool or an execution system for the social domain. The website practice this page covers is the front-office layer of that: the place where residents meet the organisation. For municipalities that want to modernise both the front office and the related back office, we run both projects in parallel with the same architecture team. If all you need is a new website, this page is the place to start.

Talk to us about your municipality website.

An introductory half-hour call in which we go through where you stand now: an expiring contract, an accessibility statement with open issues, a service desk that is overflowing, or simply the wish to think through a Common Ground-based website. Afterwards, we send a concrete proposal with scope, architecture and sprint planning.

Reply within 1 working day
No-obligation conversation
Westerdoksdijk 599, Amsterdam
Share LinkedIn Email

Edit content