Oracle OPERA Cloud · PMS Power Index

Composite score: 74.0 / 100 (published snapshot v2026.6, 2026-08-09)

Oracle OPERA Cloud scores 74.0 out of 100 on the PMS Power Index. Evidence-backed diagnostic across ten API capabilities. Vendor-neutral. Open to dispute.

Scores by capability

Marketplace coverage

Score: 9 of 9 (Best-in-class). Weight 10%.

First scorer rationale: Confirmed at 9 (Best-in-class). Oracle Cloud Marketplace hosts a certified partner ecosystem reached via OHIP, spanning RMS, CRS, guest messaging, keyless and mobile key, upselling, POS, loyalty, ERP and CX/CRM, per evidence row 18b17e44. The 8 or more category criterion at anchor 9 is satisfied on that row. OPN membership and validation enforce certification quality. No certified-integration count is published on any Oracle surface reviewed, so the 150 or more count criterion is not supported by a mapped evidence row and is disclosed as unmapped in accordance with the v2.4 criterion-coverage clarification. Note: this is the same evidence base used in marketplace_coverage, where it measures programme infrastructure quality; here it measures certified integration count and category breadth. [Rationale correction — 2026-08-09] "The figures of 650+ certified partner solutions and 1,200+ organisations are withdrawn. No evidence row on this dimension establishes either count, and the count is load-bearing on the anchor-9 threshold of 150+ certified integrations. This applies the rule adopted on 2026-08-08 across the vendor set: where a numerical count is load-bearing it must be supported by an evidence row, and where it cannot be evidenced the figure is withdrawn rather than retained. The score is unchanged at 9. The evidenced position is that Oracle Cloud Marketplace hosts a certified partner ecosystem spanning RMS, CRS, guest messaging, keyless entry, upselling, POS and loyalty, with OPN membership and validation enforcing certification, per evidence row 18b17e44. The 8+ category criterion is satisfied on that row. The 150+ count criterion is not currently supported by a mapped evidence row and is disclosed as such in accordance with the v2.4 criterion-coverage clarification; the score is unchanged under the Evidence Reconstruction Principle and the criterion is recorded for assessment at the next scheduled review." [Corroboration — 2026-08-09] "A second independent evidence row has been captured on this dimension, satisfying the two-row corroboration floor in the scoring rules, which provides that a dimension documented by a single evidence row caps at 6 until corroborated. The new row maps to the active-partner-programme criterion and its published certification process: Oracle PartnerNetwork documents tiered membership levels with Oracle Marketplace listing, integration qualification and integration validation as named programme benefits, and states which level is required for each. It corroborates, on an independent Oracle surface, the listing-and-validation position previously carried only by row 18b17e44, and it also corroborates the category-breadth position indirectly through the Marketplace listing requirement. The 150 or more certified integrations count criterion is not evidenced by the new row and remains disclosed as unmapped: no Oracle surface reviewed on this capture publishes a certified-integration count. The score is unchanged at 9."

  • OHIP hosts an open marketplace of certified integration partners accessible via Oracle Cloud Marketplace. Partners must maintain active Oracle PartnerNetwork membership and pass validation to be listed; unlisted integrations are not acknowledged by Oracle sales. The ecosystem covers RMS, CRS, guest messaging, keyless entry, upselling, POS, and loyalty categories, with IDeaS, Duetto, Cendyn, and SynXis among certified partners. https://www.oracle.com/hospitality/pms-pos-integration-partners/
  • Oracle PartnerNetwork publishes a tiered partner programme (Levels 0-3) whose documented benefits include Oracle Marketplace listing, "Integration qualification" and "Integration validation" as named technical accelerators, with published guidance on which level is required to list a solution on Oracle Marketplace and to access integration qualification. This establishes an active partner programme with a published certification/validation process. No certified-integration count is published on this surface. https://www.oracle.com/partner/

What you can control via the API

Score: 9 of 9 (Best-in-class). Weight 14%.

