- Type
- not stated
- Format
- Tabular / structured — multiple exchange modes explicitly supported: IATA XML, CSV, TXT, and API/real-time services, warehoused for on-demand reporting
- Volume
- Modest in absolute records, exceptionally high in uniqueness: per coordinated airport, every slot pair across two annual seasons, every request and decision, every SSIM message, and every audit-trail change record. A major hub carries tens of thousands of slot pairs per season with multiple historical seasons retained, so a handful of large airports yields hundreds of thousands of decision-bearing rows per year. Aggregate platform volume is not published.
- Users
- N/A — B2B institutional SaaS sold to airport coordinators, airport operators and civil aviation authorities; seat base is small given a 2-person company, but each deployment carries a whole airport's coordinated traffic. The installed footprint is broader than headcount suggests: coordinators currently run a production webservice against SlotX, and a strategic partnership with a large South American airport-system provider (since 2017) extends reach across that region's airports.
- History
- not stated
- Update frequency
- not stated
- Growth
- Active rebuild on a long heritage — the company states SlotX was 'built from the ground up in 2025', following the launch of the new SlotX Webclient in September 2024, with site branding assets refreshed in Oct-Nov 2025. Milestones are explicit: system originally developed 1997, commercialisation from 2011, Data Collection Services from 2015, South American partnership 2017.
- Launched
- 1997 — SlotX was originally developed by COHOR, the French Airport Coordination Association, in 1997; Cohor Services commercialised it internationally from 2011, and the current platform generation was rebuilt in 2025 (web client launched Sept 2024).
- Delivery
- not stated
- Entity mapping
- not stated
- Sample
- not stated
- Point-in-time
- not stated
- Licence
- not stated