Channel manager Live

The channel's credentials live in the product

The connection's keys are in an encrypted vault the application role cannot read, with a trail that survives a key change.

The credentials for a channel connection are the hotel's, not ours, and not a line in a config file. They are held in a vault module of the database, encrypted at rest, readable only by the functions that need to sign a call, and never returned to a browser.

What the screen shows

The client identifier, the environment, a fingerprint of the key and who set it — enough to know which key is in use, never the key. The screenshot on this site is scrolled past that block.

Changing a key

A key can be changed by a role with the right; the old one is retired, the new one signs from the next call, and the trail of what was set when survives the change. The pusher and the API read the same vault, so there is one key to change and one place it lives.

Isolation

The vault is a separate schema with its own grants. A function that reads it is never combined with one a tenant can call, and the test suite proves the application role cannot select from it.

More on Channel manager

The channel managerPart of the product, not a second subscription: rates, inventory and restrictions out; bookings, modifications and cancellations in; every call kept. A booking arrives, and is on the chart in the same requestThe channel's booking is applied inline — guest, room, price, tax and payer — and the acknowledgement says whether it landed, and if not, why. What is pushed, and whenRates, rooms and restrictions go the moment they change. The channel is told more than we have on purpose, and told less when the house keeps rooms back. A queue that is not moving says soEvery push has a status, an attempt count and the error; a queue that has stalled is a sentence on the screen, not a silence. The sync logEvery call both ways, hotel by hotel, with the request body and the response body — a dispute with a channel is settled by reading. The OTA is who we collect from, not who the invoice is forAn OTA that collected from the guest is the payer; the guest is still the person on the invoice; the commission is what the channel said, never a silent zero. An oversell is not a failureAn overbooking allowance per type, and a booking that lands into a full type goes on the chart waiting for a room — visible, draggable, decided by the desk. AxisRoomsThe connector the two Asar hotels trade through today — sixteen of nineteen endpoints built, real bookings from six OTAs since 10 September 2026, every push acknowledged.