Market Position and Product Profile

Radixx Res is the reservations and passenger-service core of the Radixx airline technology portfolio. For departure-control analysis, an important distinction is necessary:

• Radixx Res manages reservations, inventory, fares, passenger records, ticketless or hybrid commercial processing, distribution and ancillary services.
• Radixx Go is the associated departure-services platform used for check-in, baggage acceptance, boarding and airport passenger processing.

Radixx Res should therefore not be described as the DCS by itself. The marketable airline solution is usually an integrated Radixx environment in which Radixx Res supplies the Passenger Service System foundation and Radixx Go delivers departure control. This distinction is equivalent to separating the reservation core from airport-processing modules in other PSS portfolios.

Radixx was developed for low-cost, hybrid, regional and smaller scheduled airlines rather than primarily for global alliance carriers. Sabre acquired Radixx in October 2019 for approximately US$110 million, positioning the platform as Sabre’s offering for smaller, low-cost and budget-airline customers alongside the higher-tier SabreSonic platform.

The product occupies a market segment similar to:

• Navitaire New Skies
• Hitit Crane
• IBS iFly
• InteliSys amelia
• KIU
• AeroCRS
• Videcom VRS
• Bravo Avantik

Its strongest fit is generally found among airlines that require more capability than a basic regional reservation system but do not need, or cannot justify, the scale and cost of Amadeus Altéa or SabreSonic.

---

Vendor Overview

Item	Details
Product owner	Sabre Corporation
Original developer	Radixx International
Product family	Radixx airline retailing and passenger-service portfolio
Reservation platform	Radixx Res
Departure-control platform	Radixx Go
Primary airline market	Low-cost, regional, hybrid and smaller scheduled airlines
Secondary market	Leisure, charter and selected medium-sized carriers
Deployment model	Vendor-hosted managed platform
Standalone DCS positioning	Radixx Go may be integrated with the Radixx platform; external-system scope must be confirmed contractually
Principal competitors	Navitaire New Skies, Hitit Crane, IBS iFly and InteliSys amelia
Pricing	Not publicly disclosed

Sabre’s acquisition reflected its intention to strengthen its position among small, low-cost and budget airlines. Public reporting at the time described Radixx as a passenger-service technology supplier focused on that segment.

Radixx remains materially different from SabreSonic. SabreSonic is aimed more toward established medium and large network carriers, while Radixx provides a comparatively lighter commercial and operational environment for airlines with simpler distribution, partner and airport-processing requirements.

---

1. Radixx Product Structure

The Radixx portfolio has historically been organized around separate but related airline functions.

The principal products relevant to an airline PSS and DCS evaluation include:

• Radixx Res
• Radixx Go
• Radixx ezyCommerce
• Radixx Insight
• Distribution and agency interfaces
• Ancillary and payment integrations
• Airport and government-system interfaces

The simplified architecture is:

Sales and distribution channels
        │
        ├── Airline website
        ├── Mobile application
        ├── Contact centre
        ├── Airport sales
        ├── Travel agents
        └── External distribution
        │
        ▼
Radixx Res
        ├── Schedules
        ├── Inventory
        ├── Reservations
        ├── Fares
        ├── Passenger records
        ├── Payments
        └── Ancillary services
        │
        ▼
Radixx Go
        ├── Passenger check-in
        ├── Seat assignment
        ├── Baggage acceptance
        ├── Boarding-pass production
        ├── Boarding control
        └── Flight close-out
        │
        ▼
Airport, baggage, government and operational systems

Radixx Res and Radixx Go therefore perform different roles:

Product	Primary function
Radixx Res	Reservations, inventory, fares and passenger-service records
Radixx Go	Airport departure processing
Radixx ezyCommerce	Digital sales and booking interface
Radixx Insight	Reporting and business intelligence
Third-party systems	Load control, baggage reconciliation, WorldTracer, revenue accounting or other specialist functions where required

Public PSS directories classify Radixx as a hybrid travel-distribution and passenger-service platform rather than a traditional enterprise network-carrier host.

---

2. Target Airline Market

2.1 Low-Cost Carriers

Radixx is primarily associated with airlines that operate:

• Point-to-point networks
• Direct digital distribution
• Ticketless or simplified reservation models
• High ancillary revenue
• Standardized fleets
• Short- and medium-haul schedules
• Relatively limited alliance complexity
• High airport self-service adoption

