Join the Beta Experience
About the Program
Whether you are a new user or a Microvellum expert, we’re looking for individuals who are passionate about woodworking technology and Microvellum Software to help us shape the future of our solutions. Your real-world experiences, insight, and ideas related to workflows, process, and specific needs helps add to the robust capabilities of Microvellum.
To be a Microvellum Beta Partner, you will need to:
- Be willing to participate in beta software evaluations and discussions.
- Report bugs, issues, and feedback on a regular basis via Microvellum’s support channels and surveys.
- Have a sandbox environment set up for beta updates, so as to not disrupt your daily production.
- Submit a support ticket requesting access to the beta. Beta software access is found under the "classification" field.
How do I Participate?
Our Beta program is open to all active Microvellum users with a current support agreement. When you become a beta partner, you will gain access to software, library data documentation, and or program features for the duration of the beta cycle, as well as access to the Microvellum Insiders forum on the
Microvellum Community. Your feedback on the beta features is reviewed by Microvellum’s Product Quality team.
Grant of License
Access to the Microvellum Beta Software Program is reserved for active clients with a current support agreement. Subject to the terms and conditions of this Agreement, Microvellum Software hereby grants to you a non-exclusive, non-transferable license (without the right to sub-license) (i) to use the Software or Service in accordance with the Documentation solely for purposes of internal testing and evaluation, and (ii) provided that you do not (and do not permit anyone else to) copy, modify, create a derivative work of, reverse engineer, decompile, or otherwise attempt to discover the source code, sell, lease, sub-license, assign, grant a security interest in or otherwise transfer any right in the Software.
Microvellum reserves the right to end your access and or terminate the beta cycle at its discretion.
BETA DISCLAIMER
THE BETA SOFTWARE OR SERVICE LICENSED HEREUNDER IS BELIEVED TO CONTAIN DEFECTS AND IS AVAILABLE ON AN “AS IS” AND “AS AVAILABLE” BASIS FOR THE SOLE PURPOSE OF PROVIDING MICROVELLUM WITH FEEDBACK ON QUALITY, USABILITY, PERFORMANCE, AND THE IDENTIFICATION OF DEFECTS. LICENSEE IS ADVISED TO SAFEGUARD IMPORTANT DATA, TO USE CAUTION, AND NOT TO RELY IN ANY WAY ON THE CORRECT FUNCTIONING OR PERFORMANCE OF THE SOFTWARE AND/OR ACCOMPANYING MATERIALS. THE POSSIBILITY OF THE CORRUPTION OF DATA AND/OR THE LOSS OF DATA EXISTS. MICROVELLUM STRONGLY ENCOURAGES YOU TO BACK UP ALL DATA AND INFORMATION. YOU ASSUME ALL RISKS AND ALL COSTS ASSOCIATED WITH THE USE OF THE SOFTWARE OR SERVICE.
Recent Articles
Toolbox Release Notes | Build 24.1.0719.642
The following release notes apply to Toolbox build 24.1.0719.642 900 Tools Fix A recurring issue with 900 tools being used in an incorrect order during certain operations was reported. The issue would manifest as tools switching back and forth during ...
Foundation Hardware Highlight: Grass
Microvellum’s Foundation Library is built on the premise of providing our users with the best quality hardware for their construction projects, be they commercial, residential, or anything otherwise. As such, Toolbox has hardware from multiple brands ...
Toolbox Release Notes | Build 24.1.0703.641
The following release notes apply to Toolbox build 24.1.0703.641 Product Comments Fix An issue with product comments in has been resolved. It was found that in older builds (pre-2023), when a formula driven product had comments placed into it and the ...
Foundation Hardware Highlight: Richelieu
Microvellum’s Foundation Library is built on the premise of providing our users with the best quality hardware for their construction projects, be they commercial, residential, or anything otherwise. As such, Toolbox has hardware from multiple brands ...
Selecting an Azure VM to Deploy Microvellum
Selecting the correctly sized virtual machines (VM) in Azure depends on several factors, such workload requirements, budget, and performance requirements. It may be necessary to work closely with an IT professional with experience working in Azure to ...