First scorer rationale: Oracle Opera Cloud lands at 9 (Best-in-class). OHIP exposes the full OPERA Cloud operational surface via REST APIs — front desk check-in and check-out, reservation lifecycle (create, modify, cancel, move), room assignment and housekeeping state, rate and availability management, folio posting and financial reconciliation, and event management. Partners self-register on the OHIP developer portal, receive sandbox access, and manage API keys without Oracle involvement at any stage. The API catalogue is versioned quarterly, publicly maintained on GitHub under a Universal Permissive Licence, and accompanied by a TypeScript reference implementation and Postman collections. The combination of full operational write coverage, self-service onboarding, open-source specifications, and sandboxed testing without vendor gating meets the Best-in-class anchor for this dimension. [Comparator withdrawal — 2026-08-13] The comparator "matched only by Mews and Apaleo in the current Index" is withdrawn from the body. Whether another vendor meets the anchor criteria is not a determinant of this vendor's score, applying the standard adopted across the vendor set on 2026-08-09. The score is unchanged at 9.

  • OHIP exposes OPERA Cloud's full operational surface via REST APIs covering front desk, reservations, housekeeping, events, and distribution. Partners self-register, receive sandbox access, and manage API keys without Oracle intervention. The API catalogue is versioned and publicly documented on GitHub under a Universal Permissive Licence. https://www.oracle.com/a/ocom/docs/industries/hospitality/hosp-integration-platform-ds.pdf
  • OHIP exposes granular REST write surfaces across the full OPERA Cloud operational footprint — front desk check-in/check-out, reservation lifecycle, room assignment, housekeeping, rate management, folio posting, and event management. Partners manage API keys, subscribe to event streams, and access a sandbox without Oracle involvement. The API catalogue is versioned quarterly and publicly maintained on GitHub under a Universal Permissive Licence with TypeScript reference implementation. https://github.com/oracle/hospitality-api-docs

Real-time updates and webhooks

Score: 6 of 9 (Adequate). Weight 13%.

First scorer rationale: Adjusted to 3 under the new self-serve enablement rule (Rule 2). OHIP Streaming API via WebSocket and GraphQL Subscriptions is architecturally sound and technically at anchor 6, but enablement is gated: customers must purchase the OHIP Premium Remote Assistance SKU (B93152), engage Oracle Professional Services, and partners pay per event with a one-stream-per-application-key cap. Capability that is gated behind sales engagement, paid professional services, or partner-tier approval scores one anchor below its technical level, with the gating noted here. Lands at 3. 2026-08-08: Gating basis now evidenced. Oracle OHIP Streaming Implementation Guide FAQs (T1) confirm the SKU B93152 purchase and Oracle Professional Services engagement required for enablement, partner per-event pricing (100,000 events for $10; customers do not pay), and the one-consumer-per-stream cap per appKey/chainCode/gateway. Score unchanged at 3. [Score correction — 2026-08-09] Event-Driven Capability is restored from 3 to 6, reversing the reduction applied on 2026-07-07. The reduction applied a self-serve enablement provision stating that capability gated behind sales engagement, paid professional services or partner-tier approval scores one anchor below its technical level. A version audit conducted on 2026-08-09 established that this provision was introduced into the scoring framework on 2026-06-27, four weeks after this vendor was assessed on 2026-05-30, and that it has never been published on the methodology page in any version. The rationale above cites the provision as 'Rule 2'; no numbered rule register exists in the methodology, so that citation is withdrawn as unresolvable. The provision has not been applied to any other vendor or any other dimension. The reduction was not prompted by new evidence. The assessment of 2026-05-30 recorded the same enablement facts, the Oracle Professional Services requirement and per-event partner billing, and characterised them as friction for smaller integrators rather than as disqualifying. Corroborating evidence for the gating characterisation was captured on 2026-08-08, five weeks after the score changed. Applying an unpublished provision retrospectively to a single score is not consistent with the published methodology. The score is therefore restored to the value determined at assessment under the methodology then in force. The score of 6 rests on the anchor-6 criteria: OHIP publishes a streaming surface via WebSocket and GraphQL Subscriptions covering core reservation and folio events, with authenticated delivery via OAuth and per-application key controls, and documented subscription management. Anchor 9 is not reached on the present evidence: cryptographic payload signing, documented retry with backoff, and a replay endpoint are not evidenced on this dimension. Whether the streaming surface reaches anchor 9 has not been assessed and is recorded for the next scheduled review. Commercial enablement terms for the Streaming API are separately evidenced and remain in the ledger. Their treatment under the scoring framework is a methodology question, referred for determination and cohort-wide application at the next scheduled review rather than applied to this vendor alone.

  • Oracle Hospitality Integration Platform (OHIP) datasheet — official Oracle document confirming the streaming / business events capability (WebSocket, GraphQL Subscriptions) that the Rule 2 rescore was based on. https://www.oracle.com/a/ocom/docs/industries/hospitality/hosp-integration-platform-ds.pdf
  • Oracle OHIP Streaming Implementation Guide, FAQs. States verbatim that to enable the Streaming API for customers: "Initial Environment: Purchase the Oracle Hospitality Integration Platform Cloud Premium Remote Assistance SKU - 4 Hour Workshop (B93152) to engage with Oracle Professional Services. This workshop includes enabling streaming for one UAT chain," and lists as a minimum requirement "Streaming API Enablement: Engage with Oracle Professional Services to enable the Streaming API for your environment." Subsequent environments require a Technical Service Request; partner enablement also requires a Technical Service Request. On pricing: "Customers do not pay for the Streaming API. Partners pay per event, with 100,000 events costing $10." On the stream cap: "One consumer per stream: Only one connected client per app key/chain at a time; all others will be refused," and "The single consumer per stream limit still applies per appKey, chainCode, and gateway." Also states "Manual approvals provisioning: Integration and event subscription approvals are mandatory through the Oracle Hospitality Developer Portal." https://docs.oracle.com/en/industries/hospitality/integration-platform/stmig/c_faqs.htm