For these carriers, Radixx Res can maintain reservations and passenger entitlements while Radixx Go handles airport processing without requiring the extensive ticket-document and alliance functionality of Altéa or SabreSonic.

Radixx competes directly with New Skies in this market. The difference is often one of scale, commercial terms, customer references and integration strategy rather than basic reservations or check-in functionality.

2.2 Regional Airlines

Regional airlines are another significant target.

Radixx can suit carriers that require:

• Scheduled reservations
• Internet sales
• Airport check-in
• Baggage acceptance
• Boarding
• Agency distribution
• Basic interline or codeshare capability
• Multi-airport operations
• Lower implementation overhead than enterprise PSS products

It may be particularly suitable for independent regional airlines that do not operate as tightly integrated feeders within a large global alliance.

2.3 Hybrid Airlines

A hybrid carrier combines low-cost commercial practices with some full-service functions.

Typical requirements include:

• Ancillary sales
• Electronic ticketing
• Travel-agent distribution
• Connecting itineraries
• Multiple fare families
• Premium seating
• Corporate accounts
• Codeshare
• Loyalty
• International government interfaces

Radixx is relevant to this segment, but the airline must assess whether its planned complexity remains within the platform’s practical range.

A carrier transitioning from a simple point-to-point model into a major network operation may eventually encounter greater requirements for:

• Alliance interoperability
• Complex interline ticketing
• Multi-party servicing
• Through check-in
• Through baggage
• Partner disruption recovery
• Multi-hub inventory control

Those requirements should be tested in detail before selection.

2.4 Charter and Leisure Airlines

Radixx may suit charter and leisure airlines requiring:

• Tour-operator allocations
• Group bookings
• Direct sales
• Seasonal schedules
• Ancillary services
• Airport passenger processing
• Simplified ticketing
• Flexible fare products

Its suitability depends on how much charter inventory, allotment management and tour-operator integration are included in the proposed implementation.

2.5 Large Network Airlines

Radixx is not normally positioned as the first choice for a large global network carrier.

Such airlines commonly require:

• Extensive alliance participation
• Hundreds of interline agreements
• Complex codeshare processing
• Multi-hub operations
• Multiple cabins and brands
• Sophisticated premium servicing
• Centralized disruption recovery
• Very high transaction peaks
• Large-scale partner data exchange

Altéa and SabreSonic have stronger established positions in this market tier. Radixx may still support a subsidiary, regional brand or low-cost unit within a larger airline group.

---

3. Radixx Res Reservations Foundation

Radixx Res provides the commercial and passenger-record foundation used by the departure environment.

Its expected functional scope includes:

• Schedule management
• Inventory control
• Flight availability
• Fare management
• Booking creation
• Passenger records
• Contact information
• Payment records
• Ancillary products
• Seat selection
• Baggage products
• Booking changes
• Cancellation
• Group bookings
• Agency bookings
• Distribution interfaces
• Customer servicing

As with other PSS products, reservation, inventory and passenger data must remain synchronized with departure control. General airline PSS architecture transfers passenger and booking information from the reservation environment into departure processing and returns check-in, no-show and boarded status after departure.

Where Radixx Res and Radixx Go are deployed together, that synchronization should be more direct than in an architecture combining unrelated reservation and DCS platforms.

The airline should nevertheless confirm:

• Whether both systems share a single passenger record
• How quickly reservation changes reach the DCS
• How ticket or payment status is updated
• How duplicate records are prevented
• How airport changes are returned to the reservation platform
• How outages affect synchronization
• Whether updates are event driven or batch based
• How historical passenger data is retained

---

4. Ticketless and Hybrid Processing

Radixx is historically associated with ticketless and hybrid airline models.

A ticketless environment relies primarily on the reservation and payment record as evidence of travel entitlement. This can reduce the operational complexity associated with:

• Electronic ticket coupons
• Exchanges
• Reissues
• Interline ticket documents
• Coupon-status control
• Traditional fare construction
• Revenue-document reconciliation

This model is useful for point-to-point LCCs.

A hybrid airline may additionally require:

• Electronic tickets
• GDS distribution
• Codeshare
• Interline
• Corporate travel
• Travel-agency servicing

Public descriptions of airline reservation systems identify hybrid PSS platforms as systems that may support ticketless operations together with electronic ticketing for codeshare and interline use.

The airline should determine exactly which model Radixx supports in the proposed configuration:

