OccupySaaS

Anger over AI-driven layoffs and SaaS “enshittification” is fueling OccupySaaS, a project that uses large language models to rapidly clone proprietary platforms like Auth0 and Salesforce as free, open-source drop-in replacements. Supporters frame it as turning big tech’s own tools against them and lowering SaaS prices or margins, while critics argue it misunderstands why companies pay for SaaS (support, liability, integration, and sales), duplicates existing FOSS efforts, and may ultimately strengthen AI vendors more than it hurts incumbent software giants. Many doubt its commercial or political impact, seeing it as more symbolic “revenge coding” than a viable path to structural change.

Overall Concept & Motivation

  • OccupySaaS proposes using AI and open source to build 1:1 drop‑in replacements for major SaaS products (Auth0, Salesforce, etc.) as a response to AI-driven layoffs and “enshittified” platforms.
  • Some see it as poetic revenge: using the same AI that displaced workers to undercut the companies that fired them.
  • Others argue the framing is incoherent: replacing paid SaaS with free clones destroys more tech jobs and doesn’t address underlying economic or political causes.

Protest vs. Practicality

  • Many commenters say this is more symbolic than effective protest; real pressure on capital would need mass adoption or non-technical organizing.
  • Comparisons to Occupy Wall Street are frequent; some see the name as inspiring, others as a reminder of a failed movement.
  • Several argue that anger/vengeance is weak long-term fuel for a sustainable product or ecosystem.

Misunderstanding of SaaS Value

  • Strong theme: the “second S” (service, support, liability, reliability, security updates, ecosystem, contracts) is what enterprises actually pay for, not just the code.
  • Skepticism that companies will entrust critical systems (IDP, CRM) to “vibe‑coded” AI-generated clones lacking mature support and ecosystem.
  • Migration risk, vendor accountability, and “nobody gets fired for buying Salesforce” are cited as powerful moats.

AI Use: Irony, Risk, and Potential

  • Some praise using subsidized LLM tokens to “liberate” proprietary software and view it as a form of wealth redistribution or activism.
  • Others see it as doing free RLHF and revenue for AI labs, entrenching bigger, worse monopolies (OpenAI, Anthropic, etc.).
  • Concerns include AI slop quality, long tail of bug-fixing and UX polish, and cognitive harms or environmental costs.

Overlap with Existing FOSS & Licensing Debates

  • Many note there are already FOSS alternatives to most targets; this looks like “FOSS with AI branding.”
  • Questions why not contribute to mature projects instead of starting new ones; some attribute this to ego, NIH, or desire for donations/branding.
  • Disagreement over Apache 2.0: some want strong copyleft to prevent re-SaaSification; others prefer permissive licensing to maximize adoption.

Outlook

  • Some expect an “AI rewrite movement” and more open alternatives regardless of this specific project.
  • Majority sentiment in the thread is skeptical that OccupySaaS itself will achieve broad enterprise adoption or meaningful systemic change.