- Saw Genesis closed alpha access begins with an invitation and onboarding process.
- Check your inbox and spam folder if you completed the original signup survey.
- Steam and Discord are required for access, support, communication, and testing.
- Recording and streaming are prohibited under the closed alpha confidentiality statement.
- Future playtests are planned, so missed invitations do not end your opportunity to participate.
Saw Genesis closed alpha: What to Expect
The Saw Genesis closed alpha is an early multiplayer testing phase for the 3v1 asymmetrical horror game. It is designed to test server stability, networking, matchmaking, the central gameplay loop, and the first version of the progression systems. Because this is an early development build, features and content may continue changing as the team reviews player feedback.
The current signup page is labeled Closed Alpha Playtest #2 and directs interested players to join the official waitlist. Players who sign up can receive an email with a link to join the game when selected. The initial invitation wave was chosen using signup survey information, with the goal of creating a useful and varied group for development testing.
Video Highlights:
- The invitation process begins through the email address used during signup.
- Selected players must accept the confidentiality statement before access.
- Steam handles the game build, while Discord supports communication and assistance.
- The first test is part of a wider sequence of planned playtests.
- Testing focuses on systems, matchmaking, feedback, and the core match experience.
| Access Stage | What Happens | Player Action |
|---|---|---|
| Waitlist | Signup information is stored for future selection | Register through the official page |
| Invitation | Selected players receive an email | Check inbox and spam folders |
| Onboarding | Confidentiality statement and account connections are completed | Accept the terms and connect accounts |
| Key Assignment | A Steam key is assigned after onboarding | Watch for the key and preload when available |
| Server Launch | Test sessions open during scheduled windows | Join through the private Discord instructions |
Early Build
The test version is still evolving. Systems, balance, and content may change after feedback.
Selected Access
Signup does not guarantee entry. The development and UX teams choose participants for each test.
Private Communication
Playtest updates, support, and session details are handled through private Discord channels.
Future Waves
Additional playtests are planned to expand participation and improve the experience over time.
If you registered previously, search every email account connected to your signup, Steam, or Discord details before assuming you were not selected.
How to Join the Closed Alpha
The safest way to pursue access is to use the official SAW: Genesis playtest waitlist. The page provides signup and login options, and it is the primary route for future invitations. Avoid relying on unofficial key offers or unverified messages, especially when a test requires account linking and a confidentiality agreement.
Join or Review the Waitlist
Open the official SAW: Genesis playtest page and use the signup or login option. If you already completed a previous survey, confirm that your contact details and account information remain available to the playtest team.
Monitor Your Email
Selected players receive an invitation by email. Search your inbox and spam folder using terms such as “SAW,” “Genesis,” “playtest,” or “invitation.” Check the addresses used during signup and the addresses connected to Steam or Discord.
Accept the Invitation
Use the invitation email’s acceptance button to open the onboarding page. Read the confidentiality statement carefully before accepting it. Participation requires agreement to keep the closed alpha private.
Connect Steam and Discord
Steam is required to access the test build. Discord is used for playtest communication, updates, support, and private tester channels. Complete both connections before waiting for the key.
Wait for the Key and Session Notice
After onboarding, wait for the Steam key and server launch announcement. Session timing and regional availability are shared through the private playtester Discord area.
| Requirement | Purpose | Status to Confirm |
|---|---|---|
| Official waitlist signup | Places your information in the selection pool | Signup completed |
| Invitation email | Starts the acceptance process | Inbox and spam checked |
| Confidentiality statement | Establishes the closed test rules | Accepted |
| Steam account | Provides access to the game build | Connected |
| Discord account | Delivers support and test information | Connected |
Closed alpha participants cannot record, stream, or disclose gameplay and personal test experiences outside approved communication channels. Treat screenshots, clips, and detailed impressions as restricted until the team changes the policy.
Closed Alpha Content and Match Structure
The test focuses on the foundation of Saw Genesis rather than a finished content package. The announced goals include networking tests, server stability, matchmaking, the moment-to-moment experience, the core gameplay loop for both sides, basic progression, an endgame tutorial, and voice chat.
Matches use a 3v1 structure. The Accused side works as a group of three, while the Judge acts as the opposing role. The announced test materials identify several playable characters, including Doctor Judge, Old Hand, Caregiver, and Songbird. The exact availability of each option may depend on the test build and onboarding information.
The level structure uses procedurally generated map flow built around anchor rooms. Corridors can contain clues and collectibles that help unlock challenge rooms. Three challenge room types are identified for the alpha: maze, pest, and disposal challenges.
| System | Closed Alpha Focus | Practical Meaning |
|---|---|---|
| Match format | 3v1 asymmetrical horror | Three Accused players face one Judge |
| Map flow | Procedural structure around anchor rooms | Routes and room connections can vary |
| Challenge rooms | Maze, pest, disposal | Different objectives shape progression through the map |
| Investigation | Clues and collectibles | Searching corridors supports challenge-room access |
| Communication | Voice chat and Discord support | Coordination is important during testing |
| Matchmaking | Networking and queue validation | The team is testing party and server behavior |
The initial party structure supports groups of three players on the Accused side. A future test may expand the lobby structure so players can cycle through roles, but that should not be treated as available in the current alpha unless the private test instructions confirm it.
No cosmetic customization or skins are planned for the described test phase. The purpose is to evaluate the playable systems, role experience, and stability rather than provide a full live-service customization catalog.
Useful feedback should cover matchmaking, server behavior, clarity of objectives, role balance, progression, voice chat, and the minute-to-minute experience—not only whether a match was won or lost.
Perks, Progression, and Tester Priorities
Saw Genesis introduces an early meta-progression layer for both sides of the match. The announced alpha details include personal perks and mastery perks that unlock during testing. The available selections are limited in this build, and the system may be adjusted as the team gathers feedback.
For the Accused side, the announced structure includes two of eight personal perks after unlocking and one of three mastery perks after unlocking. The Judge has a separate selection structure, described as two of seven personal perks and one of three mastery perks after unlocking. These figures describe the announced test configuration, not a final balance commitment.
| Role | Announced Perk Access | Other Details |
|---|---|---|
| Accused | Two personal perks, one mastery perk | Three-player side; progression options are limited |
| Judge | Two personal perks, one mastery perk | Opposing role with separate perk selections |
| All testers | Basic meta-progression layer | Values and availability may evolve during development |
The alpha also identifies a static guilt system and a static drop trap, including a bear trap. These mechanics should be approached as test subjects. Players should note how clearly the systems communicate danger, how often they affect decision-making, and whether they create interesting choices for both roles.
Use the following priorities when preparing feedback:
- Record whether objectives are clear without outside explanation.
- Note whether map flow creates meaningful choices or confusing dead ends.
- Test how perks affect the core loop rather than judging them only by raw power.
- Report matchmaking delays, disconnects, voice issues, or server instability.
- Compare the experience of playing with a coordinated party against solo matchmaking.
- Explain what happened before suggesting a balance change.
Tester Feedback Checklist:
- Check matchmaking, party behavior, and server stability
- Evaluate clues, collectibles, and challenge-room clarity
- Test voice chat and private Discord support channels
- Compare Judge and Accused role experiences
- Submit feedback through the in-game or Discord survey
Describe the situation, the expected result, the observed result, and how often it happened. Specific reproduction details are more useful than a short statement that a feature felt bad.
Schedule, Rules, and Next Steps
The announced closed alpha is planned as a four-day test with four-hour sessions scheduled separately for Europe, US East, and US West regions. Exact session times are shared with accepted testers through the private Discord channels. The Steam key is expected to arrive after invitations and onboarding, allowing time to preload before servers open.
The duration and schedule apply to the announced test phase. Future tests may use different dates, regions, durations, or access rules. Always follow the latest private tester notice instead of relying on older community posts.
| Schedule Item | Announced Information | Where to Confirm |
|---|---|---|
| Test length | Four days | Private tester Discord |
| Daily access | Four hours per regional session | Session announcement |
| Regions | Europe, US East, US West | Regional schedule notice |
| Steam key | Assigned after onboarding | Email or Steam account |
| Feedback | In-game and Discord survey links | Test build and private channels |
If you were not selected for the first wave, remain on the waitlist and watch for future invitations. The development team has stated that more playtests are intended before early access, with later waves expected to broaden participation and incorporate feedback from earlier sessions.
Q: How do I join the Saw Genesis closed alpha?
Use the official SAW: Genesis playtest waitlist, complete the signup process, and wait for a selection email. Invitation access is not guaranteed for every signup wave.
Q: Do I need both Steam and Discord?
Yes. Steam is required to access the test build, while Discord is used for playtest communication, support, updates, and private tester channels.
Q: Can I record or stream the closed alpha?
No. Recording, streaming, and sharing closed alpha material are prohibited under the confidentiality statement unless the development team later changes the policy.
Q: What if I did not receive an invitation?
Check your inbox and spam folders, then remain on the official waitlist. Additional playtests are planned, so later selection opportunities may become available.
Keep your signup information current, monitor connected email accounts, and use the official waitlist rather than unofficial access claims. The private Discord instructions take priority once you are accepted.