Readiness for AI agents

Score: 6 of 9 (Adequate). Weight 12%.

First scorer rationale: OHIP exposes a published OpenAPI specification on Oracle's official GitHub repository (oracle/hospitality-api-docs) and a documented streaming/webhook surface via the OHIP Streaming Implementation Guide. The API is therefore agent-callable in principle and event-driven primitives are available, clearing anchor 6 (OpenAPI spec published; webhooks available; API is agent-callable in principle). Anchor 9 is not reached: no MCP server, no semantic-search endpoint, and no embeddings endpoint exist for the hospitality stack. Oracle's MCP investments sit in OCI Generative AI Agents and MySQL HeatWave, not OHIP. Adequate (6) is the correct landing.

Data model and multi-property design

Score: 6 of 9 (Adequate). Weight 10%.

First scorer rationale: Business event model is comprehensive and role-gated, but chain-level vs property-level scoping and manual business event configuration by PMS users adds operational overhead. OPERA 5 vs OPERA Cloud data model divergence is a real complexity for multi-PMS estates. [Rationale correction — 2026-08-09] "The reference to OPERA 5 versus OPERA Cloud data model divergence is withdrawn as a reason on this dimension. Divergence from a separate product is not a criterion at any anchor of Data Model Depth, whose anchors concern multi-property hierarchy, guest profile portability and reporting. This applies the same standard applied across the vendor set on 2026-08-09, under which cross-product and cross-vendor comparators are withdrawn where the rubric does not make them relevant. The score is unchanged at 6. The operative position is stated against the anchor criteria: multi-property hierarchy is evidenced, with chain-level and property-level scoping and role-based access controls per evidence row fcab6231. A shared guest profile across properties is partially evidenced. A standard reporting API is not evidenced on this dimension. Anchor 9 is not reached: it requires a real-time reporting API with portfolio-level aggregation and unified guest profile with custom attribute support, neither of which is evidenced. The unmapped criteria are disclosed in accordance with the v2.4 criterion-coverage clarification."

  • OPERA Cloud business events cover every transactional change in the PMS — reservations, rates, guest profiles, housekeeping, and financials — queued via an outbound messaging system and delivered through OHIP's Event Hub. The data model distinguishes chain-level and property-level scope, with five role-based access controls governing what each integration can read or write: OHIPADMIN, OHIPDEVELOPER, OHIPANALYTICS, OHIPENVIRONMENTS, and OHIPVIEW. https://docs.oracle.com/en/industries/hospitality/integration-platform/axern/c_feature_summary.htm

Developer tooling and sandbox

Score: 6 of 9 (Adequate). Weight 10%.

