I saw some discussion about this elsewhere. Here is how the project describes itself:

OccupySaaS is a protest movement in code: laid-off developers building clean-room, open-source, drop-in replacements for the SaaS giants. First up: ZeroAuthy (Auth0) and SalesCompel (Salesforce).

In 2011, Occupy Wall Street asked who the economy was really working for. In 2026 we’re asking the same question about the cloud. The tools every company runs on are now toll booths — and the people who built them were shown the door.

Two towers occupied.

Identity and CRM: the two subscriptions almost every company pays for and almost nobody loves. ZeroAuthy has shipped its first release candidate, SalesCompel is still early, and both welcome contributors today.

Who’s next?

Every category on this board is a monthly invoice somewhere. The movement picks the next target in public — bring a spec, a use case, or a grudge.

  • skisnow@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    The sentiment is all very well and good, but I’m pretty confident that we’d get better results if they put their energy into improving the many, many mature open source projects that already exist to do the same things.

  • Ghoelian@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    6 days ago

    Can you really call it clean room when you don’t know exactly what the ai was trained on? There’s gotta be some ghidra decomp of these programs in the big providers’ training data.

  • DeckPacker@piefed.social
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    Wow, you told AI to build you two slop code bases and a website. This is embarrassing.

    This “movement” will last one month max, I am sorry, but this is stupid and will change nothing.

  • floofloof@lemmy.ca
    link
    fedilink
    English
    arrow-up
    1
    ·
    7 days ago

    Copying my comment from another thread on this story:

    A lot of that AI will presumably be rented from the companies that persuaded your boss to fire you and use their tools instead. So it’s an odd kind of protest, that starts by paying those companies more money.

    I do like the idea of software engineers collectivizing and prioritizing work on projects that don’t have good enough open-source options, particularly where it targets the nastier companies in the SaaS space. But there’s nothing new about that work; what’s new is that we have a lot of people motivated to take software in a new direction, who miss being able to take pride in the quality of their work, and who may be more receptive to acting collectively than these people have traditionally been. I know whenever I’ve proposed any kind of collective stance at my workplaces I’ve been met with blank stares, silence, and developers nervously looking at their feet. Maybe that can change when more people have recent experience of what happens when you don’t act together.

    If we want to do something new, how about worker-owned cooperatives which actually offer good-quality software and support with ethical terms of use? Build it and sell it to the companies paying for SaaS, and make your software and support deal more attractive than the one they’re being gouged for. The support is particularly important when anyone can dash off some software using AI. Make your company worker-owned, nonprofit and cheap, market it professionally, offer good support and maintenance, and make a living doing it.

  • blueryth@lemmy.world
    link
    fedilink
    English
    arrow-up
    1
    arrow-down
    1
    ·
    7 days ago

    I think the idea behind a movement like this is good. This implementation worries me. When the plan is to have the AI do the “heavy lifting” from the get-go, this smells a lot like vibes. Even if we look past the ethics, this seems risky for bedrock systems like IAM. And even then, the master’s tools will never dismantle the master’s house. I wish them luck.

    I wonder what these devs think of OpenStack

    • urushitan 漆たん@kakera.kintsugi.moe
      link
      fedilink
      English
      arrow-up
      2
      ·
      edit-2
      6 days ago

      Especially because of scale. “Salesforce” is an incredibly complex group of many software applications with 80,000+ employees and many of their engineers have “unlimited” ai spend. So instead of “we’re rebuilding salesforce” they need to decompose salesforce into its individual elements and see what people need. And even when you have those products decomposed, you need to have swathes of people that understand the business needs that each one fulfills. My title is “Lead Architect: AI” for a medium sized SaaS company and our software has very specialized requirements across a number of verticals. And while salesforce is in no way a direct competitor, I know the sort of things that they’re building and the effort to “vibe code salesforce” is a Herculean task, and all the engineers at my company, many of whom have Ivy League computer science degrees, couldn’t do that in 5 years, if we dropped everything and tried, with unlimited budget for LLM assisted work.

      • blueryth@lemmy.world
        link
        fedilink
        English
        arrow-up
        1
        ·
        6 days ago

        I worry that every level has this misunderstanding, that “Salesforce” is a monolithic system that can be remade if only we pass a comprehensive test suite. Salesforce does not have 80k+ developers making a singular monolithic product. They have 80k+ employees servicing the sales demands of a massive number of customers. Excel is a perfectly fine CRM if you only have a handful of customers.

        Hope you’re staying sane in the SaaS landscape. I hear a lot of horror stories.