The market is not a closed question
Rotana announced its standardisation on Oracle OPERA Cloud across all 79 properties in early 2025. The deployment is staged, with 30 properties live at the time of the announcement and the remaining cohort expected through 2026. The decision was the rational one at the time. OPERA's hospitality module is mature, the global integrator base is dense, the OTA connectivity is well-handled, and the alternatives in the property-management category have meaningful capability gaps for a luxury-scale enterprise.
The Middle East hospitality market is not a settled question, though. Other enterprises in the region — Jumeirah, Emaar Hospitality, Kerzner, the major local chains — are at different points in their PMS cycle. The ones who renewed in the last 18 months have signed multi-year commitments. The ones with renewal calendars sitting in 2026 and 2027 are watching the Rotana deployment and asking a different question. Not whether OPERA is good. Whether owning the property-management workflow makes commercial sense at scale.
This piece is the conversation we have with hospitality CIOs when the renewal calendar lands on the table.
What sits inside the OPERA bill at scale
The OPERA Cloud commercial model is per-property, with the licence cost scaling against the property's room count and the modules the enterprise has activated. The base PMS licence covers the front-office workflow, the reservation engine, the housekeeping coordination, and the night-audit cycle. The expansion modules — distribution, sales-and-catering, food-and-beverage operations, the customer-data layer that sits underneath the loyalty programme — each add commercial scope at renewal.
At an enterprise scaling from 30 to 80 properties, the per-property bill compounds. Each new property carries the standard licence envelope. Each module the enterprise activates across the portfolio compounds against the expanded property count. The integration footprint — channel managers, payment gateways, customer-data platforms, finance integration back to the corporate ERP — is duplicated across the property estate, with the integrator's per-property implementation work billable at each cycle.
Three less-visible cost layers sit underneath the licence at portfolio scale.
The integrator retainer at the property-onboarding cadence. Each new property added to the estate carries a configuration project. The pricing rules, the rate plans, the loyalty integration, the cross-property reservation logic, the operational reporting — all of these require integrator-led configuration that the enterprise pays for at every onboarding. The retainer is structured against the property count, not against the platform's mature footprint.
The channel-management dependency. The OTA connectivity, the global distribution system integration, the metasearch surfaces — all run through a channel-management layer that interfaces with OPERA. The channel-management vendor's commercial model compounds against the same property count OPERA's does, with the per-channel commercial relationships layered against each. The total distribution cost at portfolio scale is materially larger than the OPERA licence alone.
The data-layer integration tax. The enterprise's customer-data platform, the loyalty engine, the marketing automation, the personalisation surface — each of these reads from OPERA's customer record through a defined integration boundary. The boundary is operated by the integrator, on a per-property configuration, with the change-control work billable at every meaningful change.
What "building your own" actually means
We do not propose that every hospitality enterprise should retire OPERA. The clinical-equivalent argument applies in hospitality. The operational risk in PMS migration is real. The night-audit cycle, the reservation engine, and the back-office reconciliation are workflows the enterprise cannot afford to disturb without rigorous validation. The conversation worth having is not whether to replace OPERA. The conversation is which workflows the enterprise should own outright, with OPERA continuing to handle the parts where the existing dependency is genuinely load-bearing.
The pattern is the workflow-led replacement we run at retail, banking, and healthcare clients. Pick the workflow furthest from the system of record. Build the owned alternative against the real estate. Run the parallel-validation period the operational risk requires. Retire the OPERA-vended surface for that workflow on a fixed date. The licence at the next renewal reflects the smaller surface area.
Workflows that move first in hospitality tend to be the guest-facing surfaces and the data layers that sit underneath. The guest-app and the guest-portal. The pre-arrival journey. The post-stay communication. The loyalty engine if the enterprise has built a meaningful programme. The customer-data layer that the marketing engine reads from. The personalisation surface in the room.
The PMS core — the reservation engine, the night-audit cycle, the housekeeping coordination, the back-office reconciliation — stays on OPERA. The enterprise's platform team owns the workflows around the core. The integrator's role shrinks to the modules that remain in scope.
What changes at portfolio scale
Three things change for an enterprise running the workflow-led pattern at 30 properties and onward.
The per-property cost trajectory bends. The OPERA licence continues to scale linearly against property count. The owned-workflow stack scales sub-linearly because the platform investment is amortised across the portfolio. The cost curves cross at a property count the enterprise can model accurately from the first owned workflow.
The institutional capability matures. The platform team that owns the first workflow learns the substrate it will operate against. The second workflow ships in a fraction of the time the first one did. The third workflow ships faster than the second. The institutional capability is the asset the enterprise ends up with.
The renewal conversation with Oracle shifts. The enterprise that has shipped one owned workflow brings a different posture to the next OPERA renewal. The account team responds differently to a customer with a working alternative than to a customer with a hypothetical one.
The regional dimension
Three dimensions are specific to the Middle East hospitality market.
The luxury-scale operating expectation is real. Middle East hospitality competes against the global luxury benchmark on guest experience. The guest-app, the pre-arrival journey, and the in-room personalisation are workflows the enterprise's brand depends on. The off-the-shelf module catalogue does not match the brand standard the enterprise's team is delivering against.
The talent ecosystem has matured. The enterprise can hire the engineering and product capability to operate the owned workflows after handover. Three years ago the talent argument was thinner. Today it is not, particularly in Dubai and Riyadh.
The data residency posture is tightening. Guest data is increasingly subject to the same residency expectations as financial data. The Sovereign Cloud direction in the region reaches the hospitality category. The owned-workflow stack gives the enterprise the freedom to choose the hosting posture for each workflow independently.
The saasinator perspective
The case for owning hospitality workflows is not a case against Oracle. OPERA is competent at what it does. The argument is for matching the cost structure to the value the workflow generates. The reservation engine and the night-audit cycle are commodity — renting them is rational. The guest experience, the loyalty engine, and the personalisation surface are brand differentiation — renting them is not.
The enterprise that runs the first owned workflow successfully has changed the institutional default. The next workflow is a smaller decision than the first. The renewal conversation is a different conversation.
What to bring to the diagnostic
If your hospitality group is preparing the next OPERA renewal, scaling the property count through a meaningful expansion phase, or evaluating an alternative PMS architecture, the conversation worth having is the workflow inventory. Bring the OPERA module breakdown, the integrator retainer schedule, the per-property configuration cadence, and the workflow list the operations and brand teams would prioritise for ownership.
The diagnostic is ten working days. The output is the workflow recommendation, the architecture sketch, and the first-quarter scope. Book a diagnostic at /diagnostic.