Skip months of integration hell. Use our SDK or open source scheduling package to handle everything calendar, simplify OAuth, build robust booking systems, integrate Google, Outlook, and other calendars with one unified API... 51M+ events created.
Howdyyy PH-Community! 🤠
We're the team behind Recal - the headless infrastructure for everything calendar, especially building custom booking systems.
While most calendar tools force their UI on you, we believe developers should have complete control. Recal provides the calendar integration layer without any frontend constraints - just pure API/SDK that works with Google, Outlook, and other providers.
Whether you're building AI scheduling agents, custom booking flows, or enterprise appointment systems, you get the calendar backend without the baggage. Your UI, your rules, our reliable infrastructure running on Cloudflare's edge network.
Curious what booking experiences you're building! Happy to answer any questions about our architecture or integration approach :)
Great idea of a headless calendar backend! I’ve always wanted to build custom booking UIs without wrestling with someone else's design choices—does your API handle time zone madness out of the box?
@ohansemmanuel We have no vendor lock-in, offer a unified API, and have much better pricing! Also have MCP support 🤖
Report
Love that you are targeting AI scheduling agents bcz that space is growing very fast and most existing APIs are not built with that use case in mind . Great work 👏
Thank you @farhan_nazir55 for the kind words! Yes, and also most of them are not built for scale - e.g., we saw that many new apps are not able to load massive calendar counts to check for availability. We focused on that to allow you to scale easily past 100 calendars with loading times under 1.5 seconds, faster than any competitor we know of for multi-provider scheduling APIs!
Replies
Recal.dev
Agnes AI
Great idea of a headless calendar backend! I’ve always wanted to build custom booking UIs without wrestling with someone else's design choices—does your API handle time zone madness out of the box?
Recal.dev
Congrats on the launch! What’s the typical time-to-integrate for a basic booking flow?
Recal.dev
@arnestrickmann if you build your product already and now want to integrate scheduling: <20min!
@torben_koehler love it!
Remention
Congrats! I guess a question you'll get often is how does it compare with cal.com?
Congrats on the launch again
Recal.dev
@ohansemmanuel We have no vendor lock-in, offer a unified API, and have much better pricing! Also have MCP support 🤖
Love that you are targeting AI scheduling agents bcz that space is growing very fast and most existing APIs are not built with that use case in mind . Great work 👏
Recal.dev
Thank you @farhan_nazir55 for the kind words! Yes, and also most of them are not built for scale - e.g., we saw that many new apps are not able to load massive calendar counts to check for availability. We focused on that to allow you to scale easily past 100 calendars with loading times under 1.5 seconds, faster than any competitor we know of for multi-provider scheduling APIs!
Tab
Recal.dev
@vivek_bezawada2 Thanks, hope you got some good traction!
Such a sick idea guys! Really eager to test it and finally move away from incredibly expensive cal.com. Excited to see where you are heading :)
Recal.dev
great to hear @joelh! Hit us up when you want to start to switch 🚀🙌
This is amazing. Already big fan of resend. This will be a huge game changer as well
Recal.dev
Thanks for the kind words @david_korn1!
LGF!
such a cool tool, gives me resend vibes :)
Recal.dev
@simon_gneuss ^^
I love that there is no vendor lock in. Props for that one!
Recal.dev
Thank you @nico_teufel! That was an absolute priority for us!