Peer_Rich

cofounder here

going closed source does not mean we are not fighting fire with fire

we are using a handful of internal AI vulnerability scanners for months now

being open source simply reduces risk by 5x to 10x according to several security researchers we are working with https://cal.com/blog/continuous-ai-pentesting-vulnerability-...

hey cofounder here. since it takes my 16 year old neighbors son 15 mins and $100 claude code credits to hack your open source project

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

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

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

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

thank you for supporting us! The CalDAV integration alone took a ton of engineering hours because every provider has implemented this protocol differently

thank you @brajeshwar, we're happy to keep our individuals plan free forever thanks to the growing enterprise business

aww thank you man! really means a lot to hear @zcesur

hey @ushakov, can you send me an email to peer@cal.com, can i look into your 2FA issue?

hey hey, cofounder of cal.com here. @tarunmuvvala let me know if you wanna chat about your use case! peer@cal.com

its great to offer bounties to our cal.com community!

plausible wrote a good article about limiting it with AGPL https://plausible.io/blog/open-source-licenses

mostly on GitHub and Slack: https://cal.com/slack

you can. the hint is non-blocking

Hey, Peer here, Co-Founder of Cal.com. Wow this has been overwhelming! Shoutout to all the nice people in the comments supporting us. Also thank you all for providing valuable feedback, reporting bugs and more. The beauty of OSS that everyone can contribute, participate and help.

We're ending this day adding the new "badge of honor" of hackernews #1 to our README: https://github.com/calcom/cal.com/pull/6682

Best, Peer

BAAs are not a problem once the company has HIPAA compliance itself

which one is missing?

sure! peer@cal.com or cal.com/peer

Hey josh, cal.com does support paid events

which features would you throw out the window?

it'll show in the input box when you write it

yikes