Vyrobel keeps one availability pool with a single write path, so it is built to drive channels without the calendars ever drifting apart. ⚠️ No OTA channel can be connected yet: what is live today is the direct storefront, Stripe payments, accounting exports and scoped third-party access.
⚠️ Not connectable yet. The sync pipeline, the rate push and the inbound-booking importer are built and tested against a simulated channel; a real connection needs a Channex partner account we have not set up.
⚠️ Not connectable yet, and Airbnb guest messaging is not built — the inbox carries in-app and logged conversations only.
⚠️ Not connectable yet. Expedia is in our channel catalogue; Vrbo is not modelled at all.
Card payments on the storefront and at the desk, deposits, refunds and credit notes — all reflected in the folio and the owner statement.
Statements and booking ledgers export as CSV and PDF; VAT returns and payout histories export as CSV. These are files you hand over — there is no accounting-package sync.
Grant an app scoped access, review exactly which permissions it holds, and disconnect it in one step — with the whole thing logged.
Every channel would read the same inventory: there is one availability table, one write path, and taking a unit out of service removes it from that pool immediately. ⚠️ Pushing that state out to Booking.com or Airbnb is built, but not yet live.
That's the difference between a channel manager bolted onto a PMS and a platform that owns both.
An ordinary visit sets 2 cookies — vyrobel-session and XSRF-TOKEN. 2 more appear only if you ask for them. All 4 are strictly necessary, and there are no analytics, no marketing and no third-party cookies at all — nothing here tracks you across other sites. So there is nothing on this notice to switch off today. We record your answer anyway, because it binds us if that ever changes.
| Cookie | What it does | How long | When it is set |
|---|---|---|---|
vyrobel-session |
Keeps your session — the sign-in that follows you between pages, and the basket of a booking in progress. | 2 hours | On your first page view. |
XSRF-TOKEN |
Protects every form on the site from cross-site request forgery. Without it a form you submit here could be forged from another site. | 2 hours | On your first page view. |
vy_td |
Remembers a device you chose to trust, so two-factor authentication does not ask again on it. | 30 days | Only if you tick “trust this device” at a two-factor prompt. Never otherwise. |
vy_cookie_choice |
Remembers the answer you gave on this notice, so it is not shown again and so the answer can be honoured. | 365 days | Only when you answer this notice. |