Tenbin と CalendarBridge：同期型とスケジューリング型
要点
CalendarBridge はイベントをコピーして同期し、その上で予約ページを提供する。Tenbin はイベントをコピーせず Free/Busy のみを読み取る。データ移動を抑え、予約に特化した構成。
| Feature | Tenbin | CalendarBridge |
|---|---|---|
| Core mechanism | Free/busy reads; no event copy | Sync copies events between calendars |
| Data movement | Minimal (availability intervals) | Higher (event replication) |
| Focus | Booking pages across Google accounts | Sync + scheduling add-on |
Sync vs FreeBusy
Calendar synchronization duplicates event shells across accounts so each side 'sees' blocks. That works but increases data movement and configuration surface. Tenbin avoids replication: hosts connect accounts once, and the product queries Google's FreeBusy API when computing slots.
Scheduling pages
Both products can expose booking links. Tenbin optimizes the path from 'N Google identities' to 'one merged availability.' CalendarBridge users often configure bridges first, then layer scheduling — two mental models.
Privacy and compliance
Not copying event titles or descriptions between employers can be a compliance advantage. Confirm with your counsel; architecturally, FreeBusy-only reads are narrower than full-event sync.
Pricing and scale
Compare vendor pricing for your seat count and bridge count. Tenbin bills by connected Google account for scheduling; evaluate CalendarBridge for how many bridges and pages you need.
When to pick which
Pick CalendarBridge when you need cross-platform calendar mirroring beyond scheduling. Pick Tenbin when scheduling across Google accounts is the core job and you want minimal data replication.
FAQ
Some teams use sync for visibility and Tenbin for external booking — avoid double-booking by policy. Evaluate overlap carefully.