Why Motel One chose the Old Lady

Mews - the most talked-about platform in hotel technology lost a deal it should have won

Earlier this year, Motel One completed the migration of its entire portfolio — more than 100 hotels across 13 countries — to Oracle Opera Cloud. Six months. All properties live. No public drama.

By the standards of large-scale hotel technology migrations, which routinely stall, overrun, or quietly reduce scope until the announcement no longer resembles the project, this was unusual. The trade press covered it as an operational story. That misses the point. The execution is impressive. The choice is more interesting.

Why not Mews?

It is a fair question. Mews raised $300 million in early 2026 at a $2.5 billion valuation — the largest funding round in hotel PMS history. Its leadership positions the platform explicitly as the operating system of hospitality — think Microsoft Windows for hotels — the single infrastructure through which all hotel functions, payments, and intelligence will eventually flow. In the segment where it has concentrated — boutique properties, design hotels, aparthotels, lifestyle concepts — it has built a strong product and a loyal customer base of 15,000 properties across 85 countries. But consistent wins in one corner of a fragmented market is not the same as a path to owning it.

So why did a design-forward chain with more than 100 properties choose a thirty-year-old American platform over the company currently defining the market narrative?

The answer starts with a number. After nearly four decades, billions in acquisition capital, and platform deals with the largest hotel companies in the world, Oracle — the nearest thing this industry has ever had to a dominant player — runs on roughly 20% of global hotel properties. Mews, with its $2.5 billion valuation, sits at around 8%. The top five PMS vendors combined do not control half the market. The long tail contains hundreds of regional and local platforms, many of them thriving not despite global competition but because of it — because local fiscal regulations, regional payment preferences, language requirements, and labor laws make the local specialist more useful than any global platform ever will be.

The hotel PMS market fragments by necessity. It always has. The "operating system" metaphor is borrowed from consumer technology, where interoperability creates lock-in and developer ecosystems compound advantages. This market has never exhibited those dynamics. No platform has consolidated it. The structure won't allow it.

But the fragmentation argument cuts in an unexpected direction when applied to a chain like Motel One. The same structural property that prevents any single platform from dominating the global market is precisely what creates durable value for a platform that has spent decades learning to operate across its fragments. When Motel One expanded from Germany into Austria, then across 13 countries with different tax regimes, different corporate travel infrastructure, different distribution relationships, and different regulatory environments, it needed a platform that had already done that work. That work cannot be replicated quickly. It is not a product feature. It is the accumulated result of thirty years of enterprise deployment across hundreds of regulatory environments.

That is why not Mews.

What Oracle Cloud actually offers at this scale

The infrastructure requirements of a 100-property chain across 13 countries are worth stating plainly, because they explain the Oracle choice better than any vendor pitch could.

Multi-country corporate billing — managing direct billing accounts across jurisdictions, connecting to travel management companies, reporting against corporate rate agreements — is not a feature Motel One was evaluating. It is a baseline. Without it, significant revenue from the managed travel segment is either unserviced or handled manually. At this scale, neither is acceptable. GDS connectivity at enterprise depth, with rate loading, availability management, and corporate negotiated rates flowing cleanly across Amadeus, Sabre, and Travelport, is not an integration option. It is the distribution infrastructure through which a meaningful share of corporate bookings arrive. And when something breaks simultaneously across 100 properties in multiple countries, a managed services team with contractual accountability is not a support preference. It is an operational requirement.

Oracle Managed Services was embedded in the Motel One deployment from day one — proactive monitoring, incident resolution, ongoing optimization across the entire estate. That is not software-as-a-service. It is infrastructure-as-partnership. No challenger platform offers that model at this scale. There is no shortcut to building it.

The Oracle Hospitality Integration Platform connects to more than 1,200 pre-integrated services. The number is less important than what it represents: decades of enterprise integration work across GDS connections, centralized rate and inventory control across the hotel portfolio, and corporate reporting layers that large hotel groups require and cannot assemble from scratch. A challenger platform with hundreds of self-service marketplace integrations is solving a different problem for a different customer. Both are real businesses. They are not the same business.

Opera Cloud is not Fidelio

There is a perception problem worth addressing directly. For a generation of hotel operators, Oracle Hospitality means the on-premise Opera system — or its predecessor, Fidelio — servers in the basement, specialist required to touch it, expensive to update, painful to integrate. That system still runs in many hotels. It is not what Motel One migrated to.

