Work in progress · Version 1.1, last updated 6 November 2026
Architecture

System context (C4 level 1)

Who uses padi.com and which systems it depends on.

System context

padi.com serves divers, prospective divers and dive professionals, and is maintained by PADI editors and translators. It relies on PADI-owned systems for identity, member data and dive-shop data, and on SaaS for translation, media, maps and monitoring.

Figure 3. C4 level 1. Dark blue: systems in this document. Grey: systems owned by PADI or third parties.
Figure 3. C4 level 1. Dark blue: systems in this document. Grey: systems owned by PADI or third parties.
External system Owner What padi.com uses it for Details
PADI identity (Cognito, auth gateway) PADI Sign-in, session refresh, sign-out across PADI sites MyPADI
PADI platform APIs PADI Certifications, eCards, eLearning, logbook, club status, product catalog Integration catalogue
PADI Travel PADI Travel Shop and course data for the finder; Travel pages proxied at the edge Finder and search
PADI member file PADI Which shops are current PADI members Finder and search
Crowdin SaaS (PADI account) Translation of content, labels and finder text Localisation
Acquia DAM SaaS (PADI account) Images and video padi.com and Drupal
Google Places, Mapbox SaaS Place lookups, maps Finder and search
Datadog SaaS Traces, metrics, logs, monitors Observability
TrustArc SaaS (PADI account) Cookie consent gating analytics and RUM Security
store.padi.com PADI (commercetools) Course purchase links and translated course names Integration catalogue