• Fully ticketless
• Electronic ticketing
• Hybrid ticketless and e-ticket
• GDS ticketing
• Interline electronic ticketing
• Electronic Miscellaneous Documents
• Third-party ticket database integration

This distinction materially affects both commercial distribution and departure processing.

---

5. Radixx Go Departure Control

Radixx Go is the airport-processing component most directly comparable with a conventional DCS.

Its likely operational scope includes:

• Passenger check-in
• Booking retrieval
• Seat assignment
• Boarding-pass issuance
• Baggage acceptance
• Bag-tag printing
• Boarding control
• Passenger-status management
• No-show handling
• Gate processing
• Flight close-out
• Manifest generation
• Government-data collection
• Self-service integration

The exact module catalogue is not comprehensively disclosed in current public Sabre material. Airlines should obtain the current Radixx Res and Radixx Go product specifications rather than relying on historical marketing documents.

---

6. Passenger Check-in

Radixx Go can support check-in through:

• Airport counters
• Airline websites
• Mobile applications
• Self-service kiosks
• Gate workstations
• Transfer desks
• Common-use airport environments

During check-in, the system may validate:

• Reservation status
• Passenger identity
• Payment status
• Flight eligibility
• Seat assignment
• Purchased baggage
• Ancillary services
• Travel documents
• Special Service Requests
• Check-in window
• Government clearance

The integration with Radixx Res allows the check-in process to use the current booking and ancillary record.

This is particularly useful for airlines selling:

• Checked bags
• Preferred seats
• Priority boarding
• Sports equipment
• Cabin baggage
• Meals
• Assistance
• Airport services

The agent can confirm whether the service was purchased and collect an additional charge where necessary.

---

7. Seat Management

Radixx Go should support operational seat assignment based on inventory and aircraft configuration supplied by Radixx Res or an integrated seat-management source.

Expected capabilities include:

• Preselected seat recognition
• Paid seat recognition
• Automatic seat allocation
• Airport seat assignment
• Seat changes
• Exit-row validation
• Preferred seating
• Family seating
• Group seating
• Operational blocks
• Special-needs seating
• Aircraft-change reseating

For an LCC, seat assignment is both an operational and commercial transaction. The DCS must preserve:

• The physical seat
• The purchased seat product
• The associated fee
• The passenger’s entitlement
• Any refund or replacement obligation

The airline should specifically test:

• Seat-map synchronization
• Aircraft substitutions
• Multi-cabin operation
• Paid-seat refund logic
• Partner-airline seat maps
• Group seating
• Exit-row restrictions
• Infant and accessibility rules

---

8. Baggage Acceptance

Radixx Go manages baggage at the passenger-acceptance stage.

Likely functions include:

• Checking purchased baggage allowance
• Recording bag count
• Recording bag weight
• Calculating excess baggage
• Accepting special baggage
• Printing bag tags
• Associating baggage with passengers
• Identifying destination and transfer points
• Sending data to baggage systems
• Supporting offload after passenger no-show

The system does not replace:

• A Baggage Reconciliation System
• A Baggage Handling System
• Hold-baggage screening
• RFID infrastructure
• Baggage sortation
• WorldTracer
• Airport baggage analytics

The functional division is:

Layer	Responsibility
Radixx Res	Commercial baggage entitlement
Radixx Go	Physical bag acceptance and tag-data creation
BRS	Passenger-to-bag and aircraft reconciliation
BHS	Physical baggage movement and sortation
WorldTracer or equivalent	Mishandled-baggage tracing
Airport screening	Security clearance

For airlines with connecting or interline baggage, the depth of baggage-message support must be verified.

---

9. Boarding-Pass Production

Radixx Go may issue:

• Printed boarding passes
• Kiosk boarding passes
• Mobile boarding passes
• Web boarding passes
• Reissued boarding passes
• Gate-issued boarding documents

The boarding document may contain:

• Passenger name
• Flight number
• Date
• Origin
• Destination
• Seat
• Boarding sequence
• Boarding group
• Barcode
• Gate
• Service indicators

The airline should confirm support for:

• IATA Bar Coded Boarding Pass standards
• Mobile wallet integration
• Home printing
• Common-use printers
• Partner-flight boarding passes
• Security indicators
• Document-check indicators
• Priority boarding

---

10. Boarding Control

Expected boarding functions include:

