CM Ecosystem: When a Self-Hosted Channel Manager Grows Beyond One Property

CM Free started as a local, self-hosted Channel Manager for small accommodation providers.

But as the project continued to grow, a new question appeared:

What happens when independent CM installations need to communicate with the same external systems — Booking.com, Airbnb, AI search platforms, or even with each other?

The answer we are currently developing is called the CM Ecosystem.

It is not about moving CM into the cloud, and it is not about creating another centralized PMS.

The local Channel Manager remains independent and continues to be the source of truth for reservations, availability, rates, occupancy and local business rules.

What changes is the layer around it.

A CM installation may optionally connect to a shared infrastructure:

CM → Connector → CM Relay → OTA / Community / AI

The planned CM Relay can provide a common connection layer between independent CM installations and external services such as Booking.com and Airbnb.

Instead of building every local installation around one specific connectivity provider, the Relay is designed as a provider-independent layer. Different OTA connectivity providers — and eventually direct integrations — can sit behind the same CM Connector protocol.

But OTA connectivity is only one part of the idea.

From connectivity to CM Community

Once several independent Channel Managers can voluntarily connect to the same ecosystem, another possibility appears.

What if they could also help each other?

A future CM Community could allow participating accommodation providers to share selected public information such as location, capacity, amenities, availability or a direct booking link.

Imagine that your apartment is already fully booked.

Instead of simply telling the guest that you have no availability, CM could search the Community and suggest another independent property nearby.

The guest gets an alternative.

Another host gets a potential direct booking.

And neither property needs to become part of a new OTA marketplace.

AI can become the interface — but not the source of truth

The same architecture also opens another direction: AI-assisted accommodation discovery.

A guest could ask:

> “Find me an apartment for four people near Bled with parking and an EV charger.”

AI can understand that request and convert it into structured search criteria.

But AI should not invent availability, prices or booking conditions.

Those answers should still come from the real Channel Manager data.

In this model:

Natural language → AI interpretation → CM Community search → real availability

AI becomes the interface.

CM remains the source of truth.

And there is still a safety path

One principle is particularly important to us:

> An API should improve a Channel Manager — not hold it hostage.

Even when advanced Booking.com or Airbnb API connectivity becomes available, the local CM should remain operational.

That is why the existing ICS/iCal path remains part of the architecture as a fallback option.

An API outage, Relay problem or temporary interruption of a paid connectivity service should not disable the local reservation system.

The advanced connection may disappear temporarily.

The Channel Manager should not.

The architecture is now visible

We have created a dedicated presentation page that brings these ideas together — CM Core, Connector, Relay, OTA connectivity, Community, AI Discovery and the permanent fallback philosophy.

👉 **[Explore the CM Ecosystem]

The page also contains a large CM Architecture & Operational Map that can be opened and zoomed from the overall ecosystem down into individual parts of the architecture.

The Slovenian version is available here:

👉 **[CM Ekosistem – Slovenian version]

CM Ecosystem is still a project in development.

Some parts already exist, some are being built, and some are still architectural concepts.

But the direction is becoming clearer.

Perhaps we are only building a better bridge between a self-hosted Channel Manager and Booking.com or Airbnb.

Or perhaps we are building the first docking point to something much larger.