Acuity is certainly a good option. We ultimately built our own because we knew it would be an on going feature we would need in the businesses that we were helping and we wanted to be able to own the stack ourselves. For long term cost savings as well as control over features that could be added in the future.

Great questions. It's targeted at dev teams wanting to build their own custom experiences on the frontend without having to deal with the complications of a scheduling backend. This could be anything from calendar functionality in their application to a platform that handles bookings for an office, etc. While assisting several startups get their product built, we ran into a need for something like this which drove us to build this as a standalone service. Figured others might find it useful as well!

Good question. Currently the value here is cost vs api usage compared to something like cal.com. Similar usage there would be significantly higher. That said, they also have some additional features that we don't have yet. We are actively working towards new features to close the gap! Thanks for checking it out.

:D