• Boarding-pass scanning
• Flight validation
• Passenger-status update
• Duplicate-scan detection
• Wrong-flight detection
• Boarding-group control
• Seat changes
• Standby acceptance
• Passenger offload
• Final boarded count
• Gate close
• Flight closure

This is a critical performance area for low-cost airlines because gate-processing delays can reduce aircraft utilization and disrupt short turnarounds.

Airlines should request measurable targets for:

• Boarding transaction latency
• Simultaneous scanner use
• Gate workstation availability
• Offline boarding
• Recovery from scanner failure
• Passenger-list synchronization
• Final-count accuracy

---

11. Flight Close-out

Radixx Go can support finalization of passenger-processing data after boarding.

Close-out activities may include:

• Confirming boarded passengers
• Identifying no-shows
• Offloading checked-in passengers
• Triggering baggage-offload requirements
• Finalizing passenger counts
• Closing boarding
• Updating flight status
• Producing passenger manifests
• Sending data to load control
• Returning status to Radixx Res
• Transmitting operational messages

The system should be assessed separately from the airline’s weight-and-balance platform.

A DCS can close passenger processing without necessarily calculating:

• Aircraft centre of gravity
• Trim
• Compartment distribution
• Maximum allowable weights
• Load sheet
• Last-minute changes

---

12. Load Control and Weight and Balance

Radixx Res is not principally marketed as a load-control product, and Radixx Go should not automatically be assumed to include a complete certified weight-and-balance system.

An airline may require integration with:

• A third-party load-control platform
• A ground-handler load-control system
• A centralized load-control service
• A separate Sabre or airline operations platform
• An internally developed system

The DCS can provide:

• Passenger totals
• Passenger categories
• Boarded counts
• Bag totals
• Special loads
• No-show and offload information

The load-control system may then calculate:

• Dry operating weight
• Zero fuel weight
• Take-off weight
• Landing weight
• Centre of gravity
• Trim
• Compartment distribution
• Load instructions
• Last-minute changes
• Final load sheet

The airline should ask:

• Is weight and balance native to the proposed Radixx solution?
• Which third-party platforms are certified?
• Is Centralized Load Control supported?
• How are passenger and bag figures transmitted?
• How are last-minute changes returned?
• Which aircraft types are already configured?
• Is ACARS load-sheet delivery supported?
• Are LDM, CPM and related messages generated?

Until contract documentation confirms otherwise, Radixx should be treated as requiring a separate load-control assessment.

---

13. Distribution and Digital Sales

Radixx Res is designed to support multiple sales channels.

Potential channels include:

• Airline website
• Mobile application
• Contact centre
• Airport office
• Travel-agent portal
• Online travel agency
• GDS
• Direct API
• Tour operator
• Corporate booking channel

The system’s low-cost and hybrid positioning makes direct distribution strategically important.

Key functions may include:

• Fare search
• Booking
• Payment
• Ancillary sales
• Seat selection
• Baggage purchase
• Booking changes
• Customer notification
• Check-in
• Boarding-pass delivery

The airline should confirm whether digital interfaces are delivered through Radixx ezyCommerce, airline-developed applications or third-party platforms.

---

14. Ancillary Revenue

Ancillary processing is one of the product’s strongest likely use cases.

Potential ancillary products include:

• Checked baggage
• Cabin baggage
• Preferred seats
• Extra-legroom seats
• Priority boarding
• Meals
• Lounge access
• Sports equipment
• Pets
• Change flexibility
• Travel insurance
• Ground transport
• Fast-track security
• Airport services

The critical operational requirement is that ancillaries sold in Radixx Res remain visible and enforceable in Radixx Go.

Examples include:

• A prepaid bag
• A purchased exit-row seat
• Priority boarding
• A sports-equipment allowance
• Additional cabin baggage
• Airport check-in fee exemption

This integrated commercial-operational view is essential for LCC and hybrid carriers.

---

15. Interline and Codeshare

Interline and codeshare capability is one of the principal areas requiring detailed due diligence.

Radixx may support airline partnerships, but public evidence does not establish that it matches the alliance and interline depth of Altéa or SabreSonic.

The airline should test:

• Marketing-carrier codeshare
• Operating-carrier codeshare
• Free-flow codeshare
• Block-space codeshare
• Interline electronic ticketing
• Through check-in
• Through baggage
• Onward boarding-pass issuance
• Partner seat maps
• Partner ancillaries
• Frequent-flyer recognition
• Disruption rebooking
• Passenger transfer messages
• Separate-ticket handling

