Built around the actual apartment.
The holiday-home direction puts the individual property and its operating needs first, rather than treating every portfolio like a conventional hotel.
Katalyst Stay / Property management
A native property-management workspace being built for holiday-home operators, with bookings, daily property work and owner visibility in one product direction.
Native PMS in development
Reservations, dates and property availability.
Arrival, departure and operating context.
Commercial records and owner-facing workflows.
A calendar alone is not a usable PMS. The product is being developed around the tasks that come after a booking: preparing arrival, handling changes, coordinating the property and understanding the commercial record.
The holiday-home direction puts the individual property and its operating needs first, rather than treating every portfolio like a conventional hotel.
Bring the booking context closer to guest preparation and operations, while keeping permissions and responsibilities clear.
Assess the working scope and data requirements before changing the system that holds your reservations. No forced cutover is part of a demo request.
The native PMS is not yet accepted as an operational replacement. The first offering is for holiday homes, including the Owners portal. Hotel-specific functions will follow separately; current client reservations and availability remain in RMS Cloud.
Not on the evidence currently available. The native PMS is in development and has not replaced RMS Cloud in the initial client implementation. Operational acceptance and migration scope must be established first.
Yes. The first holiday-home offering includes mandatory owner workflows in its development scope. This does not mean owner reporting or settlement is already released.
Hotels can discuss direct booking, integrations and commercial improvements now. Deeper hotel-specific PMS functions follow the holiday-home release rather than being presented as already complete.
A focused conversation
Discuss your property mix, current PMS and the workflows a replacement must handle. Development previews are clearly separated from working release scope.
We confirm the relevant demonstration or development preview and a suitable time by email. Rollout is agreed separately.