From rental housing to hotel revenue: why RealPage is now your problem
The RealPage litigation in rental housing is not a distant curiosity for hospitality executives. It is the clearest roadmap yet for how plaintiffs, regulators, and the antitrust division of the United States Department of Justice may frame a future hotel revenue management system antitrust case, especially where algorithmic pricing tools sit at the center of market coordination theories. For risk managers and directions générales, the RealPage defendants are effectively a dress rehearsal for how hotel chains, hotel operators, management companies, and hotel owners could be cast as coordinated actors if their revenue management software is built on shared nonpublic data and common pricing recommendations.
In the RealPage matter, plaintiffs allege that rental housing competitors used the same management software and pricing algorithms to align prices in markets from Seattle to Atlanta, relying on nonpublic data feeds that transformed a technology vendor into a hub for alleged price fixing. Translating that logic into hospitality, any hotel revenue management system antitrust analysis will ask whether an RMS vendor aggregates detailed hotel room and hotel revenue data from multiple competitors, then sends back pricing recommendations that materially influence prices across a local market. When plaintiffs and regulators map those flows, they will not focus on the elegance of the software but on whether competitors effectively outsourced independent pricing judgment to a shared algorithmic pricing engine.
RealPage has already shown how plaintiffs can frame a class action theory that treats a technology platform as the center of a hub and spoke conspiracy, even when competitors never speak directly. If a similar complaint targeted hotel chains in a city like Las Vegas, the middle district court hearing the case would likely dissect how each RMS uses market data, how often hotel operators follow the pricing recommendations, and whether the management companies can prove independent price setting. That is why the justice department and its antitrust division are watching algorithmic pricing tools across sectors, and why hospitality counsel should assume that hotel revenue management system antitrust scrutiny is a matter of timing, not speculation.
For insurers and juristes advising hospitality clients, the RealPage defendants and plaintiffs are a practical template for policy wording and claims scenarios. Directors and officers liability, cyber, and professional indemnity programs now need explicit treatment of revenue management software risks, including defense costs for antitrust investigations and class action litigation tied to pricing algorithms. The RealPage experience in rental housing has already influenced how underwriters assess management software concentration in a given market, and similar questions will soon be asked of hotel revenue platforms that centralize prices and recommendations for thousands of rooms.
How hotel RMS architectures can look like antitrust coordination engines
Most modern hotel revenue management systems are built on shared data architectures that would look familiar to any RealPage litigator. A typical RMS ingests nonpublic data from multiple hotel operators, including detailed room inventory, historical prices, booking pace, channel mix, and sometimes competitor benchmarks that go far beyond public rate scraping. The same management software then processes this data through pricing algorithms and pushes pricing recommendations back to each client, often with default settings that heavily influence final prices.
From an antitrust perspective, the risk is not the existence of revenue management tools but the combination of nonpublic data pooling, common pricing logic, and high adherence to algorithmic pricing outputs across competitors. When plaintiffs allege hotel revenue management system antitrust violations, they will argue that competitors effectively agreed to follow a shared set of prices generated by the same RMS, even if no human ever exchanged an email about price fixing. Courts in the RealPage litigation have already shown a willingness to treat algorithmic coordination as a form of agreement when defendants rely on the same vendor, the same data, and the same pricing recommendations to set prices in a concentrated market.
The pending Third Circuit appeal related to revenue management software in the RealPage context will be closely watched by hospitality counsel. A decision that endorses hub and spoke theories for algorithmic pricing could be cited against hotel chains and management companies that use a single RMS provider across multiple brands and markets, especially where hotel owners are contractually required to adopt that software. Risk managers should already be mapping where their group relies on one vendor for hotel revenue optimization, how that vendor uses competitor data, and whether the system architecture could be portrayed as a coordination engine rather than a neutral decision support tool.
Litigation in the middle district courts has also highlighted how motions to dismiss can turn on detailed allegations about data flows and pricing behavior. When plaintiffs allege that defendants followed RealPage pricing recommendations more than a specified percentage of the time, judges are more inclined to let a class action proceed past the motion to dismiss stage. If a similar complaint targeted hospitality, plaintiffs would likely request RMS logs, audit trails, and configuration settings to show that hotel operators routinely accepted algorithmic pricing outputs without meaningful override, especially during high demand periods in markets like Las Vegas where synchronized price increases are highly visible.
Legal teams advising hospitality clients should also track state level developments such as California AB 325, which amends the Cartwright Act to apply explicitly to algorithmic software applications. That statute signals a broader willingness to treat management software as a potential antitrust actor, not just a neutral tool, and it will influence how courts evaluate hotel revenue management system antitrust claims involving California properties. For a deeper view on how courts exercise discretion in complex commercial disputes, hospitality risk leaders can review the analysis of judicial decision making under New Jersey Court Rule 4:46 1 in this risk management litigation overview, then apply similar reasoning to RMS related motions.
Competitive intelligence versus price signaling: drawing a defensible line
Every revenue director wants sharper competitive intelligence, but antitrust law cares deeply about how that intelligence is generated and used. Scraping publicly available prices from online travel agencies or brand sites is fundamentally different from feeding nonpublic data from multiple competitors into a shared RMS that then returns harmonized pricing recommendations. The hotel revenue management system antitrust risk emerges when the line between observing the market and signaling future prices through a shared algorithm becomes blurred.
In a compliant model, an RMS uses public prices, anonymized benchmarks, and each hotel’s own data to suggest a price for every room type, while leaving clear space for independent judgment by hotel operators and management companies. Problems arise when management software aggregates nonpublic data such as forward booking curves, corporate rate loading, or group block details from multiple competitors, then uses that information to generate algorithmic pricing outputs that many clients follow without deviation. At that point, plaintiffs allege that the RMS has become a conduit for coordinated prices, and that defendants have effectively agreed to align their prices through a common technological intermediary.
Risk managers should work with juristes and compliance teams to define bright lines between legitimate benchmarking and unlawful price signaling. Contracts with RMS vendors should prohibit the use of identifiable nonpublic data from direct competitors in the same local market, and they should require that any market indices be aggregated, anonymized, and delayed enough to avoid real time coordination of prices. Where hotel chains operate multiple brands in a city like Las Vegas, internal policies must also distinguish between lawful multi brand revenue management and conduct that could be characterized as intra group price fixing, especially when the same pricing algorithms and data feeds are used across competing flags.
Courts assessing a hotel revenue management system antitrust claim will look closely at how often hotel operators override pricing recommendations, particularly during compression nights and major events. A pattern of near automatic acceptance of RMS prices can be portrayed as evidence that competitors ceded pricing authority to the algorithm, while a documented practice of independent review supports the narrative of autonomous decision making. For insurers evaluating hospitality portfolios, these behavioral details matter as much as the software architecture, because they shape both liability exposure and the likelihood that a class action will survive a motion to dismiss.
Security and risk leaders who have followed the rise in negligent security verdicts understand how operational behavior can transform legal theory into eight figure exposure. The same lesson applies here, and the analysis of expanding liability in this negligent security liability posture review offers a useful analogy for how juries may react to evidence of algorithmic coordination. When a plaintiff’s bar can show that defendants chose efficiency over independent judgment, hospitality brands often find themselves explaining not just their policies but their culture of compliance.
Contracting, documentation, and governance: building an antitrust ready RMS program
Hotel revenue teams cannot abandon technology, but they can design an antitrust ready governance framework around their RMS. The starting point is contracting, where hotel owners, hotel operators, and management companies must negotiate clear language on data use, pricing algorithms, and audit rights with their software vendors. Clauses should specify that nonpublic data from one client will not be shared in identifiable form with competitors, and that any market benchmarks used for pricing recommendations will be aggregated, anonymized, and subject to appropriate time lags.
Risk managers should insist on detailed documentation of how pricing algorithms function, including which inputs drive price changes and how often the vendor recalibrates models using cross client data. Where possible, contracts should require that vendors provide explainability tools so that revenue management teams can articulate why a given hotel room price was recommended, rather than treating the RMS as a black box. This level of transparency is essential when defending against hotel revenue management system antitrust allegations, because it allows defendants to show that the software supports, rather than dictates, independent pricing decisions.
Operationally, hospitality groups need written policies that require revenue managers to review and, where appropriate, override RMS pricing recommendations, especially during peak demand periods. Logs should record when human judgment adjusted prices up or down, along with brief rationales tied to local market intelligence, brand positioning, or specific events. In a future class action, these records become critical evidence that defendants did not simply follow algorithmic pricing outputs generated from pooled nonpublic data, but instead exercised independent management of prices at the property and cluster level.
Governance should extend beyond pricing into broader data security and privacy controls, because RMS platforms often sit alongside other systems that store sensitive guest and operational data. A recent analysis of self check in terminals as potential PII stockpiles in hotel lobbies, available in this hardware audit for hospitality risk leaders, illustrates how overlooked technology assets can create systemic exposure. The same mindset should apply to revenue management software, where unexamined integrations and opaque data flows can quietly expand both cyber and antitrust risk.
Finally, insurers and brokers working with hospitality clients should update proposal forms and underwriting questionnaires to capture RMS specific information, including vendor names, geographic scope, data sharing practices, and any prior regulatory inquiries. This information helps calibrate coverage for defense costs, civil fines where insurable, and potential settlements arising from hotel revenue management system antitrust investigations. For sophisticated hotel chains and management companies, aligning insurance structures with RMS governance is no longer optional ; it is part of a coherent risk posture that treats pricing technology as a core legal and financial exposure, not just a lever for incremental revenue.
Key figures and regulatory signals shaping RMS antitrust risk
- RealPage related litigation has generated multiple consolidated class actions in federal courts, with plaintiffs alleging coordinated rent increases across tens of thousands of rental housing units in the United States, illustrating the potential scale of algorithmic pricing exposure for hospitality portfolios of similar size (based on public court filings).
- California AB 325 amended the Cartwright Act to cover algorithmic software applications, signaling that at least one major state is explicitly targeting pricing algorithms and management software in its antitrust framework, which increases compliance complexity for hotel chains operating significant room counts in California (as reported by legal analyses of AB 325).
- Industry surveys of hotel revenue leaders have found that many properties accept RMS pricing recommendations more than 80 percent of the time during high demand periods, a behavioral pattern that plaintiffs could cite as evidence of de facto reliance on shared algorithms rather than independent price setting (based on aggregated revenue management benchmarking studies).
- In markets such as Las Vegas, where a small number of large hotel operators control a high proportion of total hotel room inventory on the Strip, even modest alignment in prices driven by a common RMS vendor could affect thousands of rooms per night, magnifying potential damages in any hotel revenue management system antitrust class action (derived from publicly reported room counts and market share estimates).