Calnode
Self-hostable Calendly + Zoom replacement — single Go binary
I built Calnode because every self-hosted Calendly alternative I tried needed Postgres + Redis + Node.js + Docker Compose just to deploy a scheduling tool. That's a 1GB+ stack to book a meeting.
So I wrote it as a single static Go binary + a SQLite file. ~20MB. Runs on a $5/mo VPS. The whole thing deploys in about 30 seconds.
What it does:
- Booking pages with calendar sync (Google, Outlook, CalDAV)
- Video calls (self-hosted LiveKit under the hood — no Zoom)
- Recording in your own S3 bucket
- AI booking in-page (point it at local Ollama, Azure OpenAI, any OpenAI-compatible endpoint — your data never leaves your infra)
- Native MCP server (your agents can schedule on behalf of users)
Why this matters right now: EU AI Act Article 50 hits Aug 2, 2026. AI booking assistants on Calendly or Cal.com SaaS tiers aren't compliant by default - the AI sends user data to third-party LLMs, and the booking data lives on vendor infrastructure. Self-hosted + BYO-LLM is the cleanest path.
Apache 2.0. ~25k lines of Go. Auditable in a 20-minute review. The audit kit (claims.yaml + AUDIT.md) ships in the repo.
I'm a founder building this with my partner Alex Makarski — we're a distributed team across the US, Canada, New Zealand, and India. The plan is to keep it open source and offer managed deployment + integration services for regulated industries (healthcare, finance, legal, government) where self-hosting is required but the team doesn't have the bandwidth to wire it up themselves.
If you've migrated off Calendly or are evaluating Cal.com self-hosted, I'd love to hear what's missing in either. Or if you're a regulated-industry IT team evaluating scheduling tools, I'm doing free 20-minute scoping calls this week.
Repo: github.com/Calnode/calnode
Site: calnode.com
Article 50 reference: artificialintelligenceact.eu/article/50/
5 Comments
The interesting positioning isn't "lighter than Calendly." It's giving regulated teams ownership of both scheduling and AI. I'd keep validating whether customers are buying a smaller deployment or confidence they can adopt AI scheduling without creating compliance or infrastructure dependencies.
Thanks for your feedback!
One thing I'd keep watching is whether customers eventually describe the product as giving them more control or giving them fewer things they need to control.
Those sound similar, but the second is often what people are actually buying when compliance and infrastructure become part of the decision.
Interesting. Thank you for the insight - I'm VERY curious to see how people start using this and their feedback. Now that you've given me this tidbit, I'll be paying particular attention to that piece.
I'm glad it was useful.
Reading your reply gave me one more thought about why customers often describe those two outcomes differently after they've actually adopted a product like this. I'd rather explain it in the context of what you're building than reduce it to a few comments.
If you're interested, what's the best email to reach you on?