How to run a closed beta for your game
2 min read
By Eduardo Orellana ·
A closed beta puts a nearly complete build in front of a limited group to find bugs, balance problems and confusing moments before launch. Pick testers from your Discord and wishlisters, give it a start and end date and a clear goal, hand out the build through Steam Playtest, Steam keys on a beta branch, or a direct link, and collect feedback in one structured place. Fix, ship a new build, and say what you changed.
A beta has a question to answer
"Is the game fun?" is a playtest. A beta asks narrower ones: does it crash, is the economy balanced, does anyone get stuck in chapter three. Write the question down before inviting anyone.
Running it
- Choose testers: your Discord, wishlisters, past playtesters; a few dozen to a few hundred.
- Pick a channel: Steam Playtest, keys to a beta branch, or a direct build link.
- Set dates and a goal.
- Collect bugs and feedback in one place, with a template.
- Ship updates during the beta and post a changelog.
NDAs and leaks
Most indie betas do not need an NDA; clips from testers are marketing. Ask for one only if the game has a secret worth keeping.
Where Flockbay fits
Flockbay's playtest links hand a build to testers and report crashes, frame times and play time back. Free in beta until 1 December 2026.