Astro developer in Amsterdam

Astro developer for Amsterdam companies. Dutch cookie law, AVG, iDEAL checkout, and EU accessibility rules applied to static marketing sites.

Astro developer

Migrate from WordPress to Astro in Amsterdam

Many businesses in Amsterdam run WordPress but face performance ceilings, security overhead, and rising hosting costs. Astro solves these with static HTML output, zero JavaScript by default, and edge deployment. I migrate existing WordPress sites to Astro with full SEO preservation, URL mapping, and 301 redirects.

  • PageSpeed 95-100

    Static HTML with zero JavaScript. Faster than any WordPress solution.

  • SEO-safe migration

    URL mapping, 301 redirects, Google rankings preserved.

  • Cloudflare Pages hosting

    Global CDN, free SSL, instant deployments. Hosting costs near zero.

I build Astro websites for Amsterdam companies whose public pages must survive regulator scrutiny: payment platforms publishing product and fee pages in Dutch and English, fintech teams explaining APIs to merchants, and scale-ups handing a repository to their first frontend hire after Techleap programmes or a funding round. Astro renders each route to static HTML at build time and loads JavaScript only where a component needs it, so cookie consent under the Telecommunicatiewet, checkout copy around iDEAL, and accessibility duties under Directive (EU) 2019/882 become template code a reviewer can read in Git before launch. I work alone, remotely and in writing from Gdynia in Poland, on Central European Time with Amsterdam.

#What does an Astro brief from Amsterdam usually combine?

An Amsterdam Astro brief usually joins four threads: Dutch and English routes that stay aligned, a tracking setup that respects article 11.7a of the Telecommunicatiewet and the Autoriteit Persoonsgegevens (AP) rules on valid cookie consent, checkout or signup flows that match what Dutch consumers expect at a bank redirect, and a codebase your own developer can extend. The sector decides which thread carries the most risk.

Payment and fintech teams around the Zuidas and the wider North Holland market care about accurate fee copy, status pages that stay up when APIs fail, and investor or merchant documentation that legal can diff in Git. Consumer brands that sell online in the Netherlands care about the iDEAL button, the privacy notice, and whether marketing cookies load only after a real choice. Scale-ups that grow through programmes such as Techleap often ask for speed and a clean handover rather than a heavyweight CMS on the public edge.

Your designer or agency supplies the visual design and wireframes. I turn approved layouts into Astro templates, content models and the Dutch hooks for consent, payments and accessibility.

#Why payment companies in Amsterdam still publish marketing sites as static HTML

Payment companies in Amsterdam still publish marketing sites as static HTML because the regulated product usually lives in dashboards, SDKs and APIs, while the public site is documentation, pricing explainers, status communication and trust content that must stay fast and easy to audit. Adyen describes its platform as a single place to run payments, manage data and offer financial products, and lists its global headquarters in Amsterdam with regional offices elsewhere (Adyen offices). Mollie, also headquartered in the Netherlands, states that it serves more than 350,000 businesses across Europe with payments and money management tools, grew from a launch roughly 22 years ago, and now employs around 1,000 people (Mollie about).

That profile shapes the brief. A merchant-facing page that misstates a fee, invents a certification, or loads trackers before consent creates reputational and supervisory risk long before a transaction fails. Astro fits the public layer around the live product:

  1. Each pricing tier, country footnote and FAQ answer lives in a typed content collection, so a missing field or broken link fails the build before it reaches production.
  2. The same entry feeds the HTML body, the FAQ block and JSON-LD, so the structured data matches the visible text.
  3. Status and incident posts can ship as markdown with fixed timestamps, giving communications a paper trail in Git.
  4. The deployed site is static files on a CDN, so a traffic spike after a product launch hits cached HTML instead of a CMS database.

The logged-in merchant portal or mobile SDK can stay on its own stack. Astro takes the marketing and documentation surface that regulators, journalists and procurement teams actually read.

#What does AMS-IX mean for page performance expectations in Amsterdam?