A public historical customer list has associated Radixx with airlines including Africa World Airlines, Air Rarotonga, Air Transat, Federal Air and several smaller regional carriers, but such lists are not reliable evidence of current product use or exact module deployment.

A proper implementation directory should distinguish:

• Confirmed current Radixx Res customer
• Confirmed Radixx Go customer
• Historical customer
• Announced migration
• Former customer
• Radixx customer with unspecified product scope

Sabre does not publicly provide a complete current module-level customer directory.

---

16. Airport Common-Use Integration

Radixx Go must operate through both airline-dedicated and common-use airport environments.

Relevant technologies include:

• Common Use Passenger Processing Systems
• Common Use Terminal Equipment
• Common Use Self Service
• Dedicated airline workstations
• Boarding-gate devices
• Kiosks
• Self bag-drop
• Mobile-agent devices

Likely hardware interfaces include:

• Passport readers
• Boarding-pass printers
• Baggage-tag printers
• Barcode scanners
• Gate readers
• Weighing scales
• Kiosks
• Self bag-drop units
• Biometric devices

The common-use provider may be:

• SITA
• Collins Aerospace
• Amadeus
• Materna IPS
• ICM
• Another airport supplier

Radixx and the airport provider must certify:

• Workstation operation
• Printer formats
• Scanner input
• Passport-reader mapping
• Bag-tag generation
• Gate updates
• Scale integration
• Offline behavior

Sabre does not publicly publish a complete current Radixx Go CUPPS and device-certification matrix. Airlines should require one during procurement.

---

17. Government and Travel-Document Interfaces

International airlines using Radixx require connectivity with:

• Advance Passenger Information
• Interactive Advance Passenger Information
• Passenger Name Record reporting
• Immigration
• Customs
• Security watchlists
• No-board instructions
• Entry authorization
• Visa validation
• Travel-document databases

The proposed solution should support:

• Passport capture
• Document validation
• Government transmission
• Interactive clearance
• Response processing
• Boarding inhibition
• Audit logging
• Data correction
• Data retention
• Privacy controls

Government support must be evaluated by route and jurisdiction. A broad claim of API support does not prove that every national border interface is available.

---

18. APIs and Integration

A modern Radixx deployment may integrate with:

• Website
• Mobile application
• Payment gateway
• Fraud system
• Loyalty
• Customer relationship management
• Revenue management
• Revenue accounting
• Operations control
• Crew systems
• Baggage systems
• Data warehouse
• Analytics
• Government systems
• Travel agencies
• Distribution partners

Possible technologies may include:

• REST
• SOAP
• XML
• JSON
• Message queues
• Batch files
• Type B messaging
• EDIFACT
• Web services
• Event notifications

Sabre does not publicly disclose a complete current Radixx API catalogue.

The airline should request:

• Full API inventory
• Read and write scope
• Authentication method
• Rate limits
• Sandbox access
• Versioning
• Deprecation policy
• Webhook or event support
• Bulk-data extraction
• Historical data access
• Error-handling model
• Commercial API charges
• Availability commitments

This is particularly important because older PSS platforms may expose service-oriented interfaces without being fully cloud native or event driven.

---

19. Hosting and Deployment

Radixx is typically positioned as a vendor-hosted managed airline platform.

Deployment characteristic	Radixx position
Vendor hosted	Yes
Managed service	Yes
SaaS-style model	Generally
Local airline core hosting	Not the normal positioning
Local airport components	Yes
Multi-airport deployment	Yes
Common-use access	Expected
Hybrid integration	Yes
Cloud-native status	Must be technically validated

The production environment remains hybrid because:

• The reservation and DCS core are centrally hosted.
• Airport workstations and devices are local.
• Government systems are external.
• Baggage and operational platforms may be separately hosted.
• Airline applications may run in private or public cloud environments.

Airlines should request:

• Hosting location
• Cloud provider
• Data residency
• Tenant isolation
• Encryption
• Backup policy
• Disaster-recovery region
• Recovery Time Objective
• Recovery Point Objective
• Availability SLA
• Maintenance windows
• DDoS protection
• Exit-data provisions

Public sources do not disclose sufficient detail to classify the current Radixx architecture conclusively as cloud native, microservices based or containerized.

---

20. Security and Resilience

Radixx is mission-critical because an outage may affect:

