OccupySaaS is a newly launched open-source movement that takes the framing of Occupy Wall Street — the 1% versus the 99% — and applies it to the cloud software industry. The premise: the engineers who built the platforms were laid off in waves between 2022 and 2025, while the platforms themselves kept raising per-seat prices. Now those same engineers are building free, self-hostable replacements under Apache-2.0, starting with identity management and CRM. The first two projects are ZeroAuthy, an Auth0-compatible identity server written in Go, and SalesCompel, a Salesforce-compatible CRM with a PostgreSQL core and Vue frontend. Both are early-stage and say so plainly. The compatibility claim is specific and testable: existing Auth0 and Salesforce client SDKs should work against the open replacements with no code changes. A "compatibility laboratory" runs vendor SDKs against the open server to verify this. The clean-room methodology is the legal backbone. Spec writers and code builders are separated by a firewall. Every project carries a CLEANROOM.md policy. Only public API documentation, open standards like OAuth 2.0 and OIDC, and published SDK behavior are used as inputs. No leaked source code, no decompiled binaries, no confidential information from former employers. AI agents do the implementation from specs alone, with human review at every merge. This is the same legal pattern that produced the Phoenix BIOS clone in the 1980s and has survived decades of case law. The movement's roadmap is public and ambitious. Beyond identity and CRM, proposed targets include docs and wikis, issue tracking, feature flags, observability, and customer support — essentially the full SaaS stack that mid-size companies pay five to six figures per year to access. Categories are picked in the open; anyone can propose a new target by opening a GitHub issue. The per-seat pricing critique has real teeth. Enterprise SaaS vendors have spent a decade optimizing for revenue per employee, turning every new hire into a recurring line item. Auth0 charges per monthly active user. Salesforce charges per seat with tiered feature gates. For growing companies, these costs compound faster than headcount. OccupySaaS frames self-hosting as an escape from that compounding. The harder question is execution depth. Auth0's surface is manageable — OIDC is well-specified, the core flows are documented, and the SDK surface is finite. Salesforce is a different animal entirely. Its API surface spans thousands of objects, Apex execution, workflow automation, reporting, and a decade of accumulated enterprise edge cases. SalesCompel currently offers basic Account and Contact CRUD with limited queries. The distance between that and replacing a production Salesforce instance is measured in years, not sprints. What makes this structurally interesting rather than just another open-source project is the combination of timing, labor surplus, and AI-accelerated development. A million laid-off engineers is a real labor pool. AI code generation genuinely does compress the build cycle for well-specified API servers. And the political framing — protest movement, not startup — changes the incentive structure. There is no Series A to chase, no pivot to enterprise sales, no eventual price hike. The risk is abandonment, not extraction. Whether that framing survives contact with the grinding reality of maintaining enterprise-grade software without funding is the open question.
