Every calendar, one local timeline.
Six sources, what each one can do, and exactly where your data lives — read on-device, never routed through a server.
Capability matrix
6 sources| Source | Read | Write | On‑device | Status |
|---|---|---|---|---|
| macOS CalendarSystem · defaultRead · Write · On-device | ● | ● | ● | Live |
| Google CalendarOAuthRead · Write · On-device | ● | ● | ● | Live |
| OutlookMicrosoft GraphRead · Write · On-device | ● | ● | ● | Live |
| CalDAVApp passwordRead · Write · On-device | ● | ● | ● | Live |
| CalendlyOAuthRead · On-device · no write yet | ● | – | ● | Beta |
| Cal.comAPI keyRead · On-device · no write yet | ● | – | ● | Beta |
Everything converges on your Mac
Each source is read locally and merged into one timeline. Your schedule never leaves the device — there is no Nudgebar server in the path.
How each source connects
Reads the accounts already in Calendar.app — iCloud, Google, Exchange. Nothing to set up.
Sign in once with OAuth — full read and write to every calendar on the account.
Microsoft 365 and Outlook.com, connected through Microsoft Graph.
Any standards-based server: iCloud, Fastmail, Nextcloud, and more.
Pull your scheduling-tool bookings into the same timeline. In early access.
Your schedule stays on your Mac
However you connect, Nudgebar reads your events locally to show and alert you. It doesn't send your calendar to a Nudgebar server, and there's no account to create.