First scorer rationale: Adjusted to 6 on cross-vendor review. Anchor_9 requires SDKs for 2+ languages plus a published developer support SLA. OHIP ships a self-service developer portal, sandbox, GraphiQL playground, quarterly release notes, and a TypeScript reference implementation — strong supporting evidence for Solid (6), but a single TypeScript reference does not satisfy "SDKs for 2+ languages" and no published developer support SLA was found. Best-in-class withheld until both criteria are evidenced.

  • OHIP provides a fully self-service developer portal where partners register applications, manage API keys, subscribe to event streams, and access a non-production OPERA Cloud sandbox without Oracle involvement. REST API specs and Postman collections are open-sourced on GitHub under a Universal Permissive Licence. A GraphiQL playground is available for streaming API testing, and Oracle publishes a quarterly changelog with dedicated learning paths for both customers and integrators. https://github.com/oracle/hospitality-api-docs

Uptime and operational discipline

Score: 3 of 9 (Limited). Weight 9%.

First scorer rationale: Adjusted to 3 on owner review. Anchor_6 requires an automated public status page with at least 90-day history as a baseline; no public OPERA Cloud or OHIP status page was located. The contractual 99.9% OCI SLA and enterprise-grade infrastructure are strong supporting evidence, but contractual SLA without a public status page does not clear anchor_6. API-specific uptime tracking and published post-mortem cadence are also not publicly evidenced. Defaults to Limited (3) until a public status page is published. [Evidence update — 2026-08-08] "The absence of a public status page has been independently verified by targeted search of Oracle Hospitality and OHIP public surfaces, rather than resting on the original review's non-location of one. No publicly accessible OPERA Cloud or OHIP status page publishing service availability or historical uptime was found. The score is unchanged at 3: anchor 6 requires an automated public status page with at least 90-day history as a baseline criterion, and the contractual OCI SLA, which is separately evidenced, does not substitute for it." [Label correction — 2026-08-13] The body above previously described 3 as "Adequate". Under the published labels 3 is Limited and 6 is Adequate. The body now reads Limited (3). The score is unchanged at 3.

  • OPERA Cloud runs on Oracle Cloud Infrastructure, which carries a contractual 99.9% monthly uptime SLA for SaaS services with service credits triggered below that threshold. OPERA Cloud recorded more than 31% year-over-year growth in properties in FY2025, including Hyatt's 1,000+ property global standardisation, indicating production stability at enterprise scale. https://www.oracle.com/a/ocom/docs/oracle-cloud-infrastructure-sla-support.pdf
  • No publicly accessible status page publishing service availability or historical uptime for OPERA Cloud or OHIP was located. Searches covered Oracle Hospitality product and OHIP pages, OHIP documentation, and the OHIP datasheet. The only Oracle status-page facility identified in search results relates to Oracle Health Insurance Cloud Services, a different product, and is not publicly accessible. The contractual 99.9% OCI uptime SLA is separately evidenced but the anchor-6 automated public status page criterion is not met. https://www.oracle.com/hospitality/integration-platform/

Security, authentication, and compliance

Score: 6 of 9 (Adequate). Weight 8%.

Reconciliation note: [Superseded — 2026-08-08] "The narrative immediately below records the position before the location of Oracle's public Data Processing Agreement and is retained for audit. The operative rationale is the 2026-08-08 block, which reconciles this dimension at 6." Anchor_6 requires OAuth 2.0 with scoped permissions, plus SOC 2 Type II or ISO 27001, plus a locatable GDPR DPA. All three are required. Oracle evidences OAuth 2.0 with per-application key controls and holds ISO 27001, SOC 1, SOC 2 and HIPAA via OCI. No public GDPR DPA was located in the archived evidence. Anchor_6 is therefore not met and the dimension scores 3 per published methodology. [Score update — 2026-08-08] Governance & Security moves from 3 to 6. The single missing anchor-6 leg, a locatable GDPR DPA, is now evidenced: Oracle publishes a current Data Processing Agreement for Oracle Services at its public contracts repository. OAuth 2.0 with per-application key controls and ISO 27001 certification via OCI were already evidenced. All three anchor-6 criteria are therefore satisfied. Score does not reach 9: anchor 9 additionally requires a published penetration-test cadence and documented role-based API access controls, neither of which is evidenced. Note that the existing certification evidence row records SOC 2 without specifying Type II; the anchor-6 certification leg is satisfied independently by ISO 27001.

