Getting started
This page explains what COD is, which operating model suits you and how a project runs.
As of: November 2026, COD 3.8.6
Documentation
What COD is
COD (Central Operations Dashboard) brings network, security and operations together on one shared inventory. It reads and controls the systems you already run through standard protocols such as SNMP, SSH and vendor APIs, and it ships its own building blocks such as NAC, Backup, TACACS+ and Passkeepr.
The interface is in English. Menu paths in this documentation therefore appear as in the product, for example "Admin Area > Tenant > Modules".
Operating models
| Operating model | Who operates it | What you provide |
|---|---|---|
| Self Hosted | You or your partner, on your own servers running Ubuntu Server | Servers, access to the package repository, network paths to the devices, credentials |
| Shared Hosted | extocode operates the instance | Reachability of the systems COD is to connect to, and the credentials for them |
| Private Hosted | extocode operates the instance. You operate components in your own network | Components in your own network, for example the NAC component, a proxy or jump server, and monitoring, including the hardware for them. Plus reachability of the systems and credentials |
Note: Your partner gives you guide values for your size. Which source address a hosted instance uses to reach your systems is clarified in the project.
How COD is built from services and modules is shown on the page COD architecture. Questions about operation and data are answered in the FAQ on operation and data.
How a project runs
| No. | Step | What happens | Who | More |
|---|---|---|---|---|
| 1 | Choose the operating model | Decide on Self Hosted, Shared Hosted or Private Hosted. With Self Hosted, decide where the servers run | Customer with partner | Operating models |
| 2 | Clarify the requirements | Work through the "Ready for COD" checklist. Prepare names, addresses, LLDP, SNMP, SSH, time and DNS | Customer | Requirements |
| 3 | Installation | With Self Hosted, choose a deployment shape and install the packages. With Shared Hosted and Private Hosted, extocode sets up the instance | Partner or extocode | Installation, Deployment shapes |
| 4 | Initial setup | Setup wizard in the browser, HTTPS, enable modules for the tenant, create locations, roles and users | Partner with customer | Initial setup |
| 5 | Connect the modules | Create assets and network objects, roll out modules per location, connect systems such as Zabbix, firewalls or vCenter | Partner with customer | Modules |
| 6 | Verify and hand over | Check services and queries, resolve open issues, hand operation over to the customer | Partner | Troubleshooting, Support |
Roles
| Role | Responsibility |
|---|---|
| Customer | Chooses the operating model together with the partner. Prepares the network and devices. Provides credentials and firewall rules, and with Self Hosted also the servers |
| Partner | Sells COD in its own name. Introduces COD at the customer. Is the first point of contact for support |
| extocode | Develops COD and delivers the packages through its own repository. Operates Shared Hosted and Private Hosted. Trains the partners |
COD is sold through partners. If you do not have a partner yet, the Partner page explains how extocode puts you in touch with a suitable one. Your partner is your first point of contact. Technical questions to extocode go through the helpdesk form.
Demo
The demo shows the real software with the data of a fictitious industrial company. You do not need an appointment. The demo is reset every night.