Cloudbeds launches its own RMS, built on the Signals data platform

Cloudbeds has launched Cloudbeds RMS, a revenue management system that sits natively inside its own property management system and channel manager. The pitch is aimed squarely at properties that do not have a revenue manager: pricing decisions made without a specialist on payroll or a second vendor in the stack.

The launch was announced on 15 September 2026.

What is in it

Cloudbeds RMS is built on Signals, the company's unified data platform. That matters for what the system can see. Rather than working from rates alone, it pulls together reservations, booking pace, occupancy, time to arrival, length of stay and channel behaviour from the PMS, then combines those with competitor rates and market demand data.

There is an automation mode called Autopilot. It handles routine rate changes inside parameters you set, and steps aside when you want to intervene manually. Rate changes push straight through the Cloudbeds channel manager rather than going through a connection to an outside system.

The product also ties into Cloudbeds Guest Marketing, so a soft period can trigger targeted marketing rather than only a price cut.

"Hoteliers shouldn't need a large revenue team or a complex technology stack to make sophisticated revenue decisions," said Jason Richards, chief business officer at Cloudbeds.

What the release does not cover

Cloudbeds has not said which plan or tier Cloudbeds RMS lands on, whether it costs extra, or which regions get it first. For a product whose selling point is that smaller properties can afford to run revenue management properly, the price is the part that decides whether that is true. Ask before you get attached to the demo.

The company says it serves tens of thousands of properties across more than 150 countries, and has been named a top hotel management system, PMS and channel manager by Hotel Tech Report for eight years running.

What it means for operators

The real question this raises is not whether Cloudbeds RMS is good. It is whether a native RMS beats a specialist one.

The argument for native is genuine and not just marketing. An RMS that reads your booking pace directly from the PMS, with no integration in between, sees cleaner data and sees it sooner. Execution is a single step rather than a recommendation you then have to push somewhere else. Connection failures between an RMS and a PMS are a real and tediously common source of stale pricing, and this removes that surface entirely.

The argument against is that specialist revenue management vendors have spent years on forecasting models, and a first-generation product from a PMS company will not match that depth on day one. If you run a complex property with group business, multiple market segments and meaningful seasonality, the depth is worth paying for.

For a small independent with no revenue manager and no RMS at all, that comparison is beside the point. The alternative is not a better system. It is a spreadsheet and a gut feel, and almost anything beats that.

If you already run a third-party RMS connected to Cloudbeds, there is nothing here forcing a change. No deprecation or migration deadline has been announced for existing integrations. Worth watching, though: when a platform ships its own version of a category, the connected alternatives in that category tend to get less attention over time.