Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Cal.diy: open-source community edition of cal.com

github.com

Post reply on HN
Print view View original

1–10 of 75 posts

Re: Cal.diy: open-source community edition of cal.com

#4

Post by raphaelcosta »

It’s curious what they said in the email they sent me about the OSS version.

------

A few important changes to note:

We will no longer provide public Docker images, so your team will need to build the image yourselves.

Please do not use Cal.diy — it’s not intended for enterprise use.

Re: Cal.diy: open-source community edition of cal.com

#5

Post by FlamingMoe »

From the docs, "It is strictly recommended for personal, non-production use."

Wow what a 180 from just a year ago when their blog said, "For companies that handle sensitive information, deploying open-source scheduling software on-premises can offer an extra layer of security. Unlike cloud services controlled by external vendors, on-prem installations let teams maintain full ownership of their infrastructure. " ¹

I just cannot trust a company that does a bait and switch like this.

¹ https://cal.com/blog/open-source-scheduling-empower-your-tea...

Re: Cal.diy: open-source community edition of cal.com

#6

Post by hrimfaxi »

FlamingMoe wrote: post #5

From the docs, "It is strictly recommended for personal, non-production use." Wow what a 180 from just a year ago when their blog said, "For companies that handle sensitive information, deploying open-source scheduling software on-premises can offer an extra layer of security. Unlike cloud services controlled by external vendors, on-prem installations let teams maintain full ownership of their infrastructure. " ¹ I j…

[dead]

Re: Cal.diy: open-source community edition of cal.com

#8

Post by Ethee »

FlamingMoe wrote: post #5

From the docs, "It is strictly recommended for personal, non-production use." Wow what a 180 from just a year ago when their blog said, "For companies that handle sensitive information, deploying open-source scheduling software on-premises can offer an extra layer of security. Unlike cloud services controlled by external vendors, on-prem installations let teams maintain full ownership of their infrastructure. " ¹ I j…

I think this is less a bait and switch and more just a legal liability shield. They're not saying you 'cant' use it that way. They just don't recommend you do, and they won't support you at all for doing so. Which I think is completely fair. Also, these two things aren't in contradiction. Deploying on prem does offer more security, but then it's up to you to use it correctly.

Re: Cal.diy: open-source community edition of cal.com

#9

Post by loa_in_ »

Ethee wrote: post #8
FlamingMoe wrote: post #5

From the docs, "It is strictly recommended for personal, non-production use." Wow what a 180 from just a year ago when their blog said, "For companies that handle sensitive information, deploying open-source scheduling software on-premises can offer an extra layer of security. Unlike cloud services controlled by external vendors, on-prem installations let teams maintain full ownership of their infrastructure. " ¹ I j…

I think this is less a bait and switch and more just a legal liability shield. They're not saying you 'cant' use it that way. They just don't recommend you do, and they won't support you at all for doing so. Which I think is completely fair. Also, these two things aren't in contradiction. Deploying on prem does offer more security, but then it's up to you to use it correctly.

It being open source also allows you to actually have a read of the software and guarantee things yourself, which is the harder better path anyway.
Post reply on HN