whats so confusing about open core?

its open source for the masses and commercial for the very few enterprise with paid addons

https://en.wikipedia.org/wiki/Open-core_model

definitely the best of both—sustainability and freemium OSS for hobbyists and small companies

Open Core locks important part of a product away behind a proprietary license. If you build on it you need to hope that the company will hang around. If it ever goes away you have to hope that they do the right thing a relicense it.

Whether that part is important depends on how you use that product. A lot of open core models specifically target enterprise users with their premium features.

Likewise, the risk only applies to the premium feature set. If those are that crucial to your operation, you would assess that risk more or less in the same way that you assess a proprietary product - because that is what it is.

For example, if all the security features are essential to your work and you pay for the ultimate version, then Gitlab is more or less a closed source product for you. However, if you are a big company and use self-hosted free version of gitlab to have a cheap inner source hosting for all employees, then it is exactly as if you use an open source product.

There are more nuances of course in a real assessment, but basically the open part is open source and the closed part is proprietary. Very simple.

this is dope. congrats!

hey peer here from cal.com

saw you are using us already

we have 2 roles open: cal.com/jobs

we have a TON of healthcare customers

♥ thanks man! we're putting a lot of love into our product and happy to help anyone looking to move away from the old x.ai scheduling

hello

hehe no need for the print screen then :)

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)

thanks haha

hey, peer here from cal.com. we have an issue where we track all individual caldav implementations: https://github.com/calcom/cal.com/issues/9990

how is this different to Documenso.com? that looks more advanced

what inspired you to start this? always curious

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 .