The trusted single source of truth for your services and configuration items — the relationship graph that grounds incidents, changes, security and operations across the whole platform.
The CMDB is the foundation the rest of the platform stands on. Configuration items — servers, applications, network devices and services — and the relationships between them give every other module its context.
Because incidents, changes, assets, security records and alerts all reference CIs, impact analysis is built in: change a CI and you can see what it touches; an alert on a CI already knows its downstream services and owners.
Servers, applications, network devices and services modeled as governed records with type, status and owner.
Map dependencies between CIs so upstream and downstream impact is always knowable.
See what a change or outage affects before it happens, across services and owners.
Operational status per CI — operational, degraded, down — visible to every module.
CIs reconcile with ITAM assets, connecting operational reality to financial ownership.
Group CIs into business services so impact is expressed in terms the business understands.
Every process is a configurable state machine — built visually, governed by approvals and SLAs, with no code.
CI created from discovery, asset reconciliation or manual entry.
Typed, owned and grouped into the services it supports.
Dependencies mapped to upstream and downstream CIs.
Status tracked live; referenced by incidents, changes, alerts and security records.
Decommissioned CIs archived with relationship history preserved.
Specialist agents work this module with business context and the exact permissions of a human in the role — planning, retrieving grounded context, and acting through governed tools under human-in-the-loop control.
Meet the agents →Uses the relationship graph to assess change risk and blast radius.
Reads CI business impact to prioritize what to fix first.
Because every module references CIs, incidents, changes and alerts arrive already knowing their blast radius.
The relationship graph makes upstream and downstream impact visible before a change is approved.
CIs reconcile with assets, so operational status and financial ownership describe the same things.
Every other module — ITSM, SecOps, ITOM, ITAM — references configuration items for context, so the CMDB is what makes those modules impact-aware.
Yes. The relationship graph lets you see what a change or outage affects across services and owners before it happens.
Configuration items reconcile with ITAM assets, connecting the operational view of a thing to its financial ownership.
Configuration Management (CMDB) shares the same metadata core as the rest of Zyvark One, so it connects natively to:
Incidents, problems, change & CAB, catalog and knowledge — with impact×urgency priority and live SLAs.
Event correlation into actionable alerts, service maps and noise reduction that feeds incident management.
NIST-aligned incident response, vulnerability prioritization and threat intel mapped to your CMDB.
Explore a fully-seeded demo tenant — live records, SLAs, agents and the Control Tower, all on one metadata core.