本文为原文前 6,000 字符的节选翻译，完整内容请查看原文。

OccupySaaS

OccupySaaS is a protest movement written in code. Laid-off engineers, armed with AI and public documentation, are building clean-room, open-source, drop-in replacements for the platforms that rent our own industry back to us — one seat at a time.

OccupySaaS 是一场用代码书写的抗议运动。被裁员的工程师们利用人工智能和公开文档，正在构建“净室”（clean-room）、开源且可直接替换的替代方案，以取代那些将我们的行业按人头收费、层层盘剥的平台。

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.

2011 年，“占领华尔街”运动质问经济究竟在为谁服务。2026 年，我们针对云服务提出了同样的问题。每家公司赖以生存的工具如今都变成了收费站，而当初构建这些工具的人却被扫地出门。

Every hire, every intern, every contractor — another line item. Infrastructure shouldn’t charge rent by the head.

每位新员工、每位实习生、每位承包商，都成了账单上的一项支出。基础设施不应该按人头收取租金。

Proprietary APIs, export walls and surprise price hikes keep customers captive. Compatible open alternatives set them free.

专有 API、导出限制和突如其来的价格上涨让客户沦为囚徒。而兼容的开源替代方案则能让他们重获自由。

A million engineers were let go while the platforms kept growing. We still know how to ship. Now we ship it in the open.

在平台持续增长的同时，百万名工程师被解雇。我们依然懂得如何交付产品。现在，我们选择在开源环境下进行交付。

We don’t leak, decompile or copy anyone’s code. Every project is rebuilt from public documentation and open standards, with AI doing the heavy lifting on the build side of a strict firewall — then proven compatible against the vendors’ own public SDKs.

我们不泄露、不反编译、也不复制任何人的代码。每个项目都基于公开文档和开放标准重新构建，由人工智能在严格的防火墙内承担繁重的构建工作，随后通过供应商自身的公开 SDK 验证其兼容性。

Public API references, open standards (OAuth 2.0, OIDC, REST) and published SDK behaviour become a written specification. Nothing confidential, nothing leaked, nothing from former employers.

公开的 API 参考、开放标准（OAuth 2.0、OIDC、REST）以及已发布的 SDK 行为被转化为书面规范。不涉及机密，没有泄露，也不包含任何来自前雇主的内容。

Spec writers and builders stay separated. Each repo carries a CLEAN_ROOM.md policy, and provenance is recorded for every fixture and reference.

规范编写者与构建者保持分离。每个代码仓库都包含一份 CLEAN_ROOM.md 政策文件，并且每一项测试装置和参考资料的来源都有据可查。

AI agents implement from the spec alone — contracts first (openapi.yaml), then code, then tests — under human review at every merge.

人工智能代理仅根据规范进行实现——先是契约（openapi.yaml），然后是代码，最后是测试——并在每次合并时接受人工审核。

A compatibility laboratory runs the vendors’ own public client SDKs against our server. If your existing code doesn’t work unchanged, it isn’t done.

兼容性实验室会使用供应商自己的公开客户端 SDK 对我们的服务器进行测试。如果你的现有代码无法在不经修改的情况下运行，那就说明工作尚未完成。

Apache-2.0. Self-hostable. Pluggable storage. No telemetry you didn’t ask for, and no seat counter.

采用 Apache-2.0 协议。支持自托管。支持可插拔存储。没有你未授权的遥测数据收集，也没有按人头计数的限制。

Identity and CRM: the two subscriptions almost every company pays for and almost nobody loves. Both are early, both are public, and both welcome contributors today.

身份验证和客户关系管理（CRM）：这是几乎每家公司都在付费、却几乎没人喜欢的两项订阅服务。这两个项目目前都处于早期阶段，且均已公开，欢迎各界人士参与贡献。

A self-hostable identity server that speaks the Auth0 Authentication API. Point an existing Auth0 SDK at a ZeroAuthy tenant domain and it works with no code changes.

这是一个支持自托管的身份验证服务器，兼容 Auth0 身份验证 API。只需将现有的 Auth0 SDK 指向 ZeroAuthy 租户域名，无需修改代码即可直接运行。

A free, open-source Salesforce replacement with a tenant-isolated Go/PostgreSQL core, a Vue record editor, and a compatibility laboratory that checks behaviour against Salesforce’s public API contract.

这是一个免费的开源 Salesforce 替代方案，拥有租户隔离的 Go/PostgreSQL 核心、Vue 记录编辑器，以及一个根据 Salesforce 公开 API 契约检查行为的兼容性实验室。

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.

这个列表上的每一个类别，在某处都对应着一份月度账单。本运动将公开选择下一个目标——欢迎带来规范、用例或不满。

ZeroAuthy — Auth0-compatible login, tokens and tenants.

ZeroAuthy — 兼容 Auth0 的登录、令牌和租户管理。

SalesCompel — Salesforce-compatible records and REST API.

SalesCompel — 兼容 Salesforce 的记录管理和 REST API。

Team knowledge bases that don’t lock your writing behind a seat licence.

团队知识库，不再将你的文档锁定在按人头付费的许可协议之后。

Tickets, sprints and boards with a compatible API for existing integrations.

工单、冲刺和看板，提供与现有集成兼容的 API。

SDK-compatible flag evaluation you can run next to your own services.

