| Calendar | Deployment | Air-gapped | Tiger integration | Protocol / standard | Authentication setup | On-screen booking | Sync direction | Screen shows | Confirm / cancel | Overview map | Room provisioning | Notes |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Cloud only11Hosted by the vendor; nothing to run yourself | ||||||||||||
Microsoft 365Outlook / Exchange mailboxes in M365![]() |
Cloud | No | Graph | Microsoft Graph REST API | Admin user (Office 365 E1, Business Basic or higher) signs in to Tiger's Microsoft-certified Azure app with OAuth 2.0; MFA supportedUse the same admin user for the RoomLists and for attaching the calendar | Yes | Two-way | Title + organizerOrganizer can be hidden | Yes | Yes | Rooms created in the M365 admin centre; RoomLists set up with Tiger's helper script (Windows, macOS, Linux); room-list, single-room and tree import; re-import | Room names and capacity come from M365 and are not editable in the Admin App. New RoomLists can take hours, up to a day, to show up in Azure. Handles recurring-event edge cases and multi-room meetings. |
Exchange OnlineStandalone EXO plans![]() |
Cloud | No | Graph | Microsoft Graph REST API | Same as Microsoft 365 (certified Azure app, OAuth 2.0, MFA) | Yes | Two-way | Title + organizer | Yes | Yes | As Microsoft 365: helper-script RoomLists; room-list, single-room and tree import; re-import | Set up exactly like Microsoft 365. Already on Graph, so not affected by Microsoft switching off EWS in Exchange Online (disabled by default from 1 Oct 2026, fully removed 2027). |
Google WorkspaceRoom resources in Workspace![]() |
Cloud | No | Google Calendar API | Calendar-enabled admin account authorises Tiger's Google-verified app (OAuth); all permissions must be granted within 60 secondsAllow-list the app if company policy requires it | Yes | Two-way | Title + organizerOrganizer can be hidden | Yes | Yes | Resources and buildings managed in the Google Admin console; imported with pagination for large lists, tree import, re-import | Room info and capacity come from Google and are not editable in the Admin App. Imports only the rooms the admin user has rights to. | |
Google CalendarPersonal / non-Workspace account![]() |
Cloud | No | Google Calendar API | Ordinary Google account authorises Tiger's Google-verified app (OAuth); MFA supported | Yes | Two-way | Title + organizer | Yes | Yes | Rooms created in the Admin App become Google calendars automatically; existing calendars can be re-imported; rooms can be renamed and removed | The simplest production setup. On detach, keep or delete the calendars Tiger created. Hidden calendars are not offered for import. | |
Zoho WorkplaceZoho Calendar + Zoho Bookings![]() |
Cloud | No | Native API | Zoho Bookings API (meeting rooms) and Zoho Calendar API (personal calendars) | Customer's own Zoho server-based OAuth app (Client ID + Secret) and Zoho data-centre region; an org admin signs in | Yes | Two-way | Title + organizer | Yes | Yes | Rooms must already exist as Zoho Bookings resources; imported grouped by branch, alongside personal calendars | Panel bookings reach Zoho within seconds; cancellations sync both ways. Each occurrence of a recurring meeting can be checked in, extended or cancelled on its own. |
Yandex 360Yandex Calendar, Yandex 360 for Business![]() |
Cloud | No | Native APICalDAV | Yandex 360 directory API for room import; Yandex Calendar CalDAV on the panels | Customer's own Yandex OAuth app (Client ID + Secret); an org admin with a mailbox on the company domain signs in onceToken lasts about a year and is not renewed automatically | Yes | Two-way | Free/busy onlyBusy slots show "Busy"; no titles or organizers | Yes | Yes | Import grouped by city, office and floor, with capacity; rooms are managed only in Yandex 360 | Needs a verified company domain and a plan with meeting-room reservations. The connected account is the organizer of every panel booking. Reconnecting removes room assignments. |
Lark SuiteGlobal edition![]() |
Cloud | No | Native API | Lark Open Platform app | Admin user signs in and authorises Tiger's Lark-certified appAdmin must be subscribed to the rooms and be room administrator | Yes | Two-way | Title + organizer | LimitedNeeds room-administrator rights to change or delete meetings booked by others | Yes | Tree-style room import (rooms sit on the 5th level of the tree); re-import | Requires at least the Pro plan; the free Starter plan's 10,000 API calls a month run out even with one room. Room info and capacity are not editable in the Admin App. |
Feishu 飞书Mainland China edition![]() |
Cloud | No | Native API | Feishu Open Platform app | Admin user signs in and authorises Tiger's Feishu-certified appAdmin must be subscribed to the rooms and be room administrator | Yes | Two-way | Title + organizer | LimitedNeeds room-administrator rights to change or delete meetings booked by others | Yes | Tree-style room import (rooms sit on the 5th level of the tree); re-import | Same product as Lark, with data kept in mainland China; a separate certified app. Pro plan required, as for Lark. |
DingTalk 钉钉Mainland China and International edition![]() |
Cloud | No | Native API Note: The DingTalk international instance's APIs do not support room resource calendar management (they are available only in the Mainland China instance) |
DingTalk Open Platform: Calendar and Meeting Room APIs | Organisation admin authorises Tiger's DingTalk app (OAuth 2.0); access tokens are renewed automaticallyThe app needs calendar and meeting-room permissions | Testing | Two-way | Title + organizer | Yes | Yes | Rooms and room groups created in the DingTalk admin console; tree-style import, re-import | Room names and capacity come from DingTalk and are not editable in the Admin App. Covers both the mainland China (钉钉) and the international DingTalk edition. |
WeCom 企业微信WeChat Work![]() |
Cloud | No | Native API | WeCom server API (qyapi.weixin.qq.com): Meeting Room and Schedule APIs | Customer's own WeCom self-built app (CorpID + app Secret) and the userid of the member screen bookings are made for; access tokens are renewed automaticallyThe app must be allowed to call the meeting-room and schedule APIs, and the public IP of the screens and the Admin App PC must be in the app's trusted IPs (企业可信IP) | Yes | Two-way | Title + bookerBookings made in the WeCom client may show as occupied only; the booker is shown by userid | Yes | Yes | Meeting rooms created in the WeCom admin console (会议室); imported grouped by city, building and floor; re-import | Only rooms that need no approval can be booked from the screens. WeCom rounds bookings to 30 minutes and has no change API, so extending a screen booking re-books it. |
GaroonCybozu, cloud edition (cybozu.com)![]() |
Cloud | No | Native API | Garoon REST API (schedule events and facilities) | The cybozu.com administrator registers an OAuth client and allows the user; the user signs in once in the browser (SAML and two-factor supported); tokens are renewed automaticallyThis user creates the bookings made on the screens; cybozu.com IP restrictions must allow the screens and the Admin App PC | Yes | Two-way | Title + organizerPrivate meetings show as occupied, without title | Yes | Yes | Facilities and facility groups from Garoon; tree-style import, re-import | Facilities that need a usage request show the booking as pending until it is approved. Repeating meetings can't be changed from the screens. Garoon does not provide room capacity. Running Garoon on your own servers? See Garoon package under Sovereign. |
| Cloud + self-hosted2Run in the vendor cloud, on your own servers, or both; rows marked Sovereign qualify when self-hosted | ||||||||||||
Exchange HybridOn-prem servers + Exchange Online![]() |
Hybrid | EWS only | EWSGraph | Graph when the room mailboxes are in Exchange Online, EWS when they are on-prem | As per the matching connector | Yes | Two-way | Title + organizer | Yes | Yes | Per connector | One connector per Tiger network, so attach the one that matches where the room mailboxes live. v3.5.15 added extended certificate-chain validation for hybrid edge cases. Mailboxes moved to EXO must use Graph once EWS is off there. |
Odoo ERPCommunity & Enterprise editions![]() |
CloudOn-premSelf-hostedSovereignSelf-hosted Odoo | YesSelf-hosted Odoo | Native API | Odoo JSON-RPC External API | Host URL, database name, and a user or service account with password or API key (read/write on Calendar and Contacts) | Yes | Two-way | Title + organizer | Yes | Yes | Rooms are Odoo Contacts, added as meeting attendees; selected contacts are imported | Direct connection, no CalDAV plugin or middleware. Works with Odoo Online or a self-hosted Odoo, so it fits sovereign setups too. |
| Sovereign4On-prem only: everything stays on your own infrastructure | ||||||||||||
Exchange Server on-prem2007 to 2019, Subscription Edition![]() |
On-premSovereign | Yes | EWS | Exchange Web Services (SOAP) | Service account (full email address) and password, server URL and Exchange version; NTLM (v1 or v2) must be enabledCredentials are stored encrypted | Yes | Two-way | Title + organizer | Yes | Yes | Room mailboxes created in the Exchange admin centre; RoomLists set up with Tiger's helper script in the Exchange Management Shell; room-list import, re-import | The EWS connector has most of the Graph connector's features, and Microsoft keeps EWS for on-prem servers. Large sites: allow one EWS session per screen and relax throttling for the service account. |
Local CalendarBuilt into Tiger![]() |
On-premSovereign | Yes | Tiger mesh | Events synced between the screens on the LAN | None | Yes | Two-way within the device mesh only | Bookings made on the screens | Yes | Yes | Rooms created, renamed and removed freely in the Admin App | Used for demos and as fallback when a demo licence expires; screens without a licence run on it. Not intended for production. |
HCL DominoFormerly IBM Lotus Domino / Notes![]() |
On-premSelf-hostedSovereign | YesDomino server on your network | Native API | HCL Domino REST API (JSON over HTTPS, recommended) or Domino Access Services (DAS)Tested with Domino 14.5 | Technical Notes user with an internet password and internet address; REST API address and scope, or for DAS the Domino server address and the technical user's mail fileThe technical user is the organizer of bookings made on the screens | Yes | Two-way | Title + organizerPrivate meetings show as occupied, without title | Yes | Yes | Rooms imported from the Domino Rooms & Resources (Resource Reservations) database, including restricted rooms; re-import. Alternative (DAS only): one mail file per room | Domino's Rooms & Resources Manager accepts or declines each booking, so capacity, availability hours, owner approval and restrictions are respected; a declined booking is removed from the screen. Extensions are checked for conflicts first. Aimed at government, defence and regulated organisations that still run Domino. |
Garoon packageCybozu, on-prem edition (パッケージ版)![]() |
On-premSelf-hostedSovereign | YesGaroon server on your network | Native API | Garoon REST API (schedule events and facilities)Garoon 4.10 or later; facility groups from 5.0 | Technical Garoon user with login name and passwordThis user creates the bookings made on the screens; use HTTPS with a trusted certificate | Yes | Two-way | Title + organizerPrivate meetings show as occupied, without title, from Garoon 5.15 | Yes | Yes | Facilities and facility groups from Garoon; tree-style import, re-import | Facilities that need a usage request show the booking as pending until it is approved. Repeating meetings can't be changed from the screens. Garoon does not provide room capacity. Nothing leaves your network: the screens talk only to your Garoon server. |
| Open standards2Vendor-neutral protocols; sovereign when the server is your own | ||||||||||||
| CalDAV serversAny RFC 4791 server
ZimbraZextras Carbonio / CEIceWarpNextcloudownCloudOX App Suite / openDeskSOGoBaïkalRadicaleSabreDAVHordeApple iCloud
![]() |
On-premSelf-hostedCloudAnySovereignYour own CalDAV server | YesServer on your network | CalDAV | RFC 4791 (CalDAV), RFC 6638 (scheduling), RFC 5545 (iCalendar data), RFC 4918 (WebDAV); PROPFIND, REPORT, PUT, DELETE | Server URL, server profile, username and passwordUse HTTPS; the full certificate chain must be valid, self-signed certificates fail | Yes | Two-way | Title + organizer | Yes | Yes | Calendar collections discovered with PROPFIND and picked from a list; one collection per room | Built-in profiles for Carbonio / Zimbra, Nextcloud / ownCloud, SOGo / Baïkal, generic servers, and Google Workspace / iCloud. Carbonio rooms use a service account with Manager rights or a resource password. Behaviour can vary with each server's scheduling support. |
| iCalendar / WebcalAny .ics feed over HTTP(S)
Exchange / Microsoft 365GoogleZimbraZextras Carbonio / CEIceWarpNextcloud / ownCloudSkeddaYaroomsSuperSaaS
![]() |
On-premSelf-hostedCloudAnySovereignFeed served from your network | YesFeed on your network | iCal | RFC 5545 file fetched over HTTP(S) | Feed URL only; no calendar account neededChange webcal:// to https:// and make the URL end in .ics | No | Read-only | Events as published in the feedTitle + organizer | No | Yes | Rooms created in the Admin App, one feed URL per room with a TEST URL check; replace the file at the same URL without reconfiguring | Built for school and university timetables. Max 10 MB per file. Feeds are polled, so changes appear after a short delay. Lowest-cost option: no calendar subscription. |
AI Assistant