Two-way sync, your rules
Changes flow both ways — new events, reschedules, and deletions, detected reliably. Or set any pair one-way: source→target or target→source.
Your work Outlook and your personal Google should agree on where you actually are. CalPair keeps them in sync — both directions, including moves and deletions. Hosted in Europe. We do not persist event titles, notes, locations, or attendees.
Personal Google on one side, work Outlook on the other — you're typing every meeting twice, missing the cancellations that never crossed over, and explaining conflicts you shouldn't have. Most sync tools copy an event once and forget it. CalPair keeps both sides aligned, continuously.
Work meetings only live in Outlook. Personal stuff only lives in Google. Every time you book something, you're mentally checking the other calendar — and often missing it.
Each dot shows where an event was created: green for Google, teal for Outlook. Keep those colors in mind for the next step.
Changes flow both ways — new events, reschedules, and deletions, detected reliably. Or set any pair one-way: source→target or target→source.
Connect several Google and Microsoft accounts — Google↔Outlook, Google↔Google, or Outlook↔Outlook across tenants. Run as many pairs as your plan allows.
Mirror appointments as anonymous “Busy” blocks. Your work calendar never reveals that dentist appointment.
Hosted on German infrastructure. No analytics, no third-party trackers. Full data export and one-click account deletion.
We store sync mappings and hashes — never event titles, attendees, locations, or notes. OAuth tokens are encrypted at rest.
Publish selected calendars as a subscribable, busy-only availability feed — ICS / webcal or a PIN-protected web page. Share when you're free, never what you're doing.
Each client gets its own Outlook account. CalPair makes sure none of them double-books another — and clients never see each other’s names on the calendar.
Personal pickup at 16:00 blocks the work calendar so colleagues don’t book a meeting on top. They see “Busy” — not why.
Birthdays, holidays and the babysitter slot show up on both phones. Everything else stays where it belongs.
Most calendar tools treat your events as training data, analytics fuel, or somebody's pitch deck. We don't. CalPair only stores what it needs to sync — encrypted OAuth tokens, internal IDs, and content hashes. The actual contents of your events — titles, attendees, locations, notes — never touch our database. We don't train AI on your data, we don't sell it, we don't share it with anyone. Servers in Germany, EU jurisdiction, no Atlantic round-trips.
Open Agenda publishes your availability as a clean, subscribable calendar — colleagues, clients, or family see your free-busy times and nothing else. It's not a booking page and not a Calendly clone: no one schedules on top of you, they just see when you're taken. The same privacy architecture, pointed outward.
Available on Basic (1 feed) and Pro (3 feeds).
“Business” and “Private” are labels you choose — one per calendar.
An ICS / webcal link for any calendar app, or a PIN-protected web page — the other side needs no CalPair account.
Name each calendar yourself: “Business”, “Private”, or simply “Psssst”… Viewers see only the label and the time, never titles or notes.
A built-in switcher converts each block, so a client in New York and a colleague in Berlin both read it right.
PIN plus a 256-bit token. Revoke or regenerate the link anytime — the old one dies instantly.
Sign in with Google or Microsoft — no new password to remember.
Connect your calendars via OAuth. We store encrypted tokens, nothing else.
Pair them up and pick a direction. CalPair runs quietly in the background.
We sync calendars. And we're exceptionally good at it.
That's the whole product.
Limits and monthly sync allowance shown on signup. Launch pricing.
Honestly? No. Even if we wanted to. The database only holds mapping IDs and SHA-256 hashes — enough to know that event X on your side matches event Y on the other, but not what's in either. The contents of your meetings never leave Google or Outlook.
Your account data — encrypted OAuth tokens, sync mappings, and content hashes — is stored on German servers (Hetzner, Falkenstein), under EU jurisdiction. Event titles and details are processed in memory for sync only and are not persisted in our database. Google and Microsoft Calendar APIs are part of the sync flow; their traffic may involve transfers to the United States, covered by the EU-US Data Privacy Framework and SCCs where applicable.
You pick the strategy per pair: last-write-wins, source wins, target wins, or origin wins.
No. CalPair uses OAuth with Google or Microsoft.
One click in settings. Account deletion wipes your data and is logged for audit.
Google Calendar (personal and Workspace accounts) and Microsoft Outlook via Microsoft 365 or Exchange. You can mix and match — Google↔Outlook, Google↔Google, or Outlook↔Outlook across different accounts or tenants.
Yes — that's Open Agenda. Publish selected calendars as a subscribable feed (ICS / webcal) or a PIN-protected web page that shows only “Busy” blocks — never titles, attendees, or notes. Give each calendar its own label, and revoke or regenerate the link anytime; the old one stops working immediately. It's read-only availability, not a booking page. Available on Basic (1 feed) and Pro (3 feeds).
Free plan syncs up to every 15 minutes. Basic brings it down to every 3 minutes. Pro syncs every minute and supports optional push webhooks for near-instant updates when an event changes.
CalPair detects it and propagates the change. Deletions are reflected on the other side. Moves — time or date changes — are tracked via content hashing, not just creation date. Most sync tools miss these; that’s a core problem CalPair was built to solve.
Free forever — one sync pair, two calendar accounts, no credit card. We'd rather earn the upgrade than auto-bill into it.
OAuth sign-in · no credit card · cancel anytime