OccupySaaS engineers compile clean‑room, AI‑generated SaaS replacements on open‑source platforms.
OCCUPYSAAS LAUNCHES OPEN-SOURCE REPLACEMENTS FOR AUTH0 AND SALESFORCE
*Laid‑off engineers are rebuilding SaaS platforms with AI and clean‑room methods. The movement promises drop‑in, self‑hosted alternatives free of per‑seat taxes.*
Layoffs swept through the cloud industry in early 2026, leaving a million engineers without jobs while the platforms they built kept expanding. Those engineers regrouped under the banner OccupySaaS, a code‑first protest that promises to rebuild the very services that dismissed them. Using AI, public documentation, and a strict clean‑room policy, they are delivering open‑source, drop‑in replacements that run on any server and charge no per‑seat fees. The movement launched with an estimated start date of October 2026 and immediately released two flagship projects: ZeroAuthy, an Auth0‑compatible identity server, and SalesCompel, a Salesforce‑compatible CRM. Their goal is to turn the cloud from a rent‑by‑head model into a self‑hosted commons.
What is OccupySaaS and how does it work?
OccupySaaS is a protest movement born from mass layoffs in the cloud industry. Engineers use public API docs, open standards like OAuth 2.0 and OIDC, and AI agents to rebuild services behind a strict firewall. Every repository carries a CLEAN_ROOM.md policy that records provenance and forbids any leaked or proprietary code. Compatibility is verified against vendors' public SDKs; if existing client code fails unchanged, the build is not released. All code is published under Apache‑2.0, self‑hostable, and free of telemetry or seat counters. The project launched with an estimate date of October 2026.
Which SaaS replacements have been released?
The first two occupied towers are an identity server and a CRM. ZeroAuthy is a Go‑based, Auth0‑compatible identity service that supports OIDC discovery, JWKS, multi‑tenant domains, and standard grant flows. It runs on SQLite, PostgreSQL, MySQL, or gRPC plugins and passes verification with auth0‑spa‑js, auth0‑react, and nextjs‑auth0. SalesCompel is a Go/PostgreSQL core with a Vue record editor that mimics Salesforce's public API contract. It offers CRUD for Account and Contact objects, external‑ID upsert, bearer authentication, and an OpenAPI 3.2 spec. Both projects are open‑source, clean‑room built, and verified against the original vendors' public SDKs.
Why are the engineers rebelling?
The grievance is simple: cloud tools have become toll booths. Per‑seat pricing adds a line item for every hire, intern, or contractor, turning growth into a tax. Proprietary APIs, export walls, and surprise price hikes lock customers into vendor ecosystems. OccupySaaS argues that the software built by the 99 % belongs to the 99 %. By delivering drop‑in, open alternatives, the movement aims to eliminate per‑seat taxes and lock‑in, returning control of data and servers to users.
How will OccupySaaS expand its occupation map?
The movement publishes an occupation map that lists every SaaS category as a monthly invoice somewhere. After identity and CRM, the roadmap includes Docs & Wikis, Issue Tracking, Feature Flags, Observability, and Customer Support. Proposals are open to the community; any target can be added by opening an issue and making a case. Names of existing products are used only to describe compatibility, not to claim ownership. The model mirrors Occupy Wall Street’s 2011 Zuccotti Park protests, swapping tents for terminals and marching on code instead of streets.
Frequently asked questions
When did OccupySaaS launch?
OccupySaaS estimates its launch in October 2026.
What license does OccupySaaS use for its code?
All OccupySaaS projects are released under the Apache‑2.0 license.
How many engineers claim to have been laid off?
The movement states that a million engineers were let go while the platforms kept growing.
OccupySaaS turns a wave of layoffs into a coordinated engineering strike against SaaS lock‑in. By publishing clean‑room, AI‑generated code under an Apache‑2.0 licence, the movement forces vendors to confront a growing open‑source alternative that can be swapped in without code changes. If the occupation spreads to the next category on the map, the per‑seat tax model could face a practical, community‑driven demise. The next target is only a proposal away.
Sources: Hacker News