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.
Related Articles
Microvellum Software Versioning Schema
When it comes to the version or build number of your software, what is important is knowing whether or not the build you are running is the most current, and having a clear understanding of the features available in the software build. We’ve made ...
Support Discontinued for Microvellum Version 6.7 Software
As of December 1, 2021, all forms of support for Microvellum version 6.7 software applications will be discontinued. If you are still using Microvellum v6.7 software, then you know that maintenance updates ended in 2012. This announcement pertains to ...
Software Troubleshooting
This article lists a few of the hiccups our users have encountered while trying to install or launch our software and provides a tested solution for each. If you are having trouble getting your software to cooperate and don't see a solution listed ...
Microvellum Foundation Library Release Notes: 2021-2024
This document catalogs all versions of the Microvellum Foundation Library released between the years of 2021-2024. This encompasses builds 20.1201 to 24.0919 (current). To download the Foundation Library in one of the builds listed in this document, ...
Deploying Microvellum on an Azure Virtual Machine (VM)
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 ...