The next announced Vaultbreakers Alpha is scheduled to begin October 15, 2026 at 10:00 CEST and end October 21 at 23:59 CEST. Treat those times as a limited test window, not the base game’s release date. The public Steam Demo became available on October 8 and is the confirmed preparation path: the official Demo announcement says Demo progress will carry into the Alpha. The exact Steam app used to deliver Alpha access is not identified clearly enough in the public material to tell players to install an unverified client.
Know which product you are opening
Vaultbreakers has more than one Steam identity. AppID 306910 is the unreleased base game, while AppID 4488770 is the public Demo released October 8, 2026. A historical Playtest listing also exists, but that does not prove it is the delivery mechanism for the October Alpha. Check the title and AppID on the Steam page before downloading, and follow the official site or Discord for access instructions rather than a similarly named store result.
Prepare through the Demo
The Demo lets you learn the expedition loop with Nymera or Bjornir, explore part of Wolfswood, use Haven, play solo or with up to two friends, and advance through the first Vaultbreak. That foundation is useful because the Alpha notes describe a wider game rather than a completely different one. Focus on movement, camera control, wounds, extraction decisions, storage, crafting, and team communication.
Do not grind only for temporary item totals. The announcement specifically says Demo progress carries into Alpha, but it does not make a blanket promise that every Alpha possession will carry into launch. The Demo separately identifies Legacy progression as something intended to remain for the full release. Keep these two transfers distinct when deciding how much time to invest.
Expect a broader Alpha world
October patch notes name additional regions or subareas such as Bahra, Shanty Town, Windshear Crag, and Fume Pits. They also mention Balloon Teleporters, later Vaults, more Artifact paths, Haven social changes, expanded controller navigation, and new or revised opponents. These additions make the Alpha a content and systems test, not merely a longer Demo.
That breadth also means old strategies may be invalid. Balance changes affect heroes, equipment, healing, enemy behavior, recipes, and the economy. Read current in-game descriptions after the Alpha client updates. A build copied from a July or February test can be useful context, but its values and interactions are not authoritative for October.
Set up the Windows client cleanly
Verify free storage, update the graphics driver only if needed, and restart after any required installation. The October notes state that DirectX 11 is no longer supported, while the current base-game Steam requirements specify DirectX 12. Start with conservative graphics settings and a stable frame-rate limit; visual polish is less useful than consistent input and readable enemy attacks during a test.
Connect only the controller you intend to use, or establish a keyboard-and-mouse baseline. Disable unnecessary overlays and third-party injectors if the client crashes. Do not delete configuration or save folders blindly. Preserve a copy and use official support channels before destructive troubleshooting, especially when test progress is supposed to move from Demo to Alpha.
Plan around the actual window
Convert both CEST timestamps to your local time before the opening day. A test may also require a patch, queue, maintenance period, or server recovery, so do not schedule your only session for the last hour. If access is account-limited, follow the invitation’s instructions exactly and avoid paying strangers for keys or account access.
For a useful first Alpha session, choose one objective: confirm transferred Demo progress, enter one new region, test a new hero, or exercise the updated party flow. Record the build identifier and time when reporting an issue. A focused report is more useful than a large list of unrelated symptoms.
Report problems with reproducible details
Include the client name, build, region, Windows version, hardware, input method, party size, location, and the exact steps leading to the issue. For a crash, note what happened immediately before it and whether relaunching restored the expedition or returned you to Haven. For network trouble, say whether party members were affected together.
Screenshots and short clips should omit account names, invitation codes, and personal data. Use the current official reporting destination stated for the Alpha; historical forms or channels may no longer be monitored. If the symptom is performance-related, the Performance and Crashes guide provides an isolation order that preserves useful evidence.