When a device fails, do you rebuild its configuration from memory?
Config backups happen by hand, “when there is time”, and end up scattered across file shares. Devices nobody thinks of stay without any backup. COD brings configuration and database backups together in one interface: across vendors, with schedule and diff. Multi-tenant, as Self Hosted, Shared Hosted or Private Hosted.

Backup hosts in the demo, with status and last run.
Know the feeling?
Every vendor has its own backup path
The pain: Switches, firewalls, servers and databases come from different vendors. Each system has its own export dialog, its own script, or no automated backup path at all.
The consequence: If a configuration is lost, it has to be rebuilt from memory. That means hours of work. Forgotten systems are a silent gap, and in critical-infrastructure (KRITIS) environments the backup evidence for the audit is missing.
How COD solves it: All configuration and database backups run in one interface. Per template you define the source: file/folder download, shell command or MariaDB dump. That way you avoid clicking through every device GUI. Cron schedules back up regularly, and "Execute Now" starts single or many hosts off-schedule at any time.
Segmented networks: precisely the critical systems stay unprotected
The pain: Management network, DMZ, sealed-off production segments: exactly the systems isolated for security reasons are out of reach for the central backup path. So someone backs them up occasionally by hand, or they drop out of the backup entirely.
The consequence: Of all systems, the most critical ones have the oldest config snapshots, or none at all. A real outage risk, and an obvious finding in any audit.
How COD solves it: Per host you store a jump host. Through it COD also backs up systems that are not directly reachable, segmented networks included. These hosts run with the same templates, schedules and retention rules as all the others, instead of as a hand-crafted special case.
After the incident: what changed in the configuration?
The pain: A switch has behaved differently since the weekend, the firewall suddenly blocks a service. Somebody changed something. Without versioned snapshots all that is left is placing two text dumps side by side in an editor, or plain guessing. Creeping config drift only shows once something fails.
The consequence: Troubleshooting drags on, rollbacks hit the wrong spot, the outage stretches out. And without traceable snapshots there is no way to prove what was changed and when.
How COD solves it: COD retains backup snapshots and compares them as a diff: either just the differences or the full text, for folder backups down to the individual file. Contents can be previewed and downloaded as a file, or a whole folder as a ZIP. That is the basis for a targeted restore.
Why COD, not just a feature
In COD, Backup does not stand apart. A firewall from the inventory becomes a backup host with one click, and COD fills in the address and credentials once. Status and recent runs appear on the Home dashboard. The module keeps its own host register, so later changes in the inventory do not arrive there by themselves. Uniform templates and schedules, across vendors and multi-tenant, as Self Hosted, Shared Hosted or Private Hosted.
Connected with
Firewall: a backup host with one click
COD fills in address, user, password, operating system and template from the inventory. Later password changes do not arrive by themselves.
Home: status on the dashboard
Status, errors and recent runs appear on the Home dashboard, next to the cards of the other modules.
Admin Area: one audit
Changes in the Backup service appear in the Admin Area audit, with the user who made them.
See it in the demo. The interface is in English, the data belongs to a fictional company.
Frequently asked questions
See the backup module live
Request a personal walkthrough and we'll show you the backup module hands-on in your own environment, or download all the details about the COD backup module as a datasheet.