Stay in contact
Reply to test questions, tell us when you cannot continue a test, and let us know whether a new build changed the result.
Blackwire Testing Program
Apply to test Blackwire alpha and beta software.
Blackwire is looking for people who are comfortable testing unfinished software, reporting what actually happened, and staying in contact while we work through problems. Good testing is more than saying something works or does not work — we need the details that let us reproduce it.
Real test buildsWork with active Alpha and Beta projects selected for outside testing.
Direct feedbackSend logs, screenshots, reproduction steps, and retest results to Blackwire.
Reproduce and retestFinding a problem is only half the job. We also need testers who can confirm whether the next build fixed it.
Not a public previewSome builds and test details may need to stay private until Blackwire says otherwise.
Who we are looking for
People who will actually test, document, and follow up.
You do not need to be a software developer. We are interested in home users, repair technicians, MSPs, network administrators, IT staff, and experienced power users who can describe a problem clearly and are willing to retest changes.
Different projects need different environments. Some tests may require particular Windows versions, hardware, network equipment, or real-world workflows. Applying does not guarantee that every project will be a fit.
What we expect
Open communication is part of the testing job.
If a build fails, hangs, behaves differently than expected, or produces a warning, we need enough information to understand what happened and to verify the fix afterward.
Send useful evidence
Provide Blackwire-generated logs, error messages, screenshots, and short videos when they help show the problem.
Give reproduction steps
Tell us what you were doing, what you expected, what actually happened, and whether you can reproduce it.
Retest fixes
A bug report is most useful when the person who found it can verify whether the next build actually fixes it.
A useful test report
Give us enough information to reproduce the problem.
- Blackwire product name and exact build/version
- Windows version and relevant hardware or network environment
- What you were trying to do
- Steps that produced the problem
- Expected result and actual result
- Exact error text when available
- Blackwire logs, reports, dumps, or exported diagnostics related to the test
- Screenshots or screen recording when the problem is visual
- Whether the issue happens every time or only sometimes
- Result after testing a replacement build or workaround
Participation terms
Testing unfinished software comes with a few ground rules.
These terms keep the program useful and protect both the tester and Blackwire while a product is still changing.
1. Participation is voluntary
Applying does not guarantee acceptance, access to a particular project, or a complimentary license. Testing is voluntary and does not create an employment, contractor, partnership, or agency relationship with Blackwire Software LLC.
2. Pre-release software may fail
Alpha and Beta builds may contain bugs, incomplete features, compatibility problems, or data-loss risks. Testers are responsible for maintaining backups and should not use a pre-release build on a production-critical system unless the test specifically calls for it and the tester accepts that risk.
3. Communication and evidence are required
Testers are expected to provide timely, honest results and reasonable diagnostic evidence when requested. Repeatedly accepting builds without reporting results, refusing to provide available logs, or becoming unreachable may end participation in the program.
4. Do not redistribute private builds or licenses
Private installers, test links, license keys, internal documentation, and other material provided for a closed test may not be copied, resold, posted publicly, or given to another person without written permission from Blackwire.
5. Public discussion depends on the project
Some tests may be open for public discussion while others may involve unreleased features or confidential test material. Blackwire will tell testers when a project has additional confidentiality requirements. Security findings should always be reported privately first.
6. Complimentary licenses
Blackwire may provide temporary test licenses or complimentary product licenses to approved testers. The type, duration, product, device limits, and other license conditions are determined when the license is issued. Complimentary licenses are not wages, cannot be exchanged for cash, and may not be resold or transferred unless Blackwire explicitly allows it.
7. Program access can change
Blackwire may pause a test, remove a tester, replace a build, or end a testing cycle when needed. Testers may leave the program at any time by contacting Blackwire.