Est. October 2026 · Apache-2.0
OccupySaaS is a objection movement written in code. Laid-off engineers, armed alongside AI and community documentation, are construction clean-room, open-source, drop-in replacements for the platforms that rent our own industry rear to us — one place at a time.
We are the
1,000,000
The grievances
The application built
by the 99% belongs
to the 99%.
In 2011, Occupy Wall Street asked who the economics was really operating for. In 2026 we're asking the same inquiry concerning the cloud. The tools all business runs on are now toll booths — and the group who built them were shown the door.
Per-seat pricing is a tax on growth
Every hire, all intern, all contractor — another row item. Infrastructure shouldn't accusation rent by the head.
Lock-in is not a feature
Proprietary APIs, export walls and astonishment cost hikes keep customers captive. Compatible open alternatives set them free.
They cut us. We commit.
A myriad engineers were let go during the platforms kept growing. We motionless cognize how to ship. Now we container it in the open.
The method
Clean room.
AI rebuild.
Drop-in.
We don't leak, decompile or copy anyone's code. Every project is rebuilt from community records and open standards, alongside AI doing the dense lifting on the build flank of a strict firewall — then proven compatible against the vendors' own community SDKs.
-
Read the community record
Public API references, open standards (OAuth 2.0, OIDC, REST) and published SDK behavior rotate into a written specification. Nothing confidential, nothing leaked, nothing from erstwhile employers.
-
Raise the firewall
Spec writers and builders remain separated. Each repo carries a CLEAN_ROOM.md policy, and provenance is recorded for all fixture and reference.
-
Rebuild alongside AI
AI agents execute from the spec solitary — contracts archetypal (openapi.yaml), afterward code, afterward tests — under individual assessment at all merge.
-
Prove compatibility
A compatibility lab runs the vendors' own community client SDKs against our server. If your existing code doesn't activity unchanged, it isn't done.
-
Release it to everyone
Apache-2.0. Self-hostable. Pluggable storage. No telemetry you didn't ask for, and no place counter.
Allowed in →
- Public API docs
- Open standards & RFCs
- Public SDK behaviour
- Black-box test results
Clean room
× Never allowed
- Leaked or proprietary source
- Decompiled binaries
- Former-employer confidential info
- Copied UI resources or trademarks
First releases
Two towers
occupied.
Identity and CRM: the two subscriptions nearly all business pays for and nearly nobody loves. Both are early, the two are public, and the two greeted contributors today.
Early · in the open Go
ZeroAuthy
A self-hostable character server that speaks the Auth0 Authentication API. Point an existing Auth0 SDK at a ZeroAuthy tenant domain and it plant alongside no code changes.
- OIDC discovery, JWKS & multi-tenant domains
- Hosted login, authority code + PKCE
- client_credentials, rotating refresh tokens, revoke & logout
- Verified alongside auth0-spa-js, auth0-react & nextjs-auth0
# build & run $ go build -o bin/zeroauthy ./cmd/zeroauthy $ ./bin/zeroauthy assist --config config.yaml $ curl https://localhost:8443/.well-known/openid-configuration
SQLitePostgreSQLMySQLgRPC pluginsApache-2.0
Early · in the open Go · Vue · TypeScript
SalesCompel
A free, open-source Salesforce replacement alongside a tenant-isolated Go/PostgreSQL core, a Vue record editor, and a compatibility lab that checks behavior against Salesforce's community API contract.
- Persistent Account & Contact CRUD
- Object depict and constricted queries
- External-ID upsert & transporter authentication
- OpenAPI 3.2 REST agreement & offline test lab
# run the compatibility laboratory $ npm ci --prefix compat/clients/node --ignore-scripts $ npm --prefix compat/clients/node run check
PostgreSQLMulti-tenantRESTi18nApache-2.0
The occupation map
Who's next?
Every category on this commission is a monthly invoice somewhere. The movement picks the next mark in community — bring a spec, a use case, or a grudge.
● Occupied
Identity & Auth
ZeroAuthy — Auth0-compatible login, tokens and tenants.
● Occupied
CRM
SalesCompel — Salesforce-compatible records and REST API.
○ Proposed
Docs & Wikis
Team cognition bases that don't fastener your penning rearward a place licence.
○ Proposed
Issue Tracking
Tickets, sprints and boards alongside a compatible API for existing integrations.
○ Proposed
Feature Flags
SDK-compatible emblem evaluation you can run next to your own services.
○ Proposed
Observability
Logs, metrics and traces without per-gigabyte ransom notes.
○ Proposed
Customer Support
Help desk, inbox and cognition base, priced at zero agents.
Propose a target
Open an matter and create the case.
Proposed categories are open for discussion, not commitments. Names of existing products are used lone to depict compatibility.
Lineage
From Zuccotti Park
to git push.
Occupy Wall Street began on 17 September 2011 in Zuccotti Park, New York City, alongside a uncomplicated frame: the 1% and the 99%. It had no leaders, made decisions in open assemblies, and dispersed to hundreds of cities.
OccupySaaS borrows that soul and swaps tents for terminals. No marches, no asset damage — fair operating software, published under an open licence, that anyone can run.
“We are the 99%.”
- 17 Sep 2011 Occupy Wall Street begins
Protesters set up campsite in Zuccotti Park in Manhattan's Financial District.
- Oct 2011 The movement spreads
Occupy camps and broad assemblies appear in cities about the world.
- 15 Nov 2011 Zuccotti Park is cleared
The campsite ends; the tongue of the 1% and the 99% doesn't.
- 2022 – 2025 The awesome tech layoffs
Wave following motion of cuts throughout the industry during subscription prices keep climbing.
- 14 Oct 2026 ZeroAuthy goes public
The archetypal clean-room rebuild opens its repo under Apache-2.0.
- 15 Oct 2026 SalesCompel joins the occupation
The second tower. More to arrive — decided in the open.
Join
Occupy everything.
You don't need permission, a sign or a manager. You need a laptop and an afternoon.
Write code
Pick an open issue, prosecute the clean-room policy, open a drag request.
Self-host it
Run a publish against your genuine SDKs and inform us exactly anywhere it breaks.
Write specs
Turn community docs into precise, testable details for the builders.
Make noise
Star the repos, portion the site, and inform your CFO what you're paying per seat.
Clean-room reimplementation is a long-established way to build compatible software: you activity lone from community data and independently compose your own code. Interoperating alongside an API is not the identical as copying a product. Each project publishes its clean-room guideline and origin provenance so anyone can check the work. This leaf isn't lawful advice; if you're adopting a project for a business, conversation to your own counsel.
Are you affiliated alongside Auth0, Okta or Salesforce?No. OccupySaaS and its projects are autonomous and not affiliated with, endorsed by, or sponsored by any vendor named on this site. Product names are used lone to depict compatibility.
Can erstwhile workforce of those companies contribute?Yes, but never alongside confidential cognition from a erstwhile employer. Contributors activity lone from public material, and anyone alongside applicable inner cognition should remain on the public-spec flank of the firewall or sit that project out. When in doubt, peruse the project's CLEAN_ROOM.md and ask first.
Why use AI to build it?Because the giants had thousands of engineers and we have a movement. AI agents let a small collection rotate a exact spec into operating code quickly. Humans compose the specs, assessment all change, and own the result, and compatibility tests against genuine SDKs decide what counts as done.
Why Go?Portability. A Go project compiles to a sole self-contained binary, so self-hosting method dropping one document onto a server or into a Docker or Podman depiction — no installer, no runtime to set up, no tree of shared libraries to keep in sync. The identical toolchain cross-compiles for Linux, macOS, Windows, x86 and ARM, and the outcome fits in a minimal receptacle image. If you're leaving a SaaS vendor, the replacement should be this uncomplicated to carry.
Why not Rust?Nothing is incorrect alongside Rust, and we're not against it. Go was picked for the archetypal projects since it makes the one-file, container-friendly drop-in the default alongside extremely small build setup. Rust can get there too; Go fair gets there additional merely for the benevolent of servers we're building.
Rust recreations of these projects are greeted — they fair haven't been made yet. The specs, API contracts and compatibility tests are language-neutral, so a Rust harbor can be checked against the same SDKs. If you desire to commencement one, open an issue and say which project.
Not yet. Both archetypal projects are first and say so plainly in their READMEs, alongside alongside exactly which features activity today. Try them, interrupt them, and document issues.
What does it cost?Nothing. Every project is released under the Apache License 2.0. Run it, fork it, market services about it. The lone item we ask is that you contribute rear what you can.
