Every feature your CMDB needs, nothing it doesn't

ITILv4-aligned incident and change management

Real ITIL incident depth: response and resolution SLAs, resolution and closure codes, watchers, parent and child links.

Before you make a change, Kovira runs a full upstream and downstream impact analysis. Pick a CI and you see every dependency, every service that could be affected, and every team that needs to know. Change approvals are gated to an independent reviewer: the person who created the change cannot approve their own work.

Incidents carry the fields ITIL practices call for: priority matrix, response and resolution SLA timers driven by per-customer policies and coverage windows, resolution category, closure code, who resolved it, watchers who get notified on updates, parent and child links for major events that group dozens of related tickets, and a postmortem document reference for major incidents. Reopens are tracked with a counter, so you can spot patterns instead of patching the symptom.

Every incident and change links back to the CIs it touches, so postmortems and audits run against current configuration rather than someone's recollection.

Mailbox to ticket: turn shared inboxes into a ticket pipeline

Connect a support@ mailbox and email becomes incidents, replies thread, automation kicks in.

Connect a Microsoft 365 user or shared mailbox and every new message raises an incident in Kovira. Replies from the requester or from technicians thread back onto the original incident as comments, with attachments and inline images preserved. Conversation matching uses Microsoft's native conversation identifier, standard email threading headers, and a normalised subject fallback, so threads do not split when someone strips the ticket reference from the subject line.

Access is scoped per mailbox to the minimum read permission and revocable from the Microsoft 365 admin centre at any time. There is no tenant-wide admin grant. Change notifications come in close to real time, so an email landing in the inbox produces an incident within seconds, not on a polling cycle. The incoming-mail workflow trigger then fires whatever automation you have wired up: assign by routing rules, set priority by sender domain, send an acknowledgement, populate fields from the email body, escalate, or chain into your existing approval flow.

Loop prevention is built in. Auto-replies, bounce notifications, and Kovira's own outbound mail are detected and skipped, so you do not get a feedback loop the first time someone forwards a vacation responder.

VECTOR network scanner and ATLAS endpoint agents

Automated discovery from the network and every endpoint, with real physical topology.

Point VECTOR at a subnet and it finds the devices, maps how they connect, and keeps your CMDB current. Routers, switches, firewalls, servers, workstations, printers, and IoT all surface as CIs, with no agent required on the scanned devices.

VECTOR also pulls the Layer 2 evidence most network tools skip: LLDP and CDP adjacencies, local and remote switchports, VLAN membership, access and trunk roles, LAG membership, link speed and state, spanning-tree root and port state, and MAC presence. Optional read-only SNMP adds standards-backed chassis and software inventory, environmental sensors, PoE state, 802.1X sessions, and LACP actor, partner, and aggregator evidence. The interactive graph can isolate L2 or L3, colour by VLAN, switch between force, radial, tree, and STP layouts, and open the underlying CI without leaving topology context.

Each VECTOR publishes itself into the CMDB as a device CI when it registers. Other VECTOR instances receive that CI identity with the peer's observed endpoint and public identity keys, allowing them to recognise the scanner, establish an authenticated peer channel, measure the path between sites, and report the resulting WAN relationship back to Kovira.

ATLAS covers the endpoint side. It runs on Windows and Linux machines and reports hardware specs, installed software, and security posture, so endpoint inventory stays accurate without anyone chasing it. Both VECTOR collectors and ATLAS endpoints can be paused, resumed, or uninstalled centrally from the workspace, and heartbeats flag any agent that goes silent. Both are included in every plan, including the free tier.

Microsoft 365 integration

Sync users, groups, and devices from Entra ID and Intune.

If you are running Microsoft 365, Kovira can pull your users, security groups, directory roles, and managed devices straight from Entra ID and Intune. The sync runs in the background, so your CMDB stays current without anyone having to manually update records when someone joins, leaves, or gets a new laptop.

The data flows into the same CI model as everything else, which means you can see an employee, the device they are using, the groups they belong to, and the services they have access to, all in one place. Synced records are correlated with VECTOR and ATLAS data automatically.

Tenant isolation, role-based access control, and recycle bin

Database-level isolation, per-member RBAC overrides, and a soft-delete safety net for CIs.

Tenant isolation is enforced at every layer of Kovira. Every organisation's data is separated at the database level, and the application layer applies tenant context to every query. There are no admin backdoors, no shared tables, and no path for one tenant's data to reach another's. On the MSP plan, the same isolation extends across many client workspaces in one account: each workspace stays fully separated while technicians switch between them without logging out.

Role-based access control gives you four base levels (Owner, Admin, Editor, Viewer) plus per-member overrides for the cases that do not fit a role cleanly. A specific user can be granted a permission above their role or have one revoked below it without changing the role itself, so you can keep the model clean and still handle the contractor who needs read-only access to one workspace section.

Deleted configuration items move into a recycle bin instead of being removed outright. From there you can restore the record back to its prior state or purge it permanently when you are sure. Recycled CIs do not count against your plan’s CI limit while they sit in the bin.

ITILv4 CMDB tool built for practice, not theory

Structured around the ITIL practices that matter most.

Kovira is structured around the ITIL practices that matter most to growing IT teams: Service Configuration Management, Change Enablement, Incident Management, Problem Management, IT Asset Management, and Service Request Management.

This is a purpose-built ITSM tool, not a generic project manager with ITIL labels added on top. The data model, the workflows, the permission structure, and the reporting are designed around how ITIL works in practice. If you are working towards ITIL maturity, or you already follow ITIL and need a CMDB tool that keeps up, Kovira is built for that.