Opera Cloud is an architectural rebuild. Not a refresh. Not a cloud-hosted version of the old software. It runs on Oracle Cloud Infrastructure, deploys without on-site hardware, receives continuous updates without downtime, and exposes a REST API layer that makes integration straightforward. Mobile access is native. Analytics are embedded. The platform that Accor selected as its global standard across 110 countries and that Hyatt used to move more than 1,000 properties is not the system those operators were cursing ten years ago.

On architecture, the gap between Opera Cloud and a cloud-native challenger has genuinely closed. Both deploy without on-site infrastructure. Both update continuously. Both expose modern APIs. A hotelier still making Oracle decisions based on Opera 5 muscle memory is evaluating a product that no longer exists.

But the gap has not closed evenly, and saying so matters. User experience remains the clearest distance. Opera Cloud was rebuilt by enterprise engineers modernizing an enterprise product, and the logic of how screens are organized and workflows are structured carries the weight of that history. Hotels that have made the move report that routine tasks require more navigation than Opera 5, information spread across multiple screens that once lived in one. Mews and its cloud-native colleagues were designed from scratch to a consumer-grade UX standard. Front desk staff with no prior PMS experience learn it faster. That is a real difference, not a marketing claim.

Speed of product development is a second genuine gap. Oracle manages a global installed base across every hotel segment. New product decisions move through a commercial and compliance surface that a focused challenger does not have. Opera Cloud improves, but it does not move at challenger speed and is not going to.

Implementation weight is the third. A cloud-native platform can be live in weeks. An Opera Cloud enterprise deployment is a structured project measured in months, involving Oracle's professional services organization. For Motel One, that included Oracle Managed Services from day one — which is exactly what a migration of that complexity requires. For a smaller group without dedicated IT resources, it looks different.

These gaps are most consequential for operators where simplicity and self-sufficiency matter most. For an enterprise chain running a managed deployment, they are workable. The architecture critique behind the "old lady" label has largely expired. What remains is a distance that matters for some operators and not others. For Motel One, it apparently did not matter.

The regional vendor ceiling

Before Oracle, Motel One ran on SIHOT — a solid PMS with genuine market share and strong standing in the DACH hospitality market. This is not a story about SIHOT failing.

It is a story about what happens when a hotel group crosses certain thresholds of scale and geographic complexity. A regional vendor, however capable within its domain, hits structural constraints when a customer starts operating across 13 countries, managing enterprise corporate accounts, and requiring global managed services infrastructure. The relationship doesn't break because the product deteriorates. It breaks because the customer outgrows the context the product was built for.

This is a broader condition in European hospitality technology. The continent has produced serious regional PMS vendors. At the independent and mid-market level, several compete effectively. But the enterprise layer — the infrastructure layer that governs multi-country distribution, corporate relationships, and managed travel at scale — remains the territory of a thirty-year-old American platform that has spent the last decade rebuilding itself in the cloud.

It is not a comfortable observation for European hotel technology. It is the right one.

What the market should take from this

The cloud-native challenger narrative is real. The funding is real, the product quality is real, the wins in independent and lifestyle segments are real. The argument that the industry is moving away from legacy infrastructure is directionally correct.

It is not universally correct. The PMS decision looks entirely different depending on where a hotel sits in the market. The same fragmentation that makes "hotel operating system" a flawed metaphor makes Oracle indispensable to chains large enough to feel that fragmentation as a daily operational problem. There is no contradiction in arguing that no platform will ever dominate the global PMS market while also arguing that one platform holds a structural advantage at enterprise scale. Both are true. The market fragments by necessity. Enterprise chains need a platform that has already navigated every fragment.

Mews is building a strong business in a real segment of a large market. That is worth real money. But the $2.5 billion valuation requires a different story — one where Mews consolidates a market that has never been consolidated. The market structure does not support that story.

For a 40-room boutique in Amsterdam, the platform decision points in one direction. For Motel One, it points in another. The question was never which platform is winning. It was which platform had done the specific work this chain's commercial reality required.

Motel One answered that. The answer was Oracle.

by Markus Busch, Editor/Publisher Hospitality.today

Read also: The $300 million question: Mews's bid for PMS dominance

Enjoying this analysis? Hospitality.today delivers daily insights on hotel distribution, AI trends, and travel commerce — straight to your inbox. Subscribe for free at Hospitality.today →