Tenbin vs OneCal — カレンダーミラーとTime Commerceの差
仕事が Google アカウントの束なら Tenbin が直球。Google・Outlook・iCloud を同期で一枚にしたいなら OneCal のスコープが広いです。
要点
OneCalはカレンダー間で予定をミラーリングし、すべてを一か所で見られるようにします。Tenbinはさらに先へ。ミラーリングせずに空き時間を統合し、組み込みの決済でその空き時間を売れます。
| Feature | Tenbin | OneCal |
|---|---|---|
| Provider scope | Google accounts (OAuth) | Google, Microsoft, iCloud, etc. |
| Approach | No sync; scheduling-native | Sync-first unified calendar |
| Ideal if | Your work lives in Google Workspace | You need cross-provider mirroring |
Provider breadth
OneCal targets people who live across multiple providers and want one aggregated calendar experience via sync. Tenbin assumes your work happens in Google Workspace accounts and optimizes booking across those accounts.
Scheduling depth
Tenbin includes booking pages, guest flows, and host controls oriented to public scheduling. OneCal's primary story is unification; scheduling features depend on product tier — compare current roadmaps.
Data path
Sync-based tools move event data. Tenbin's default path is free/busy intervals for availability, then write a single event to the destination calendar you choose when a guest books.
Operational fit
If you run five Google Workspace identities, Tenbin maps directly. If you run Google + Outlook + iCloud personally, OneCal's breadth may win.
Summary
Breadth (OneCal) vs focused Google booking fabric (Tenbin). Choose based on where your calendars actually live.
FAQ
Roadmaps change; today Tenbin is optimized for Google OAuth and Calendar API.
関連記事
あなたの時間に、値段をつけよう。
カレンダーを連携し、料金を決めて、リンクを1本公開するだけ。マーケットプレイスで見つけてもらう／自分のリンクで直接共有、どちらもOK。
無料ではじめる