Platform Overview
One platform core. Nine connected modules.
Every AERODX module shares the same customer data, identity model and permission structure. Add a module today, and it inherits the data, workflows and access rules already in place — no duplicate integrations, no re-entered data.
Architecture built for airline complexity
Airlines operate across reservation systems, ground handling tools, finance platforms, marketing stacks and customer-facing channels — often maintained by different vendors and teams. AERODX does not try to replace all of it. Instead, it provides a connected platform core that centralises customer identity and data, then exposes that data consistently to every module and integration.
The result is a system that can start small — a single module for a specific team — and expand into a full digital ecosystem without re-architecting the underlying data model.
Core Architecture Principles
What holds the ecosystem together
Centralised customer data
One customer record for contact details, preferences, consent, bookings and service history, shared across every module.
Shared identity and access
A single identity layer authenticates staff and passengers once, applying consistent permissions across the platform.
Modular architecture
Each module is a discrete, independently deployable capability that plugs into the same core — add or remove without disruption.
API-first connectivity
Every module and integration communicates through documented APIs, supporting both platform-native and third-party workflows.
Real-time or scheduled exchange
Data can sync in real time for operational workflows or on a scheduled basis for reporting and batch processes, depending on requirements.
Central reporting
Cross-module reporting draws from the same underlying data, avoiding conflicting numbers between commercial, service and operations teams.
Workflow automation
Tasks, approvals and notifications can be triggered automatically as records move through CRM, service and marketing workflows.
Multilingual by design
Interfaces, customer communications and content can be managed in multiple languages from the same platform instance.
Ecosystem Diagram
How the modules connect to the platform core
Each module reads from and writes to a shared customer and operational data layer, coordinated through role-based permissions and a central administration console.
The AERODX platform core coordinates identity, permissions and data exchange across all connected modules.
Administration & Governance
Configurable permissions, built for your organisation
Role-based administration lets IT and operations teams define exactly who can see and act on which data — by department, function or individual role. Custom fields, workflows and business rules can be configured to reflect how your airline actually operates, rather than forcing your teams into a fixed structure.
- Role-based access down to individual field level
- Custom fields and workflows per department
- Configurable approval and escalation rules
- Support for airline-specific business logic and custom development
Deployment
Cloud, or your approved infrastructure
AERODX is available as a cloud-hosted service for airlines that want to move quickly, and can also be deployed on approved private infrastructure where regulatory, data-residency or internal IT policy requires it. Either way, the platform integrates with the reservation systems, booking engines and internal tools you already operate.
- Cloud deployment with managed updates and monitoring
- Private or airline-approved infrastructure on request
- Integration with existing airline systems and data sources
- Scoped, project-based onboarding for each deployment
Platform FAQs
Common questions about the AERODX architecture
Do we need to implement every module at once?
No. AERODX is designed to be adopted module by module. Many airlines start with a single capability — such as the CRM or customer portal — and add further modules as priorities evolve. Every module connects to the same underlying platform core, so nothing needs to be rebuilt later.
Does AERODX replace our reservation system?
No. AERODX integrates with reservation systems such as Amadeus and other airline platforms through authorised APIs. It consolidates and presents that data for commercial, service and operational use, rather than replacing the systems of record.
Can AERODX be customised for our specific processes?
Yes. Beyond configurable permissions, fields and workflows, the AERODX team offers custom development for requirements that fall outside the standard modules, scoped as part of your project.
How is data kept secure across modules?
AERODX applies role-based access control, secure authentication and server-side validation across the platform, with audit logging available where supported. Deployment options include cloud and airline-approved private infrastructure.