One CMDB the whole
company shares.
The platform has its own CMDB and its own discovery. Apps consume the CMDB and never own a private copy of it: 88 CI types, 32 relationship types and impact analysis up to 10 hops.
Modelled once, used everywhere.
The CI type library covers servers, databases, network, cloud and business applications. Tenants add their own types and fields, or relabel and hide library fields.
88 CI types, 32 relationship types
A ready library for servers, databases, network, cloud and business applications. Tenants add their own types and fields, or relabel and hide library fields.
Impact analysis up to 10 hops
What fails if this CI fails, what does it depend on, and which business services sit behind it? Answered from a CI, an alert, an incident or a change.
Service mapping
Discovered software, processes, ports and connections turn into Business Services grouped by tier. A person reviews before anything is published.
Assets and CIs in two-way sync
They stay in step through one shared status set. Work items link to CIs, and choosing one fills in the other.
What fails if this CI fails?
Impact analysis up to 10 hops shows what fails, what it depends on and which business services sit behind it — from a CI, an alert, an incident or a change.
- Only relationships marked as impact-carrying are followed.
- A CI is counted once, at the fewest hops.
- Retired CIs are skipped unless included.
Relationship diagram, hops and layers.
A relationship diagram with filters, hop counts and saved views. Every CI keeps a full field-level history.
- Impact-carrying and informational relationships are distinct.
- Service mapping turns discovered software, processes, ports and connections into tiered Business Services.
- A person reviews before anything is published.
BS-CORP-PORTAL
2 nodes · 2 edgesAssets, licenses and vulnerabilities in one place.
The CMDB is not just a CI list. Software assets, vulnerabilities and change risk connect to the same data model.
Software assets
Software catalog, inventory, allow/deny policies, license entitlements and compliance, end-of-life dates.
Vulnerabilities
Deterministic CVE matching against installed software and patches, with evidence, exclusions, remediation work items and risk acceptance through approvals.
Change risk
A traceable risk score from affected services, open alerts, recent incidents, concurrent changes and maintenance windows.
Its own discovery agents, in the same platform.
A discovery agent installed in the customer network scans and uploads raw results to the platform: WMI, SSH, SNMP topology, vCenter, Hyper-V, OLVM, F5, FortiGate, Cato, Kubernetes, AWS, Azure, databases, NetFlow and certificates.
It takes commands, never scripts.
- Agents connect with a company token.
- They must be approved before they can be commanded.
- They verify signed commands.
- They can only scan authorised ranges.
- They can never be told to run a script.
The matching order is fixed.
A re-scan updates the same CI, certain duplicates are merged automatically, and doubtful ones go to a review queue. Weaker sources cannot overwrite stronger ones, and unchanged re-scans write no history.
In a test run, five real scan payloads grew the CMDB from 3 to 46 CIs and created the linked assets automatically.
What the CMDB changes in practice.
A CMDB is not an inventory list; it is a decision tool. A well-fed CMDB makes impact analysis, change risk and asset cost manageable from one place.
A single source of truth
A company-wide CMDB stays current through the platform’s own discovery, and apps keep no private copies.
Evidence-based impact analysis
Dependencies up to 10 hops are answered from a CI, an alert, an incident or a change.
Visible change risk
Affected services, open alerts, recent incidents and maintenance windows become one traceable risk score.
Scan your own network into the CMDB.
In the demo we run impact analysis against your own CI model: which business service is affected if this server fails?