AMS-IX shapes performance expectations because Amsterdam hosts one of the world’s busiest internet exchange points, and buyers who work next to that infrastructure notice slow marketing sites. AMS-IX Amsterdam reports a peak traffic level of 15.822 Tb/s on its public site (AMS-IX facts and figures).

That context does not mean every SME must peer at AMS-IX. It does mean technical buyers are sensitive to unnecessary JavaScript, bloated tag managers and third-party fonts that add round trips. On an Astro site the default page ships HTML and CSS only; islands load frameworks such as React or Svelte for the pieces that need client state (Astro islands). A build step can fail when known tracker domains appear outside the consent island, which keeps marketing experiments from undoing the performance budget.

#What article 11.7a of the Telecommunicatiewet requires on cookie banners

Article 11.7a of the Telecommunicatiewet transposes the Dutch cookie rule: storing or accessing information on a user’s device through an electronic communications network is allowed only when the user receives clear and complete information, at least about the purposes, and has given consent, without prejudice to the Algemene verordening gegevensbescherming (wetten.overheid.nl, artikel 11.7a). The article also lists exceptions for communications that are strictly necessary to provide a requested service, and treats certain analytics and profiling use as personal data processing.

The Netherlands Authority for Consumers and Markets (ACM) enforces those cookie rules on businesses. ACM reported that it told the operators of the hundred most popular Dutch websites to fix cookie policies, and that many previously failed to inform visitors or obtain consent in a correct and clear way (ACM, online privacy campaign). ACM also notes that some sites still use cookie walls that deny access unless visitors accept tracking.

The AP explains what counts as valid consent for tracking cookies: information must appear before the choice; continuing to scroll is not consent; pre-ticked categories on a deeper layer are not allowed; and a cookie wall that blocks normal use of the site is not allowed (AP, cookies). When cookie use involves personal data complaints, visitors can contact the site owner first and then file a complaint with the AP.

A 2017 joint intervention on StemWijzer.nl illustrates the split. ACM and AP said the site placed advertising cookies without valid consent under Telecommunicatiewet article 11.7a, while political preference data made the case a personal data issue as well. StemWijzer.nl removed the advertising cookies; AP pressed for security improvements (ACM and AP on StemWijzer.nl).

On an Astro build I translate that split into build rules:

  • The base layout loads no third-party analytics, chat or advertising scripts.
  • A single consent island mounts optional tags only after an explicit accept or reject action with equal prominence.
  • The privacy notice and cookie text name the same processors as a typed configuration file in the repo.
  • A deploy step scans built HTML for tracker domains outside the island and fails when it finds one.

#How the AVG and Uitvoeringswet reach forms, newsletters and CRM hooks

In Dutch law the GDPR appears as the Algemene verordening gegevensbescherming (AVG). The Uitvoeringswet Algemene verordening gegevensbescherming (UAVG) implements it nationally and names the Autoriteit Persoonsgegevens as the supervisory authority referred to in article 51 of the GDPR (UAVG, artikel 6). The AP describes the GDPR on its site as the main privacy law that protects personal data (AP, basic GDPR).

For an Amsterdam marketing site the practical hooks sit in forms and integrations:

  • Demo request forms send personal data to a CRM or inbox. I list each processor, purpose and retention field in a typed config file that must match the privacy notice.
  • Newsletter signups store consent wording and a timestamp with the email address, because marketing to private individuals by electronic mail requires prior consent under Dutch consumer rules enforced by ACM in the online commerce space.
  • Job applications and partner intake forms receive the same treatment when they leave the static site for a third-party ATS or spreadsheet.

Astro does not remove your obligation to answer data subject requests, but it keeps the public attack surface small: no PHP admin on the edge, no plugin supply chain on the marketing domain. Your data protection officer still decides lawful basis and retention; I make the published site reflect that decision in components rather than in a one-off banner script.

#What changes for Dutch e-commerce accessibility from 28 June 2025?