• Reservations
• Sales
• Payments
• Check-in
• Baggage acceptance
• Boarding
• Flight closure
• Passenger manifests
• Government reporting

Expected controls include:

• High availability
• Geographic redundancy
• Encryption
• Identity and access management
• Privileged-user controls
• Multi-factor authentication
• Audit logging
• Security monitoring
• Vulnerability management
• Backup
• Disaster recovery
• Incident response
• Change control
• Business continuity

The airline should verify:

• ISO certification scope
• SOC reporting
• PCI DSS responsibility
• GDPR controls
• Penetration testing
• Subprocessor arrangements
• Breach notification
• Security-event retention
• Administrator auditability
• DR test frequency
• Availability remedies

Airport fallback procedures remain necessary for:

• Host outage
• Network failure
• Common-use failure
• Printer failure
• Scanner failure
• Government-system outage
• Payment-system outage
• Baggage-interface failure

---

21. Scalability

Radixx was acquired specifically to extend Sabre’s presence among smaller and budget airlines rather than to replace SabreSonic at the top enterprise tier.

This does not mean the product is limited to very small operators. It has historically been associated with scheduled carriers operating multi-airport and international services. However, current public sources do not disclose:

• Maximum passengers per year
• Flights per day
• Concurrent agents
• Booking transactions per second
• Check-ins per second
• Boarding scans per second
• API throughput
• Bag-message capacity

Airlines should request proof based on comparable production customers.

Relevant performance tests include:

• Promotional booking peaks
• Mobile check-in peaks
• Simultaneous airport check-in
• Boarding latency
• Schedule-change processing
• Mass cancellation
• Passenger reaccommodation
• Data extraction
• API bursts
• Host recovery

A medium or fast-growing airline should not assume that historical customer size guarantees future scalability.

---

22. Known Airline Customers

Public historical listings have associated Radixx with airlines such as:

Africa

• Africa World Airlines
• Federal Air

Asia-Pacific

• Air Rarotonga

North America and Caribbean

• Air Turks & Caicos

Other historical references

• Air Transat
• AeroCon
• Eznis

These names appear in public reservation-system directories, but such sources may be outdated and do not establish current use of Radixx Res, Radixx Go or another Radixx product.

Sabre does not publish a sufficiently detailed current list showing:

• Current customer
• Product modules
• Implementation date
• Migration status
• Passenger volumes
• Airport count
• Contract duration

Accordingly, customer references should be verified individually through airline announcements, Sabre case studies or procurement records before publication as current deployments.

---

23. Pricing

Sabre does not publish standard Radixx Res or Radixx Go prices.

The commercial model may include:

• Per-passenger fees
• Per-segment fees
• Booking transaction fees
• Minimum annual commitment
• Implementation
• Data migration
• Airport activation
• Common-use certification
• Digital-channel integration
• API access
• Payment integration
• Government interfaces
• Training
• Support
• Hosting
• Customization
• Professional services
• Change requests

Indicative Cost Position

Cost category	Likely position
Core PSS implementation	Medium
DCS implementation	Medium
Airport deployment	Medium
Digital integration	Medium
Interline customization	Medium to high
Training	Medium
Hosting	Included or separately priced in managed model
Small-airline affordability	Better than Altéa or SabreSonic
Large-airline suitability	Conditional
Switching cost	High

These are comparative market estimates, not disclosed Sabre prices.

Radixx would generally be expected to cost less than SabreSonic for a smaller carrier, but it should not be treated as an entry-level booking application. A multi-country airline with many stations and integrations may still face substantial implementation and operating cost.

---

24. Typical Implementation Timeline

Indicative planning ranges are:

Airline profile	Estimated implementation
Start-up airline	4–9 months
Small existing carrier	6–12 months
Regional airline	9–15 months
Medium LCC or hybrid carrier	12–20 months
Complex multi-country carrier	15–24 months
PSS and DCS replacement with extensive interline	18–30 months

These are industry estimates, not Sabre commitments.

Timeline factors include:

• Existing PSS
• Data migration
• Number of airports
• Common-use certification
• Government interfaces
• Digital channels
• Payment providers
• GDS distribution
• Interline and codeshare
• Loyalty
• Load control
• Baggage systems
• Training
• Cutover strategy

A start-up is faster because it has no historical reservations or active passenger records to migrate.

---

25. Principal Advantages

