CASE STUDY

EuroHockey

One platform replacing manual coordination across 42 federations

DESIGN BUILD SECURITY MAINTENANCE

One platform replacing manual coordination across 42 federations

Who they are

EuroHockey governs field hockey across Europe: 42 member national associations and more than 40 competitions a year, coordinated from Brussels. In 2022 our team designed and built the new EuroHockey website and platform, spanning a WordPress brochure site, a Keystone back-end on AWS, and a headless Next.js front-end on Vercel.

eurohockey.org ↗

The challenge

A small central team ran that calendar through disconnected systems and manual processes. A single competition change meant separate updates across multiple tools, and member federations had no way to manage their own entries or officials.

Scope

DESIGN & BUILD · SECURITY · MAINTENANCE

The solution

We ran structured discovery workshops across every department, then built one data model across three connected layers: a public website fed live scores and streaming from a sports data feed; a member portal giving all 42 federations self-service over competition entry, development programmes and officials scheduling, with more than 20 role-based permission types; and an internal management platform for EuroHockey’s own team. Shipped in phases between 2022 and 2025, replacing three legacy tools with one two-way integration.

The impact

A competition change that once needed multiple manual updates now propagates from a single entry. All 42 federations manage their own entries and officials, and the central team runs the sport rather than the admin.

3 → 1

legacy tools (TMS, Altius, AWS) consolidated into a single system

20+

role-based permission types

Single source of truth

Maintaining the platform

EuroHockey is the lynchpin for European field hockey. The platform isn't a brochure, it's the operational system 42 federations depend on to enter competitions, schedule officials and publish results. One integrated stack now carries the whole operation, which is exactly why maintenance is the work that keeps it trustworthy. The ecosystem runs across four components, each maintained against a specific risk.

WordPress on WP Engine

During competition windows the public site carries live scores and streaming to a spectator audience, so downtime mid-tournament is a visible failure in front of the whole sport. We run monthly maintenance across WordPress core, theme and plugin updates on a managed staging-then-production cycle, so nothing ships untested. WP Engine handles server-level patching, backups and its own WAF; we own everything at the application layer. Let plugins lapse or core fall behind and known vulnerabilities go unpatched, opening the door to defacement, malware injection or a breach through to the member portal.

Keystone on AWS

The member portal holds personal data across 42 federations under more than 20 role-based permission types, which carries GDPR obligations and a real attack surface. We keep dependencies and the framework current, security-patch the Node runtime, and monitor the AWS infrastructure it sits on. A single unpatched entry point puts federation and officials data at risk.

Next.js on Vercel

As the governing body, EuroHockey sets the standard others follow, so a broken results feed or a failed portal undermines the authority the organisation exists to hold. We maintain framework and dependencies across both front-ends, while Vercel handles edge delivery, TLS and platform-level uptime.

The integration layer

Consolidating three legacy tools into one system is the win, but it also means data now flows through a single two-way integration. We monitor it so a competition change keeps propagating cleanly from one entry, keeping the single source of truth intact.