OccupySaaS aims to remake Auth0 and Salesforce with AI

Founded in October 2026, OccupySaaS aims to rebuild open source alternatives to Auth0 and Salesforce. The collective relies on AI agents, but its software remains incomplete and far from widespread enterprise use.

OccupySaaS, a collective launched in October 2026, aims to rebuild open source alternatives to subscription-based software using AI, starting with Auth0 and Salesforce. The group echoes a classic SaaS critique: dependence on vendors, per-user billing, and complicated switching between services. For now, it mainly offers a technical demonstration, not a ready-to-use production replacement.

Refaire du SaaS sans payer la facture, ou presque

The movement's slogan is straightforward: "They laid us off. We rebuild their SaaS." OccupySaaS advocates an open source, self-hosted, license-free approach, aiming to break dependence on platforms that often lock companies in through their APIs, integrations, and migration mechanisms. The name echoes Occupy Wall Street, born in New York in 2011, but the target here is much more technical than financial.

The collective does not specify the former employers of its initiators nor the reasons for their departure. No public information confirms that they worked at the targeted vendors or that their departure was due to AI-related layoffs. This is a significant point, as the project's activist dimension also relies on this narrative.

Une méthode de « clean room » sous supervision humaine

OccupySaaS claims to rely on AI agents capable of generating code from technical specifications written by developers. The produced code then undergoes human review. The claimed approach is that of the clean room, or white-box reimplementation: reproducing software functionality from public documentation, open standards, and observable API behavior, without using proprietary code or confidential information. In short, you observe how the machine runs but don’t steal the blueprints under the hood.

This method aims at a concrete goal: enabling small teams to move faster while maintaining sufficient compatibility with existing uses. Compatibility tests rely on vendors’ public development kits so that some applications and integrations continue to work after switching solutions. The promise is appealing, but it does not equate to automatic migration.

Deux chantiers visibles: ZeroAuthy et SalesCompel

The first project, ZeroAuthy, was made public on October 14, 2026. Developed in Go, it seeks to replicate the functions of Auth0, Okta’s identity and access management platform. Its first release candidate, published on November 4, supports several authentication mechanisms, user management, and some administration APIs. The software also obtained OpenID certification for three OpenID Connect profiles, though this does not constitute a comprehensive security validation.

The second project, SalesCompel, was released on October 15, 2026, to compete with Salesforce in the CRM market. It is based on Go and PostgreSQL, with a record editor developed in Vue.js. Its current core manages accounts, contacts, some queries, and part of Salesforce’s APIs. However, it does not include Apex code, Flow automations, or Salesforce’s custom interfaces, which remain outside the scope of this first version.

La compatibilité, oui. La migration complète, non.

Both software packages are distributed under the Apache 2.0 license, allowing their use, modification, and commercial exploitation. On paper, this opens the door to internal deployments or external contributions. In practice, their functional coverage remains incomplete, and the collective itself states that its tools are not ready for widespread production use.

The core issue concerns the reversibility of information systems. If an alternative replicates the same APIs as proprietary software, some applications can continue running without major redesign. But in a Salesforce environment, customizations, automations, and third-party extensions still need to be redone. Technical compatibility alone is therefore insufficient to erase the complexity of switching out.

Le Data Act change le décor, mais pas la mécanique

The initiative arrives as the European Union pushes further for data portability. Effective since September 12, 2025, the Data Act aims to facilitate changing data processing service providers, especially in the cloud. Starting January 12, 2027, switching fees targeted by the regulation, including data exit fees, must be eliminated.

OccupySaaS thus fits into a regulatory context more favorable to migrations, but its model does not solve everything. Self-hosting requires managing maintenance, updates, monitoring, backups, and security patches—tasks particularly sensitive for an authentication service. The absence of license fees does not mean absence of cost. The cloud loves the fine print; invoices, less so.

Un collectif encore fragile

OccupySaaS is now seeking new contributors and mentions future targets such as collaborative documentation, incident tracking, and customer support. For now, nothing indicates that this effort has reached a sufficient size to challenge established platforms in complex enterprise environments.

As of November 8, 2026, the collective’s GitHub organization shows no public members, preventing assessment of its actual base. Its two projects give an idea of the method, but not yet of robustness. The movement has put forward a simple idea: if proprietary software locks too tightly, sometimes you have to rebuild it from scratch. The question remains how long a community can maintain this pace without turning into a permanent worksite.

Key points

  • OccupySaaS was launched in October 2026.
  • ZeroAuthy has been public since October 14, 2026.
  • SalesCompel was released on October 15, 2026.
  • The Data Act has been in effect since September 12, 2025.
  • From January 12, 2027, exit fees must disappear.
  • The collective has four public repositories on GitHub as of November 8, 2026.

By the numbers

  • 3 OpenID Connect profiles — certification obtained by ZeroAuthy, November 2026.
  • 4 public repositories — OccupySaaS GitHub organization, November 8, 2026.
  • 2 projects — ZeroAuthy and SalesCompel, publicly accessible in November 2026.
  • 1 million — engineers laid off mentioned by the collective, mobilization figure.

To read