Huntress Explains Its Public and Private Beta Approach
Summary
Huntress describes its beta process: private beta tests features for stability, while public beta offers opt-in access to stable features so the company can learn from customer use and feedback.
Key points
- Huntress says beta is intended to gather real-world feedback and improve features, not simply mark them as unfinished.
- Private beta may be used for features that could affect endpoints, such as Managed AV, to identify issues before broader access.
- Public beta features are opt-in through the Huntress dashboard and are described as stable, with full support available.
- Huntress says public beta is focused on learning how customers use features and iterating based on feedback.
- The company cites early collection of endpoint autorun telemetry as an example of sharing useful security information before its product was fully developed.
Article Details
- Topic
- Huntress’s approach to private and public beta releases, emphasizing early partner access, feedback, and stable releases.
People
Vendors
Products
Huntress security platformAfter months of rigorous beta testing, we’re excited to announce the addition of our Managed Antivirus service to the Huntress Security Platform.Managed AVnew features in Huntress, we will not go through a “Private Beta” phase. But in some cases, such as Managed AV, we decide that a traditional beta phase is warranted — especially if we are changing something on thePersistent FootholdsKeep in mind that while there are some features that are in a beta state, there are still high-value services that are very mature and have already reached a full release stage — such as Persistent Footholds.