First scorer rationale: Adjusted to 6 on cross-vendor review. Anchor_6 requires OAuth 2.0 plus SOC 2 or ISO 27001 plus a published GDPR DPA. Oracle clears all three: OCI ISO 27001, SOC 1, SOC 2 and HIPAA certifications, OAuth 2.0 per-application key controls, and a public GDPR Data Processing Agreement located on 2026-08-08. Anchor_9 requires SOC 2 Type II and ISO 27001 together, a published penetration-test cadence and documented role-based API access controls; the penetration-test cadence and role-based API access controls were not located in public sources. Solid (6) until both are publicly evidenced. [2026-08-08] This primary row is superseded by reconciliation dca880b8-9293-40fa-810a-7020e2dee740, which now also reads 6 following the location of a public GDPR Data Processing Agreement. The primary value is retained unchanged as the historical record. [Correction — 2026-08-09, applied to the body 2026-08-13] The GDPR Data Processing Agreement is an anchor-6 criterion under the published rubric, not an anchor-9 criterion. The body above has been amended to state the anchor placement correctly. Anchor 9 requires SOC 2 Type II and ISO 27001 together, a published penetration-test cadence, and documented role-based API access controls. The score is unchanged at 6.

  • Oracle Cloud Infrastructure holds ISO 27001, SOC 1, SOC 2, and HIPAA certifications audited by independent third parties. OHIP enforces fine-grained OAuth 2.0 security on all APIs with per-application key access controls. Hotels control which APIs each integration partner can access in their environment. Streaming event consumption by partners requires explicit customer approval per property. https://www.oracle.com/a/ocom/docs/industries/hospitality/hosp-integration-platform-ds.pdf
  • Oracle publishes a Data Processing Agreement for Oracle Services (version 14082025) at its public contracts repository. Oracle acts as Processor; the agreement covers Applicable Data Protection Law including GDPR and UK GDPR, defines third-party subprocessor obligations, and incorporates EU Standard Contractual Clauses. It applies to Oracle Cloud Services, which includes OPERA Cloud. This document is scoped to Oracle Cloud Services and does not extend to on-premise products. https://www.oracle.com/contracts/docs/data-processing-agreement-oracle-services-081425.pdf

Partner programme and references

Score: 6 of 9 (Adequate). Weight 7%.

First scorer rationale: Adjusted to 6 on cross-vendor review. Anchor_9 requires programme infrastructure: tiered partner economics, a developer community channel, a reference programme and a dedicated partner-success resource. A publicly searchable partner directory is evidenced via Oracle Cloud Marketplace. Published partner tiers, an active developer forum or community channel, published partner economics and a documented dedicated partner-success resource are not evidenced, so anchor 9 is not reached. Solid (6) on the anchor criteria. Installed base by rooms, analyst recognition and enterprise validation are not criteria at any anchor of this dimension and are not relied on. Named-competitor comparators are not determinants of this vendor's score and are not used. [Rationale correction — 2026-08-09] "Two elements of the reasoning above are withdrawn. First, the named-competitor comparator is withdrawn: whether another vendor meets the anchor-9 criteria is not a determinant of this vendor's score, and comparators of this class were withdrawn across the vendor set on 2026-08-09. Second, market share by rooms, analyst recognition and enterprise installed base are withdrawn as reasons: none is a criterion at any anchor of Ecosystem Maturity, whose anchors concern partner programme tiers, developer community, partner directory, published economics, reference programmes and partner success resources. The score is unchanged at 6. The operative position is stated against the anchor criteria: a publicly searchable partner directory is evidenced via Oracle Cloud Marketplace. Published partner tiers are not evidenced. An active developer forum or community channel is not evidenced. Anchor 9 is not reached: published partner economics, an active developer community and a documented dedicated partner success resource are not evidenced. Anchor-6 coverage is partial and is disclosed in accordance with the v2.4 criterion-coverage clarification; the score is unchanged under the Evidence Reconstruction Principle."

  • Oracle holds the largest PMS market share by rooms globally. OPERA Cloud was named a Leader in the IDC MarketScape Worldwide Hospitality PMS 2025 Vendor Assessment. Recent enterprise adoptions include Hyatt (1,000+ properties), PPHE Hotel Group (18 properties), Scandic Hotels, Thon Hotels, Rotana, and Absolute Hotel Services (23 properties), with 3,500 properties on OPERA Cloud Central. Independent analysis describes Oracle as defending the largest installed base in the industry while cloud-native challengers capture growth momentum. https://www.oracle.com/hospitality/hotel-property-management/hotel-pms-software/