Appropriate Mid-Market Positioning

Radixx targets airlines that need an integrated PSS and DCS but do not require the full cost and complexity of SabreSonic.

Strong LCC and Regional Fit

Its reservation and departure model aligns with direct sales, ancillaries and simplified airport processing.

Integrated Radixx Res and Radixx Go Environment

Reservations and departure services can operate within one product family.

Sabre Ownership

Sabre provides access to a larger corporate, distribution and airline-technology ecosystem than Radixx had as an independent vendor.

Ancillary-Revenue Support

The platform is suitable for paid baggage, seating, priority boarding and other optional products.

Flexible Airline Models

It can serve ticketless, hybrid and selected electronic-ticketing environments.

Lower Organizational Burden

Implementation should generally be less complex than Altéa or SabreSonic for a standard regional or low-cost carrier.

---

26. Principal Weaknesses

Product Naming Confusion

Radixx Res is often incorrectly described as the DCS. Radixx Go is the relevant departure-services product. Procurement scope must be explicit.

Smaller Proven Enterprise Footprint

Radixx has less visible evidence among large alliance and multi-hub airlines than Altéa or SabreSonic.

Limited Public Documentation

Current module specifications, APIs, architecture, performance limits and certification matrices are not broadly public.

Customer List Uncertainty

Available public customer directories are often historical and do not identify exact current product usage.

Interline Depth Requires Validation

Complex alliance, through-check and partner-airline scenarios should not be assumed from general PSS claims.

Load Control May Be External

A complete weight-and-balance solution may require a separate supplier.

Potential Product-Roadmap Risk

Because Sabre owns both Radixx and SabreSonic, airlines should seek contractual clarity on Radixx investment, support horizons and migration strategy.

Vendor Dependency

Combining reservation, distribution and departure processing creates significant switching cost.

---

27. Radixx Versus Navitaire New Skies

Criterion	Radixx	Navitaire New Skies
Parent company	Sabre	Amadeus
Primary market	Regional, LCC and hybrid	LCC and hybrid
Reservation core	Radixx Res	New Skies
Departure control	Radixx Go	Integrated New Skies departure functions
Large-LCC market evidence	Moderate	Stronger
Regional-airline fit	Strong	Strong
Ancillary capability	Strong	Strong
Ticketless heritage	Strong	Strong
Interline complexity	Must be validated	More mature but still configuration dependent
Cost position	Mid-market	Enterprise LCC tier
Best fit	Small-medium LCC or regional airline	Medium-large LCC or hybrid

New Skies generally has stronger visibility among major global LCCs. Radixx may offer a more proportionate fit for smaller and medium carriers.

---

28. Radixx Versus Hitit Crane

Criterion	Radixx	Hitit Crane
Parent/vendor	Sabre	Hitit
Core market	Regional, LCC, hybrid	Regional, LCC, hybrid and medium full service
Standalone DCS	Scope must be confirmed	Explicitly supported
Integrated weight and balance	Not clearly central	Crane Weight & Balance available
Ancillary support	Strong	Strong
Full-service positioning	More limited	Stronger
Vendor scale	Backed by Sabre	Independent specialist
Global partner community	Sabre ecosystem advantage	Smaller but growing
Technical transparency	Limited	Somewhat more published product detail
Best fit	Regional and LCC	Regional, hybrid and medium national carrier

Hitit has the clearer publicly documented standalone DCS and load-control proposition. Radixx benefits from Sabre’s corporate ecosystem.

---

29. Radixx Versus SabreSonic

Criterion	Radixx	SabreSonic
Primary segment	Small-medium regional and low-cost airlines	Medium-large network airlines
Complexity	Medium	High
Interline and alliance depth	Conditional	Strong
Implementation	Faster and lighter	Longer and more complex
Cost	Lower tier	Enterprise
Multi-hub network fit	Limited to conditional	Strong
Ancillary-led LCC fit	Strong	Possible but potentially excessive
Best use	Regional, LCC, hybrid	Network, alliance and flag carrier

Sabre’s ownership of both platforms allows it to address different airline tiers. It does not make the products interchangeable.

---

30. Radixx Versus IBS iFly

IBS iFly is generally positioned as a more modern, modular and cloud-oriented PSS for regional, hybrid and full-service airlines.

Radixx may have advantages in:

• Established low-cost operating models
• Sabre ecosystem integration
• Commercial familiarity among smaller airlines
• Ancillary-led processing

