Cal.eu shuts down Nov 1 - wrote up a self-hosted escape route

Disclosure first: I'm building Calnode (Apache-2.0 self-hosted scheduler), which is one of three options below. The other two are legit. Cal.com is shutting down Cal.eu on November 1, 2026. Their own words: "Cal.eu will remain available until November 1, 2026." New signups are already closed (the signup page says so today). If you picked Cal.eu so meeting data stays in the EU, that ends in ~45 days. Enterprise contracts get extensions; everyone else gets an export and a deadline. Notice is in four languages, so it's done, not rumoured. Three options as I see it: Take the migration to Cal.com International. Least work, keeps your setup. Loses EU residency. Fine if nobody ever asked where the data lives. Move to another EU-hosted scheduler. eualternative.eu lists ten. Works, but it just moves the problem. Next shutdown, same situation. Self-host. The only option where nobody can send you a shutdown notice. For option 3, the short version of what I'd do: Export everything from Cal.eu now, not late October. Event types, bookings, team lists. Calnode is one static Go binary + embedded SQLite. No Redis, no Postgres, no API server. One docker run , data in ./data . Set an encryption key, point Litestream at a backup target. Rebuild event types and booking links (the manual hour), wire confirmations + reminders. Repoint webhooks (HMAC-signed, API-configured) or use the built-in MCP server if agents book for you (stdio local, HTTP remote, role-scoped tools). Cut over one event type at a time. Keep Cal.eu read-only till November so old links keep working. Full writeup with links here: dev.to/shockalotti/caleu-is-closing-on-...1-here-is-your-migration-playbook-26la Happy to answer self-hosting questions in the comments - Calnode or otherwise.