If something at work feels wrong, you do not have to figure it out alone.
unionize.software is a public organizing wiki for U.S. private-sector software and game workers. It is here to help you understand what is happening, compare notes more safely, and figure out a sensible next step.
A few ground rules
- Use a personal phone and personal email if you can.
- Do not use company chat, company email, or company devices for organizing.
- Start with facts, trusted coworkers, and one small next step.
- No analytics, session replay, or ad pixels.
- The pathfinder stays local to your device.
Plain-English guidance for workers trying to make sense of a workplace problem.
Some people arrive here because of surveillance. Some because of layoffs, pay, burnout, or retaliation. The point is to help you get oriented without acting rashly or handing the site a detailed story about your workplace.
What you can do here
- Read issue guides, rights explainers, and campaign-stage pages.
- Use checklists for documentation, first conversations, and common mistakes.
- Browse by work mode: in-person, hybrid, or remote/distributed.
- Use the evidence pages when you need numbers, history, and a steadier answer to the claim that software workers cannot organize.
- Use the optional local-only pathfinder if you want a narrower route in.
What this site is not
- Chat, forums, boards, and campaign CRM
- Tracking scripts or growth analytics
- LLMs over worker intake or wizard data
- Advice that tries to rush people into dramatic or risky moves
If you already know the problem, go straight to the closest guide.
You do not need to fill anything out. Start with the issue guide that matches what is happening, then move to the checklist or reference page that fits your situation.
How to use the wiki
Most people do not need a perfect plan. They need the right next page.
Start with the problem in front of you. Then look at the work mode, the worker-status questions, and the checklist or reference page that helps you make the next move more carefully.
Read the issue guide first
Start with the closest match to the actual workplace problem instead of waiting for someone else to interpret it for you.
Use checklists and reference pages
Keep the next move small and practical: preserve facts, have one careful conversation, and avoid obvious disciplinary traps.
Match the strategy to the workplace
Remote, hybrid, and in-person teams need different mechanics. The site should help people learn that difference, not hide it.
Special tools
The site also ships agent-ready tooling, not just pages.
If people want to bring the guide corpus into their own terminals and agents, there is a cleaner way to do that than scraping rendered HTML.
CLI
Read guides, search by issue, and run the pathfinder from the terminal without scraping pages.
MCP Server
Expose the guide corpus, prompts, and pathfinder logic to agents through a local MCP server.
OpenClaw Skills
Ship a reusable skill pack so agents approach organizing questions with the right safety boundaries.
Browse the wiki
Issue guides
AI surveillance, layoffs, pay, burnout, discrimination, contractor questions, and other concrete workplace problems.
Browse issue guidesWork modes
In-person, hybrid, and remote/distributed organizing need different mechanics and different failure warnings.
Compare work modesChecklists and tools
What to preserve, first conversation help, what not to do, and quick-reference pages for stressed workers.
Use checklistsEvidence and leverage
Workforce size, low union density, why tech stayed weakly organized, and what collective bargaining can actually change.
Read evidenceSlow and careful is often better than fast and loud.
People usually land here under stress. The goal is to help them compare facts, talk to trusted coworkers, and avoid handing management an easy excuse.