IBS may be more attractive where the airline prioritizes:

• Modern cloud architecture
• Broader full-service capability
• Modularity
• Open integration
• A longer-term transition toward network operations

The decision should be based on production references and architecture evidence rather than vendor claims alone.

---

31. Best-Fit Recommendations

Strong Fit

Radixx should be shortlisted by:

• Small and medium low-cost carriers
• Regional scheduled airlines
• Hybrid carriers
• Leisure airlines
• Charter-scheduled hybrids
• Airlines prioritizing direct digital distribution
• Airlines with substantial ancillary revenue
• Carriers seeking a Sabre-backed mid-market PSS

Conditional Fit

It may suit:

• Medium national carriers
• Growing international airlines
• Airlines introducing codeshare
• Airline groups operating a low-cost subsidiary
• Carriers migrating from a basic regional PSS

These airlines should verify interline, performance and partner-processing requirements carefully.

Weak Fit

Radixx is less likely to be appropriate for:

• Large global alliance airlines
• Highly complex multi-hub flag carriers
• Cargo-only airlines
• Government operators requiring extensive bespoke control
• Airlines requiring a complete on-premise PSS
• Carriers demanding a fully integrated advanced load-control suite
• Very small operators needing only basic booking and check-in

---

32. Procurement Questions

An airline evaluating Radixx should require precise answers to the following.

Product identity

• Is the proposed product Radixx Res, Radixx Go or both?
• Which DCS functions are native to Radixx Go?
• Which functions require third-party systems?
• Is Radixx Go available independently of Radixx Res?
• What is Sabre’s long-term Radixx product roadmap?

Departure control

• Which check-in channels are included?
• Is mobile check-in included?
• Is kiosk software included?
• Is self bag drop supported?
• Is offline airport processing available?
• What is the gate-transaction SLA?

Load control

• Is weight and balance included?
• Which external load-control systems are certified?
• How are passenger and baggage totals exchanged?
• Are LDM, CPM and MVT messages supported?
• Is ACARS load-sheet delivery available?

Interline

• Which airlines currently use through check-in?
• Is interline e-ticketing supported?
• Are partner boarding passes supported?
• Is through baggage supported?
• How are partner ancillaries handled?
• How are disrupted passengers transferred?

Integration

• Which APIs are available?
• Which transactions are writable?
• Are events or webhooks supported?
• What are API limits?
• How is historical data exported?
• Are API calls separately charged?

Hosting and resilience

• Where is the platform hosted?
• Is it cloud native or cloud hosted?
• What are the RTO and RPO?
• What is the contractual availability?
• How is tenant isolation implemented?
• What fallback mode is available at airports?

Commercial terms

• Is pricing per passenger, booking, segment or departure?
• What minimum annual commitment applies?
• Are airport activations charged?
• Are interfaces separately priced?
• What exit-data support is included?
• What migration support is provided if Sabre changes the product roadmap?

---

33. Overall Assessment

Radixx Res is a mid-market passenger-service platform designed primarily for low-cost, regional and hybrid airlines. In DCS terms, it must be evaluated together with Radixx Go, which provides the departure-processing layer.

Its principal value lies in providing:

• Integrated reservations and airport processing
• A ticketless or hybrid operating model
• Ancillary-revenue support
• Direct distribution
• A proportionate alternative to enterprise PSS platforms
• Access to Sabre’s wider airline technology ecosystem

Its principal risks are:

• Limited public technical documentation
• Uncertainty around current module-level customer deployments
• Need to verify complex interline capability
• Possible dependence on external load control
• Product-roadmap questions following Sabre’s acquisition
• Lower evidence of top-tier network-carrier use

For a small or medium LCC, regional carrier or hybrid airline, Radixx can be a credible alternative to New Skies, Hitit Crane and IBS iFly. For a major alliance or global network airline, SabreSonic or Amadeus Altéa will usually offer a stronger and more proven functional foundation.

The central procurement question is not whether Radixx can support reservations and check-in. It is whether the airline’s five- to ten-year growth plan will remain within Radixx’s natural regional and low-cost operating envelope.

Where that answer is yes, Radixx may provide an appropriate balance of functionality, cost and implementation effort. Where the airline expects extensive alliance participation, multi-hub operations or complex interline servicing, the platform should be stress-tested against those future requirements before selection.

0

• User Ratings (0 Votes) 0