SDK 兼容的标志评估功能，可与你自己的服务并行运行。

Logs, metrics and traces without per-gigabyte ransom notes.

日志、指标和追踪功能，不再有按 GB 收费的“勒索信”。

Help desk, inbox and knowledge base, priced at zero agents.

帮助台、收件箱和知识库，按零坐席定价。

Open an issue and make the case.

提交一个 Issue 并陈述你的理由。

Proposed categories are open for discussion, not commitments. Names of existing products are used only to describe compatibility.

提议的类别仅供讨论，不构成承诺。现有产品名称仅用于描述兼容性。

Occupy Wall Street began on 17 September 2011 in Zuccotti Park, New York City, with a simple frame: the 1% and the 99%. It had no leaders, made decisions in open assemblies, and spread to hundreds of cities.

“占领华尔街”运动始于 2011 年 9 月 17 日的纽约祖科蒂公园，其核心框架很简单：1% 与 99%。它没有领导者，通过公开集会做出决策，并蔓延至数百个城市。

OccupySaaS borrows that spirit and swaps tents for terminals. No marches, no property damage — just working software, published under an open licence, that anyone can run.

OccupySaaS 借用了这种精神，并将帐篷换成了终端。没有游行，没有财产破坏——只有在开源许可下发布、任何人都可以运行的实用软件。

Protesters set up camp in Zuccotti Park in Manhattan’s Financial District.

抗议者在曼哈顿金融区的祖科蒂公园安营扎寨。

Occupy camps and general assemblies appear in cities around the world.

占领营地和全体大会出现在世界各地的城市中。

The camp ends; the language of the 1% and the 99% doesn’t.

营地终会散去，但关于 1% 与 99% 的话语不会消失。

Wave after wave of cuts across the industry while subscription prices keep climbing.

行业内裁员潮一波接一波，而订阅价格却在不断攀升。

The first clean-room rebuild opens its repo under Apache-2.0.

第一个“净室”重构项目在 Apache-2.0 协议下开放了代码仓库。

The second tower. More to come — decided in the open.

第二座大厦已起。更多项目即将到来——一切都在公开讨论中决定。

You don’t need permission, a badge or a manager. You need a laptop and an afternoon.

你不需要许可、工牌或经理。你只需要一台笔记本电脑和一个下午的时间。

Pick an open issue, follow the clean-room policy, open a pull request.

挑选一个开放的 Issue，遵循“净室”政策，提交一个 Pull Request。

Run a release against your real SDKs and tell us exactly where it breaks.

使用你的真实 SDK 运行发布版本，并准确告诉我们它在哪里崩溃。

Turn public docs into precise, testable specifications for the builders.

将公开文档转化为供构建者使用的精确、可测试的规范。

Star the repos, share the site, and tell your CFO what you’re paying per seat.

为仓库点赞，分享网站，并告诉你的首席财务官你为每个坐席支付了多少钱。

Clean-room reimplementation is a long-established way to build compatible software: you work only from public information and independently write your own code. Interoperating with an API is not the same as copying a product. Each project publishes its clean-room policy and source provenance so anyone can check the work. This page isn’t legal advice; if you’re adopting a project for a business, talk to your own counsel.

“净室”重构是一种构建兼容软件的既定方法：你仅根据公开信息独立编写自己的代码。与 API 进行互操作并不等同于复制产品。每个项目都会发布其“净室”政策和源代码来源，以便任何人都能核查工作。本页面不构成法律建议；如果你打算在商业环境中使用某个项目，请咨询你自己的法律顾问。

No. OccupySaaS and its projects are independent and not affiliated with, endorsed by, or sponsored by any vendor named on this site. Product names are used only to describe compatibility.

不。OccupySaaS 及其项目是独立的，与本网站提到的任何供应商均无关联，也未得到其认可或赞助。产品名称仅用于描述兼容性。

Yes, but never with confidential knowledge from a former employer. Contributors work only from public material, and anyone with relevant inside knowledge should stay on the public-spec side of the firewall or sit that project out. When in doubt, read the project’s CLEAN_ROOM.md and ask first.

可以，但绝不能使用来自前雇主的机密知识。贡献者仅使用公开资料工作，任何拥有相关内部知识的人都应留在防火墙的“公开规范”一侧，或者退出该项目。如有疑问，请阅读项目的 CLEAN_ROOM.md 并先行咨询。

Because the giants had thousands of engineers and we have a movement. AI agents let a small group turn a precise spec into working code quickly. Humans write the specs, review every change, and own the result, and compatibility tests against real SDKs decide what counts as done.

因为巨头们拥有数千名工程师，而我们拥有的是一场运动。人工智能代理让一小群人能够迅速将精确的规范转化为可运行的代码。人类负责编写规范、审查每一次变更并掌控结果，而针对真实 SDK 的兼容性测试则决定了什么才算“完成”。

Portability. A Go project compiles to a single self-contained binary, so self-hosting means dropping one file onto a server or into a Docker or Podman image — no installer, no runtime to set up, no tree of dependencies.

可移植性。Go 项目编译为单个自包含的二进制文件，因此自托管意味着只需将一个文件放入服务器、Docker 或 Podman 镜像中——无需安装程序，无需设置运行时，也没有复杂的依赖树。