General & Platform
COD: General Questions
The COD is a vendor-independent platform that connects your IT infrastructure on one shared inventory. Rather than replacing siloed solutions, the COD connects your existing systems and brings together their control, documentation and reporting, as far as the integration allows.
For IT departments and service providers that operate heterogeneous infrastructures spread across multiple sites and want to bring operations, documentation, and compliance together in one place.
The COD combines its own solutions with integrations. Capabilities such as NAC, backup, OTP, GRC, or virtual switch management are delivered as standalone, vendor-independent solutions. Existing third-party systems such as directory services, monitoring, your CMDB/asset management, or firewalls remain in place and are connected. You keep the mechanisms you know and gain central transparency and automation.
All platform modules are active by default and already installed out of the box. In addition, there is vulnerability management with COD-VAS. It is a separately ordered add-on and is currently in preparation.
As separate building blocks we include: Network Access Control (NAC), TACACS+, configuration backup, the Passkeepr vault, the OTP module, GRC (incl. NIS2 readiness), hypervisor management (for virtual switches) and network documentation and visualisation (L2/L3 topology) incl. firewall and report management.
Through integrations we also connect what you already run: directory services, Zabbix for monitoring, i-doit as a source for read-only import. What stays and where the limits are is on the Integrations page.
COD comes in three operating modes. Self Hosted runs in your own infrastructure or in that of your partner. Since version 3.7.0 it is installed and updated as a package for Ubuntu Server. Your operational data then stays with you or your partner. Shared Hosted and Private Hosted are instances that extocode operates for you. The operating modes are also listed on the Pricing page.
With Self Hosted, COD runs in your own environment and the data stays under your control. With Shared Hosted and Private Hosted, extocode operates the instance for you and processes the data on your behalf. Access is governed by roles. Tenants and sites are separated logically and by access rights.
Through role-based access control (RBAC). Permissions are assigned in fine-grained detail per module, role, and site. For sign-in, existing directory services can be connected via LDAP/Active Directory, and local accounts are supported as well.
Yes. The COD is multi-tenant and multi-site capable. Data and permissions are separated per site, and users can switch between the sites they are authorized for.
The GRC module digitizes the risk matrix, asset-based risk management, and policy and threat catalogs. Combined with the central asset and dependency context, the COD supports the evidence and documentation obligations under NIS2.
COD works with several vendors. In the network, nine vendors are collected: Allied Telesis, Arista, Aruba, Cisco, Extreme, Juniper, MikroTik, Ruijie and Sophos. Allied Telesis, Cisco and Ruijie can be configured. Firewalls can be managed through OPNsense, pfSense, DynFi and AIMdefense. We also connect directory services (LDAP/Active Directory), Zabbix and i-doit as a source for read-only import. The aim is operation with your existing, heterogeneous infrastructure.
Security is built in: role-based access, login with a second factor (TOTP with recovery codes), encrypted storage of sensitive data and a field-level audit log in the GRC module. Since COD 3.7.8, the Admin Area also keeps an audit across the modules. Tenants and locations are separated logically and in their access rights. With Self Hosted, data and access stay in your environment.
All platform modules are included in the Seat and Tenant Fee prices. There is no separate licensing for individual modules. Only the COD-VAS add-on for vulnerability management is ordered separately. COD is sold through partners, so your quote comes from a partner. Tell us what you need using the contact form and we will put you in touch with the right partner.
Feature Overview
It covers the core features currently shipping, condensed module by module into one description per feature. We continuously maintain the complete, technically detailed picture. Just ask about a specific project.
Yes. All modules are part of the platform. Only the COD-VAS add-on is ordered separately.
In three operating models. Self Hosted runs in your infrastructure or your partner's, and the operating data stays there, except for messages a user deliberately sends to extocode through the feedback channel. Shared Hosted and Private Hosted are instances operated by extocode.
Integrations
No. Zabbix, your firewalls, your vCenter and your directory keep running, and COD connects them. Where something is missing, COD brings building blocks of its own that fit in.
No. codPass runs on its own and not as part of COD. It is not getting any new features. This does not imply any commitment to further versions. The vault in COD is called Passkeepr.
NIS2 & Compliance
COD makes your preparation for the NIS2 requirements demonstrable, with asset transparency, asset-based risk management and traceable evidence. It makes no statement about your compliance, which depends on your measures. The legal assessment of your obligations remains with you or your legal counsel. COD does not replace legal advice.
Not if you choose Self Hosted. Your operating data then stays in your infrastructure, except for messages a user deliberately sends to extocode through the feedback channel. With Shared Hosted and Private Hosted, extocode operates the instance. Compliance data sits in its own PostgreSQL database.
The GRC module works on the same assets COD keeps in its inventory. Your risk assessment refers to the specific asset, not to an outdated list. GRC does not show an operating state of the device.
Pricing
These are non-binding recommended guide prices (net, EUR/month unless stated otherwise). Your final price depends on the number of Seats, the hosting model, the asset volume and the service level. COD is sold through partners, so your quote comes from a partner who calculates their own price.
Entry starts at a minimum of 2 seats at €47.50 each plus a tenant fee starting at €8 (self-hosted). VAS and service packages are added as needed.
Yes. Seats carry a 10% term discount with a 36-month contract term. For COD-VAS there is no recommended price for tenants with more than 25,000 assets. The price is then agreed individually.
Demo and walkthrough
Yes. Open the demo and choose an account. You do not need an appointment. You see the real software with the data of an invented industrial company. We reset the demo every night around midnight.
If you like, yes. We demonstrate COD hands-on using scenarios from your environment or with a prepared sample environment, whichever works best for you.
Yes. The personal walkthrough is free and without any obligation. There is no sales pressure.
All that interest you: from network & assets through NAC, firewall & VPN, GRC and monitoring to backup. You set the focus.
Network & Access
Monitoring
That depends on the check interval you set per location through a cron. This check is part of the Firewall module. Alerts from your monitoring come from Zabbix.
No. Throttling per firewall prevents repeated mails about the same problem. You control Zabbix alerts in Zabbix, and COD does not suppress them.
Yes, if you want to use monitoring. The module is an integration and requires your own Zabbix server. Zabbix detects and alerts, COD reads, acknowledges and creates hosts from the asset. Zabbix is not part of the delivery.
Network Access Control (NAC)
- Type: COD-native, vendor-independent NAC solution based on RADIUS
- Authentication: 802.1X (EAP with certificates), MAC authentication
- Access control: dynamic VLAN assignment (Tunnel-Private-Group-Id, Cisco-AVPair, Egress-VLANID), client groups with priorities
- PKI: integrated certificate management for 802.1X (CA/leaf certificates, CRL, PKCS#12 export)
- NAS management: switches/access points with shared secret
- Logging: authentication and accounting logs (success/failure, sessions), connection statistics
- Import: CSV bulk import (MACs, VLANs, groups) with validation and conflict detection
A COD-native, vendor-independent solution for Network Access Control based on RADIUS. It controls and logs network access centrally in the COD.
Usually not. COD-NAC is multi-vendor capable and works with existing 802.1X- or MAC-capable infrastructure.
802.1X (EAP, with certificates) as well as MAC authentication.
Dynamically via RADIUS attributes. Client groups with priorities let you bundle rules. A device can be assigned to any VLAN you have created, including a dedicated quarantine or guest VLAN. COD-NAC does not check whether a device is compliant.
Yes. The CSV bulk import handles MAC addresses, VLAN assignments, and groups, including validation and conflict detection.
From the integrated PKI: creation of CA and leaf certificates, CRL management, and PKCS#12 export for distribution to clients.
COD does not connect to an existing Windows CA. For 802.1X, COD brings its own certificate authority.
COD does not connect to PacketFence. Network access control in COD works with FreeRADIUS.
Through authentication and accounting logs as well as per-client connection statistics.
Captive Portal
No. Thanks to role-based delegation, reception or non-technical staff can handle guest management themselves, without admin rights and without an IT ticket.
It is automatically disabled and removed. Forgotten legacy accounts and permanently valid passwords are a thing of the past.
They are time-limited vouchers instead of permanent passwords. COD generates them for the captive portal of your OPNsense firewall, with validity and expiry, as a QR code or printable PDF. Expired vouchers are deleted. No one copies a password off a whiteboard anymore.
TACACS+ (Device Administration)
- Type: TACACS+ AAA server for administering network devices (authentication + authorization)
- Protocol: TACACS+ (port 49), RFC 8907. For switches, routers, firewalls, access servers
- Authorization: PERMIT/DENY rules, pattern-based command authorization, privilege levels 1–15
- RBAC: roles link user group ↔ device group ↔ authorization rule (different permissions per device)
- Crypto: Argon2id (passwords), AES-256-GCM (sensitive fields)
- Management: REST API, separate from the server daemon
- Operation: PostgreSQL, Python
Any TACACS+ client per RFC 8907, such as switches, routers, and firewalls. The solution is not vendor-specific.
Yes. Through roles (user group × device group × rule), permissions can be assigned granularly per device group.
Yes. Command authorization works on a pattern basis.
As an Argon2id hash, not reversible.
For managing users, clients, groups, and rules, separate from the actual server daemon.
Levels 1 to 15, configurable per user.
Via an enabled flag. Disabled entries are skipped during evaluation.
Switch Automation
- Type: Automated switch configuration via Ansible
- Vendors: Allied Telesis (AWPlus), Cisco IOS, Ruijie (CLI fallback)
- Profiles: PORT (interface), AUTH (802.1X/AAA), VLAN (create/delete), PORT_ACTION (cable test, port restart)
- Security: credentials encrypted in the vault. Automatic config backup before every change, selective restore
- Transport: SSH (libssh/paramiko), legacy algorithms for older devices
- Execution: asynchronous with task/result logging
Allied Telesis, Cisco IOS, and Ruijie (via CLI fallback).
No. After the initial rollout, credentials are stored encrypted in the vault and reused.
A backup of the current configuration is created automatically. A restore to an earlier state is possible.
Yes, via profiles (PORT, AUTH, VLAN) directly from the COD.
Yes. Legacy algorithms (host key, key exchange, cipher) are supported, and paramiko is used when needed.
No. Only the individual interface is reset (shutdown/no shutdown), and the device stays in operation.
There is no lock. Requests are processed sequentially, and parallel manual CLI changes should be avoided in the meantime.
Security & Identity
Vulnerabilities (VAS)
COD-VAS is an optional add-on and is currently in preparation. The plan is to bring findings and their handling together with COD's assets. Findings are meant to become prioritized and trackable instead of just appearing as a list.
The plan is to break findings down by severity and present them so you immediately see where urgent action is needed. You are meant to work on the risk, not on the length of the list.
COD-VAS is an add-on to the COD platform and is in preparation. We will describe how it is operated when it is released.
OTP Authentication
- Type: COD-native, central OTP management
- Standard: TOTP (RFC 6238), SHA-1/256/512, 6–8 digits, 30-second interval
- Provisioning: QR code or manual entry. Compatible with common authenticator apps (Google, Microsoft, Authy)
- Sharing: private (user-bound) or public tokens. Group delegation for teams
- Isolation: site-specific (separated per tenant)
- Integration: assignment of tokens to assets. Also usable for users from Active Directory. The second factor of the COD sign-in is separate from it
It is the shared store for time-based one-time passwords (TOTP) your team uses to sign in to other systems, such as vendor portals or device logins. Codes no longer have to live on one person's phone. The second factor of the COD sign-in is a separate system.
Yes. It generates standard otpauth:// codes and works with any RFC 6238-compatible app.
Yes. Tokens can be shared across a team via groups, while private tokens remain bound to individual users.
The codes in the OTP module are stored centrally in COD, not on the smartphone. For the second factor of the COD sign-in there are recovery codes, and an administrator can reset the factor.
Private tokens are not in the open pool, they appear with their owner. Open and group tokens are seen by the module users and group members concerned. Anyone who may read the module can also reach the setup key of every token they can see.
Yes. All tokens and groups are isolated per site.
Through the COD's role-based access control and site isolation. Storage is in the secured database.
As a shared store for the one-time passwords of other systems. Multi-factor sign-in to COD itself is a separate system within user management.
codPass
codPass runs on its own and not as part of COD. It is not getting any new features. This does not imply any commitment to further versions.
No. codPass has no browser plugins.
Passkeepr: Password Vault (from COD 3.8)
Available. Passkeepr has been part of the platform since COD 3.8. Until COD 3.7 the vault was called Stronghold. Passkeepr offers zero-knowledge encryption, personal, shared and enterprise vaults, and a browser extension for Chrome and Firefox.
- Type: Zero-knowledge vault for passwords and secrets (end-to-end encrypted)
- Principle: The server stores only ciphertext. Plaintext, the master password, and private keys never reside on the server.
- Vaults: personal, shared and enterprise vaults (enterprise vaults belong to the organisation, two or more Keepr admins run them)
- Sharing: whole vaults and single items, with “Can edit” or “Read-only”, to people or local groups, also by invite link
- Recovery: Emergency Kit with a recovery phrase (24 words) and the Secret Key at setup
- Crypto: Argon2id (key derivation), X25519 (keys), AES-GCM (items)
- Sign-in: JWT (ES384) via the COD login, verified through JWKS
- Operation: PostgreSQL, reachable only through the COD proxy, rate limiting, logging
No. The server holds only encrypted data. Without your master password, which exists only on the client side, that data is worthless even in a full database dump. A deliberate exception are enterprise vaults: the organisation account can open them too, and its unlocks and changes are logged.
On the unlock page you choose “Forgot your master password?” and enter the recovery phrase from your Emergency Kit. Then you set a new master password. Passkeepr then shows a new Emergency Kit, and the old one stops working.
Yes. Through shared vaults, through single items or through local groups of your location, with “Can edit” or “Read-only”. Invite links are possible too: valid for seven days and usable once. Everything is public-key encrypted.
The vault key is renewed. The removed member loses access to everything stored afterwards. What they have already seen stays seen: after someone leaves, change the credentials at the systems themselves.
No. The vault name is encrypted. The server knows neither vault names nor item titles, addresses, customers, passwords or notes.
The kit restores access to your key, for example after a forgotten master password. Your regular backup protects against data loss on the server.
Through the COD login (JWT, ES384, verified via JWKS). The vault is reachable exclusively through the COD proxy. Your COD role needs the permission for the Passkeepr module.
No. With COD 3.8, every Passkeepr database starts empty. There is no automatic transfer from Stronghold. You enter items again or read them in through the import.
Yes. The import reads files from Bitwarden, 1Password, KeePass, sysPass, CSV and JSON, including password-protected ones. With Bitwarden, the passkeys come along. On request, the import sorts the items into several vaults by the groups in the file. Since COD 3.8.3, the sysPass import also reads a groups file from the sysPass database and puts each group into a vault of its own.
Operations & Resilience
Backup
- Type: COD-native, vendor-independent backup solution
- Target systems: Switches, firewalls and servers as well as MariaDB/MySQL databases
- Methods: Command on the host, file or folder, database dump
- Scheduling: cron per host or template
- Encryption: optional per host/template, for locally stored backups except folder backups
- Retention: by count or age (days), automatic cleanup
- Comparison: diff view of two backup states
- Storage: local
- More: jump host/bastion, pre-backup scripts, failure emails as an operational aid, disk-space monitoring, serial number check
Configurations of switches, firewalls and servers as well as MariaDB/MySQL databases. The solution is vendor-independent and can be extended through OS templates.
Freely configurable via cron, per host or per template, e.g., hourly, daily, or weekly.
Optionally. Encryption can be switched on per host or template. It applies to the backups COD-Backup stores locally. Folder backups are excluded.
Configurable by count or age in days. Once the limit is reached, the oldest states are deleted automatically.
Yes. A diff view shows the changes between two versions line by line.
The host then shows the ERROR status and the failure is visible in the overview. If mail delivery is switched on, the backup service also sends a failure email. It is an operational aid. We do not commit to active alerting.
No. The former offloading to an SCP server was removed in COD 3.7.11. You download backups through the interface.
Yes, through a jump host.
Backups can be downloaded through the interface. Restoring to the device is done manually with the usual tools.
Hypervisor Management (virtual switches)
- Type: Management of virtual switches (no VM or host management)
- Platform: VMware vCenter / ESXi
- Objects: standard vSwitches and port groups with VLAN ID. NIC assignments and security settings are displayed
- Functions: read inventory (datacenter → cluster → host → vSwitch → port group), create vSwitch, create/modify/delete port group
- Dry run: simulate port group changes in advance (Port Groups screen)
- Multi-host: operations across multiple hosts, result per host
- Interface: REST API, sign-in via vCenter account
Virtual switches and port groups on VMware. It deliberately does not control the lifecycle of VMs or hosts.
VMware vCenter and ESXi (via the VMware API pyVmomi). Other platforms such as Hyper-V or KVM are not supported.
Yes. Each port group is assigned a VLAN ID. COD creates new port groups with a VLAN ID from 1 to 4095. In the inventory, 0 means untagged and 4095 means trunk all.
Yes, on the Port Groups screen. There, every change to the hosts can be simulated in advance as a dry run, without touching anything. The wizard under Structure, which you use to create new vSwitches and port groups, has no dry run and writes to the hosts immediately.
COD shows active, standby and unused NICs per vSwitch in the inventory. When you create a vSwitch, you pick the physical NICs it uses as uplinks on each host. Load balancing and security policies are still set in vSphere.
With vCenter credentials (host, user, password) in each call.
Yes. Operations accept a host list, and the result reports success or failure per host.
It provides the complete vCenter object tree as read access, for example for dashboard views or documentation.