Mend.io Reviews

Mend.io's pricing is seen as high by some, but others find it comparable to other tools or negotiable. Some customers feel that they are getting good value for what they pay, while others feel that the pricing could be improved. The licensing model for Mend.io requires a minimum of 20 developers.

Mend.io has resulted in various returns on investment for different companies. One company is saving 15 percent of their time and achieving a big financial gain, while also delivering safer products for their customers. Another company has seen an improvement in code quality and incident reaction. Some companies have seen a terrific ROI and rate the solution highly. However, there are also competitors in the space, and pricing may become a problem for Mend.io in the future. Additionally, the tool helps remove manual processes, which speeds up delivery and reduces costs in terms of compliance and risk avoidance. Overall, companies have seen a return on investment and expect to see it increase in the future through new sales and cross-sales.

Mend is primarily used for detecting and fixing vulnerabilities in products and delivering security reports during product releases. It covers license usage, license type, and CVE vulnerabilities. Mend is deployed on the AWS cloud and has multi-region enabled. It is used to automate software composition analysis, particularly for third-party and open-source software. Mend is also used for code analysis and management of open-source associated risks. It allows for scanning open-source libraries and checking for vulnerabilities and open-source licenses. Policies can be set to disallow risky open sources from being used in solutions. Mend's deployment is hybrid, with scans on-premise and the knowledge base on the cloud.

M.io is valued for its ease of setup and integration with Git providers and IDEs. Its command line tool and plug-ins automate scans and allow for continuous integration. Mend.io's ability to identify and remediate open-source vulnerabilities and its integration with developer workflows are highly appreciated. Mend.io's UI and scanning for security threats fit well into workflows, making it valuable to Intellectual Property Councils. Its vulnerability analysis and license distribution analysis are useful features for legal firms. Mend.io's Smart Fix helps developers fix vulnerable transitive dependencies and reduces mean time to resolution. Its ability to integrate with existing workflows, including IDEs, repositories, and CI/CD pipelines, is good. The dashboard view and the management view are also highly valued. Overall, Mend.io helps reduce the number of open-source software vulnerabilities running in production and streamlines around 60% of the software development life cycle via automation, while the remaining 40% requires human intervention.

Improvements needed on Mend.io include better reporting with customizable reports, implementing a version number between product and projects, improving the UI, adding preconfigured policies, reducing visibility on the dashboard, supporting more package managers, improving automation to human involvement ratio, improving user management, adding support for C++ in Mend Prioritize, having a central support system, improving latency for remediated findings, changing the pricing model, supporting multiple SBOM formats, having builds fail if important vulnerabilities are found, improving database upgrading turnaround time and accuracy, including static analysis in the open-source version, providing on-premises service, simplifying the initial setup, and adding a code snippet part.

The initial setup for Mend.io was generally straightforward and easy, with some minor configuration needed to meet specific company requirements. Deployment and maintenance are low, with only a few key staff involved in the process. Implementation takes a few days, with minimal maintenance needed afterward. Overall, it was considered a simple and efficient process.

The Mend.io solution is highly scalable, with users from multiple departments and locations, and the ability to handle increased usage without performance issues. One user had some difficulties with a large codebase but is working with the vendor to resolve the issue. The solution is used by a range of organizations, from those with only a few users to those with hundreds. Scalability is crucial for this type of software and is a prerequisite for a SaaS-based solution.

Customers generally have positive feedback about Mend's customer service and support. They highlight the efficiency, responsiveness, and knowledgeability of the support team. Some customers also appreciate the option of having a dedicated customer support manager. However, some customers note that there may be room for improvement in terms of customer-friendliness and pricing compared to other solutions. Overall, customers rate Mend's support between seven and nine out of ten.

Overall, Mend.io is considered to be a highly stable solution with very few reported issues or downtime. While there have been a few minor hiccups in the past, these were swiftly resolved and did not impact the overall stability of the product. Users rate the stability of Mend.io very highly and consider it to be a dependable and reliable solution. Additionally, the solution is also scalable, meaning it can adapt to meet the changing needs of users over time.

Before switching to Mend.io, some companies had manual processes or tried using other tools to detect vulnerabilities, but they were not effective or efficient. Some companies switched to Mend.io for its proactive identification of vulnerabilities, immediate scanning of code, and ability to control releases. Other companies looked at various solutions before choosing Mend.io, and found it easier to use and more accurate than competitors like Black Duck. Some users also use multiple solutions, but Mend.io stands out for its legal guidance and ability to find unwanted license types.

Mend.io has received overwhelmingly positive feedback regarding their customer service and support.

The solution of Mend.io is being deployed in a mix of both public and private cloud environments. Some users are utilizing the public cloud deployment model, while others are opting for a private cloud setup. There does not seem to be a clear consensus on which deployment model is preferred, as both options have received positive feedback from reviewers.

The implementation team for Mend.io seems to require very few people, with some users rolling out the solution themselves and others using only one person for deployment. Sales engineers were involved in some cases, but for CI/CD integration, a consultant was required. The team size varied between cases, with one user having only four people on their team.