hey cofounder of cal.com here. the plan has always been to: 1. start and go fast with a mono repo and trpc fullstack api to understand and learn the fastest. once we knew what we need, we were able to build an external facing API. we wanted to be very clear to externals that using our “trpc api” is with caution due to undocumented breaking changes. a lot of companies have an internal API + external API (built later)
We have been in the feedback & survey market for many years now, and especially with the new privacy regulations (e.g. GDPR) and the new rise of Open Source, we often wondered why there was no easy to use Open Source solution that you could embed into your own technical infrastructure and also customize the way you need.
So we built a first MVP as a hobby project and got such a great response from the open source community and early customers that we decided to go all in at the end of last year .
hey, peer here, cofounder of cal.com. We are quite fortunate to have a growing enterprise business that is subsidising the free plan.
we will never raise prices for the free plan, free stays free, especially since it's open source which means if we were to raise, it would compete with the self-hosted product and we really dont want that
rest assured, we are comfortable providing a free product with enterprise customers
