Skip navigation
Open source is dead.
0:00 / 9:11

Open source is dead.

Bailey Pumfleet

@pumfleet6.5K followers

Visit on X
2,138 likesDownloadOriginal post

1,570,227 views

Open source is dead. That’s not a statement we ever thought we’d make. Cal.com was built on open source. It shaped our product, our community, and our growth. But the world has changed faster than our principles could keep up. AI has fundamentally altered the security landscape. What once required time, expertise, and intent can now be automated at scale. Code is no longer just read. It is scanned, mapped, and exploited. Near zero cost. In that world, transparency becomes exposure. Especially at scale. After a lot of deliberation, we’ve made the decision to close the core Cal.com codebase. This is not a rejection of what open source gave us. It’s a response to what risks AI is making possible. We’re still supporting builders, releasing the core code under a new MIT-licensed open source project called cal. diy for hobbyists and tinkerers, but our priority now is simple: Protecting our customers and community at all costs. This may not be the most popular call. But we believe many companies will come to the same conclusion. My full explanation below ↓

51 Comments

Comments from the original post on X (Twitter)

  • ThePrimeagen's profile picture

    @ThePrimeagen

    @calcom

    729 likes

  • Simon Willison's profile picture

    @simonw

    @calcom Did you see this piece by @dbreunig? He argues that the cost of locking down software through LLM analysis makes open source MORE valuable now:

    341 likes

  • Bailey Pumfleet's profile picture

    @pumfleet

    @calcom @dbreunig I don’t think that this is wrong - it’s just that this would require us to spend crazy budgets that we don’t have, and overall in our situation proves to be unfeasible. Closing source is the biggest method of risk reduction we can take right now to secure our customers

    50 likes

  • xlr8harder's profile picture

    @xlr8harder

    @calcom Terrible decision. Open source will have the best security story in the long run because the number of bugs are finite. Obscurity won't save you, and it never has.

    277 likes

  • Bailey Pumfleet's profile picture

    @pumfleet

    @calcom How are the number of bugs finite? We ship code constantly, meaning that there’s always going to be the possibility of introducing new bugs, and we need to be in the best possible position to defend against attackers discovering those bugs and exploiting them

    28 likes

  • xlr8harder's profile picture

    @xlr8harder

    @calcom A new equilibrium will be reached that benefits defenders, just like other cybersecurity innovation (e.g. fuzzers) Steady state probably looks something like every line of code gets reviewed in detail by AI experts before commits go through.

    17 likes

  • prom's profile picture

    @citnotcitta

    @pumfleet @calcom > every line of code gets reviewed in detail by ai experts perhaps in a decade when compute gets cheap enough. this isn’t going to happen anytime soon

  • xlr8harder's profile picture

    @xlr8harder

    @pumfleet @calcom i think there's a good chance this will be one of the highest demand uses of ai in the next 6-12 months if the cybersecurity arms race I'm anticipating materializes. i get why Bailey wants to defend from that, it's not wrong to worry about, i just disagree on the tactic

    3 likes

  • Félix Malfait's profile picture

    @_felx

    Love you guys but you’re better than this "open source is dead" shitposting. Security by obscurity has never been a good solution. Closing the repo buys time but at the end of the day if the vulnerabilities remains then AI will also make it much easier to reverse engineer at the API layer / perform mass injection, etc.

    242 likes

  • Bailey Pumfleet's profile picture

    @pumfleet

    @calcom It's not meant to be shitposting. I genuinely believe that AI is getting to the point where almost anything is exploitable, and according to Hex Security, OSS is 5-10x more exploitable than closed source. So there's probably not that much left in OSS that can't be hacked by AI.

    19 likes

  • Pliny the Liberator 🐉󠅫󠄼󠄿󠅆󠄵󠄐󠅀󠄼󠄹󠄾󠅉󠅭's profile picture

    @elder_plinius

    @calcom

    204 likes

  • Bailey Pumfleet's profile picture

    @pumfleet

    @calcom As much as I’d love to have balls, I’d even more love to not be the headline of TechCrunch saying how customer’s calendar data was breached because we didn’t take the option on the table to go closed source

    32 likes

  • Pliny the Liberator 🐉󠅫󠄼󠄿󠅆󠄵󠄐󠅀󠄼󠄹󠄾󠅉󠅭's profile picture

    @elder_plinius

    @calcom cutting your code off from the white hats of the world is a silly way to deal with those fears. but I’m sure security through obscurity will work THIS time, surely!

    66 likes

  • Rafael Aleksandryan's profile picture

    @NoVibeJustOrch

    @pumfleet @calcom Pliny coming in hot, if anything it's actually now going to make things worse. Now, bad actors will be the only ones with the incentive to break it versus security hobbyists and big bounty hunters doing so.

    21 likes

  • Pliny the Liberator 🐉󠅫󠄼󠄿󠅆󠄵󠄐󠅀󠄼󠄹󠄾󠅉󠅭's profile picture

    @elder_plinius

    @EffortDefines @pumfleet @calcom

    18 likes

  • GitHub Projects Community's profile picture

    @GithubProjects

    @calcom Open-source is not dead. You just need to be adaptable.

    154 likes

  • Tudor Golubenco's profile picture

    @tudor_g

    @calcom Funny, we just went the opposite direction:

    92 likes

  • Clayton Kohler's profile picture

    @Oneofinfinity

    Switch from open to closed core does not address the underlying problem though. This makes it harder for code to be exploited, but it will eventually happen regardless with AI over time. We should start planning for the future we start giving access to more information so that that exploitation is not incentivized.

    89 likes

  • Bailey Pumfleet's profile picture

    @pumfleet

    @calcom I agree, and going closed source isn't a complete fix. We're putting in tons of investment to secure in other ways, it's just that going closed source is just one way that we can massively reduce risk.

    25 likes

  • Veros's profile picture

    @boldnames

    @calcom What!!! this is such a backward thinking in my honest opinion, if you can prove your code is secure publicly, then you can always claim that you're secure. In todays world, being open source means being confident and accountable to what you delivered. Not the other way around.

    79 likes