Documentation and changelog discipline

Score: 9 of 9 (Best-in-class). Weight 7%.

First scorer rationale: Oracle Opera Cloud lands at 9 (Best-in-class). OHIP documentation meets every criterion in the rubric: (a) quarterly versioned release notes on a fixed cadence — Release 25.3 September 2025, 25.1 May 2025 — with dedicated breaking-change advance notices issued separately from the changelog; (b) OpenAPI specifications and Postman collections publicly maintained on GitHub under Universal Permissive Licence with no access gate; (c) TypeScript reference implementation published alongside the API catalogue; (d) structured learning paths for both customers and integration partners; (e) a GraphiQL playground for interactive streaming API testing; and (f) per-API troubleshooting guides covering authentication, environment configuration, and version migration. The documentation surface publishes a TypeScript reference implementation and dedicated partner learning paths alongside a quarterly versioned changelog. [Corroboration — 2026-08-09] "A second independent evidence row has been captured on this dimension, satisfying the two-row corroboration floor in the scoring rules. The new row maps to the Oracle-published OHIP GitHub specification repository (OpenAPI REST specifications and Postman collections under Universal Permissive Licence 1.0, no access gate), and maps to two anchor-9 criteria: complete endpoint coverage and updated within three months. The rationale above asserts that every documentation-quality criterion in the rubric is met. Assessed against the stored anchor-9 criteria, the following position is recorded: complete endpoint coverage — evidenced, by the published specification set in the GitHub repository read together with the OHIP API catalogue; versioned with deprecation policy — evidenced, by the OHIP release-notes and patch-release-notes surface, which lists new and deprecated APIs by SaaS product release with a subscription facility; changelog with dates — evidenced, by the dated quarterly release notes; updated within three months — evidenced, the most recent repository commit at capture being 2026-06-25; code examples in two or more languages — not evidenced, the record establishing a single TypeScript reference implementation together with Postman collections, which are request collections rather than code examples in a second language; complete error reference — not evidenced, the record establishing per-API troubleshooting guides but no consolidated error reference. Any criterion not supported by a mapped evidence row is disclosed here in accordance with the v2.4 criterion-coverage clarification. The score is unchanged at 9 under the Evidence Reconstruction Principle, and unmapped criteria are recorded for assessment at the next scheduled review." [Comparator withdrawal — 2026-08-13] The comparatives "the most operationally complete in the Index" and "no other vendor publishes both..." are withdrawn from the body. Cross-vendor comparison is not a determinant of this vendor's score, applying the standard adopted across the vendor set on 2026-08-09. The score is unchanged at 9.

  • Oracle publishes versioned OHIP release notes on a quarterly cadence — Release 25.3 was September 2025 — covering new endpoints, deprecations, and breaking change notices. A dedicated what's-new changelog, implementation guides, Postman collections, and a TypeScript reference implementation are publicly maintained. An October 2025 ReadMe documents upcoming breaking changes to the Streaming API payload structure in advance of the change. https://docs.oracle.com/en/industries/hospitality/integration-platform/axern/c_feature_summary.htm
  • Oracle publishes the OHIP REST API specifications and accompanying Postman collections in a public GitHub repository (oracle/hospitality-api-docs) under the Universal Permissive Licence 1.0, with no access gate. The repository holds rest-api-specs, postman-collections and graphql directories and a documented contribution and security process. The most recent commit at capture is dated 2026-06-25 ("Updated Postman collection for Data APIs" for release 26.1), within three months of capture. The repository does not publish code examples in two or more programming languages, and does not publish a consolidated error reference. https://github.com/oracle/hospitality-api-docs

Scores are published only where documented evidence exists. Corrections and disputes are recorded in the public changelog. The scoring rubric is published in full in the methodology.

This provider is listed in the HotelLogic marketplace →

Rank 3 of 17 scored vendors on the PMS Power Index ladder.