BeaverFlow CMDB vs CMDBuild

BeaverFlow CMDB maintains a registry of configuration items such as physical devices, virtual machines, SaaS subscriptions, cloud resources, and installed software. Items can record an owner, location, version, support contract, and lifecycle stage. A relationship graph maps dependencies and service impact paths, while change impact assessment identifies affected items and services. The listed capabilities include hardware and software inventory, cloud asset tracking, licence compliance, and lifecycle tracking. Discovery tools and infrastructure-as-code pipelines, including Terraform and Ansible use cases, can update records automatically. The CMDB logs item creation, modification, and retirement with a timestamp, user, and reason; it also generates a health indicator from incident history, age, support status, and open vulnerabilities. Shared and dedicated cloud deployment are offered on all plans, while on-premise deployment is listed for Enterprise. iOS and Android apps are listed across plans. Growth costs $24 a month per user, and Enterprise costs $47 a month per user; both are for up to 50 users. A three-month trial includes all 12 products, is limited to five users, requires no credit card, and preserves data for 30 days after it ends.

CMDBuild is an open-source web environment for configuring custom asset-management applications. It manages asset databases and tracks asset composition, location, functional relationships, updates, and lifecycle. Configuration tools cover database modeling, workflows, reports, dashboards, external connectors, georeferencing, and administration. Other listed features include file import and export, document archives, GIS and BIM, history, task management, and scheduling. REST web services let connected applications read and write data, run operations, exchange notifications, and connect to external systems. Permissions can be assigned through user roles and scoped to data, processes, views, reports, and dashboards. The software runs on a web server and is accessed in a browser; server setup knowledge is required. Its listed minimum hardware includes 16 GB RAM, 150 GB disk per instance, and four cores, alongside PostgreSQL 17.x, Tomcat 10, and Java 17. The standard download does not include a data model, workflows, reports, or dashboards. CMDBuild is available under the AGPL, with legal notice and logo requirements for modified versions.