Directive (EU) 2019/882 on accessibility requirements for products and services applies to e-commerce services provided to consumers after 28 June 2025, alongside other listed services such as banking services for consumers (EUR-Lex, Directive (EU) 2019/882). Member states must apply the directive from 28 June 2025. Recital 47 of the same directive aligns functional accessibility expectations with the perceivable, operable, understandable and robust principles used for public sector websites.

For a Dutch online shop or subscription service marketed from Amsterdam, that date matters on marketing templates, checkout flows hosted on the same domain, and self-service account pages linked from the shop. I build semantic headings, visible focus states, labelled forms and keyboard-friendly navigation into shared components, and run automated accessibility checks in continuous integration. Your counsel decides whether a specific micro-enterprise exception applies; the templates aim at the directive’s e-commerce scope unless you document otherwise.

#How iDEAL checkout copy fits a site that will show iDEAL | Wero

iDEAL remains the dominant online payment method in the Netherlands. Currence reported in April 2024 that 1.3 billion transactions run through iDEAL annually and that iDEAL accounts for 73% of Dutch online purchases (iDEAL news, April 2024). The same news archive states that from 2026 iDEAL will begin rebranding to iDEAL | Wero as the first step toward Wero, the European digital wallet, and that merchants will see the combined logo while familiar checkout behaviour continues during the transition.

The operator’s merchant guidance on the move to Wero explains phase one from Q1 2026: checkout keeps working, the PSP applies the new logo, and technical migration proceeds in the background (ideal.nl, Naar Wero). Earlier announcements on ideal.nl asked merchants to remove bank selection lists and use a single iDEAL button to the iDEAL Payment Page from 1 April 2025, with monitoring and enforcement after that date (iDEAL news, February 2025).

On an Astro storefront I keep payment method names, button labels and help text in one Dutch and one English string table. Checkout islands that embed a PSP widget still get reviewed so the visible label matches what Currence publishes for the current phase. When your PSP announces iDEAL | Wero assets, we update the string table and screenshot the staging checkout before DNS changes.

#What Techleap and Amsterdam scale-ups need from a handover

Techleap describes itself as a catalyst for Dutch tech talent, capital and knowledge, runs community programmes for founders, and hosts The Stack as an Amsterdam-based office for frontier AI companies (Techleap). Amsterdam scale-ups therefore often hire their first in-house frontend developer shortly after a funding round or accelerator cohort, and the repository must be readable without private lore.

I write for that hire:

  • TypeScript throughout, following Astro routing, content collections and islands as documented on docs.astro.build.
  • Dutch and English routes using Astro’s built-in internationalization patterns where you need both languages at launch (Astro i18n).
  • A README with commands to install, preview, add a page and trigger a deploy.
  • No hidden build step that only I understand.

Before handover I apply one test: a developer who has read the Astro documentation can add a Dutch page and its English sibling without calling me.

#How an Amsterdam Astro project runs from brief to launch

An Amsterdam project runs in five written stages. Communication stays on Central European Time working days; everything scope-related ends up in writing.

StageWhat you receiveWhat I need from your Amsterdam team
Brief reviewA free initial written estimate with scope, assumptions and open questionsCurrent site URL, launch languages, payment methods, target launch window, owner of design files
Architecture noteRoute map, content schemas, redirect list, inventory of third-party scripts and form endpointsConfirmation of slugs, CRM or ESP processors, consent categories your DPO uses
BuildStaging deploys from pull requests and a changelog in GitApproved designs and content, or clearly marked placeholders
Compliance passConsent island, tracker scan, iDEAL label review, accessibility checks on checkout templatesLegal texts from your counsel, privacy notice, PSP documentation for the current iDEAL phase
LaunchDNS checklist, redirect file, handover guideA named person for DNS and a go-live date

#Send an Amsterdam project brief

Send the brief through the contact form with your current site URL, the languages you need at launch, whether you sell to Dutch consumers online, which payment methods you offer, who supplies the design, and your target launch window. I reply on Central European Time working days with questions or a written scope at no charge for the initial review.

See also in Netherlands

Need this service: Astro developer in Amsterdam?

Describe your project by e-mail. I reply within 48 hours.

Describe your project

Explore other WordPress services and knowledge base