Penetration testers
Evaluate scope definition, controlled verification, evidence capture and reproducibility across realistic assessment workflows.
PRIVATE BETA / EARLY ACCESS
We’re inviting pentesters, AppSec engineers and technical defenders to push HOLES through realistic, authorized workflows. Test where evidence holds, where context breaks and where the operator needs sharper control. Your feedback goes straight into the product.
Small cohorts. Direct technical exchange with the team.
WHO WE ARE LOOKING FOR
We want detailed, honest feedback from people who understand the difference between a scanner signal and a defensible finding.
Evaluate scope definition, controlled verification, evidence capture and reproducibility across realistic assessment workflows.
Challenge finding quality, prioritization, handoff and the usefulness of evidence for remediation teams.
Review the operator workflow, reporting clarity and whether HOLES supports transparent client communication.
Show us where better context, test-pressure controls and stronger evidence can turn an ambiguous alert into a clear next move.
WHAT BETA TESTERS DO
Use synthetic systems, infrastructure you own or targets covered by explicit permission. Tune the pressure to the environment and see where the workflow holds.
Share the conditions, expected behavior, observed result and enough context for the team to reproduce the problem.
Tell us whether the result is reproducible, technically defensible and ready for the person who must validate or remediate it.
Help prioritize the changes that make HOLES faster, sharper and more useful in real technical work.
YOUR SCOPE. YOUR AUTHORIZATION.
Use HOLES on synthetic environments, systems you own or targets covered by explicit permission. The beta is built for controlled technical evaluation and is not yet intended as the sole basis for production-critical decisions.
APPLY FOR EARLY ACCESS
Complete the short profile to apply for early access.
BETA PROGRAM FAQ
Security professionals, penetration testers, AppSec engineers, consultants, system administrators and technical teams with authorized assessment experience.
Setup, usability, governed assessment workflows, evidence quality, reproducibility and technical reporting on safe, authorized environments.
Conditions, expected behavior, observed result, evidence and enough context for us to reproduce the issue. Sharp technical disagreement is more useful than polite approval.
We onboard small cohorts as builds become ready. Selected testers hear from us directly.