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.

We include the following as standalone, vendor-independent solutions: Network Access Control (NAC), backup/disaster recovery, OTP authentication, GRC (including NIS2 support), hypervisor management (for virtual switches), as well as network documentation and visualization (L2/L3 topology) including firewall and report management.

Through integrations, we also connect existing third-party systems: directory services, monitoring, and your CMDB/asset management.

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.

The COD is multi-vendor capable. In network management, it supports Cisco, HPE, Allied Telesis, Ruijie, and MikroTik, among others. Firewalls can be managed via OPNsense, pfSense, DynFi, and AIMdefense. In addition, we connect directory services (LDAP/Active Directory), monitoring, and your CMDB/asset management. The goal is to operate with your existing, heterogeneous infrastructure.

Security is built in from the ground up: role-based access, sign-in with a second factor (TOTP with recovery codes), encrypted storage of sensitive data and a field-level audit log in the GRC module. A shared log for the other modules is being built. Tenants and sites are separated logically and by access rights. With Self Hosted, data and access stay within 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.

Yes. All modules are part of the platform. Only the COD-VAS add-on is ordered separately.

Yes. COD runs in your environment, and you retain full data sovereignty, a good fit for KRITIS and NIS2 requirements.

No. codPass is a standalone product and not part of COD. The vault integrated into COD is Stronghold. Browser plugins are not part of codPass.

No. COD can run fully on-premises and is KRITIS-ready. Compliance data resides in a dedicated PostgreSQL database under your full control.

The GRC module works on the same assets that COD-Network detects and maintains automatically. Your risk assessment refers to the actual asset including its live status, not to an outdated list.

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.

Yes. The live demo is free and without any obligation. There is no sales pressure.

Any that interest you: from Network & Assets to NAC, firewall & VPN, GRC, and monitoring, all the way to vulnerability management and backup. You set the focus.

No. Per-firewall throttling prevents repeated alerts about the same issue, and you schedule planned maintenance centrally in the calendar, so monitoring does not trigger without reason.

Monitoring is built directly into COD as a module and uses the same data as your network inventory. Existing systems such as Zabbix can be connected through integrations.

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.

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 or AIMdefense 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.

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.

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.

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.

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 only the respective owner. Public or group tokens are visible to the members of the group as well as administrators.

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.

No. codPass currently does not offer browser plugins. Managing passwords, secrets, and OTP happens directly in the application.

Because openness builds trust: the source code and the security mechanisms are transparent and verifiable. For a secrets manager, that is a security and quality feature, not an afterthought.

• 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: one personal vault per user, plus shared team vaults (roles: OWNER/MEMBER)
• Sharing: individual entries across users, with READ/WRITE permission and expiration date
• Recovery: one-time recovery code at setup
• Crypto: Argon2id (key derivation), X25519 sealed box (key wrapping), AES-GCM (entries), HKDF
• 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.

At setup you receive a one-time recovery code. It lets you restore access to your key and set a new master password.

Yes. Either through a shared vault or by sharing individual entries (with permission and expiration date). Both are public-key encrypted.

The vault key is reissued for the remaining members, and the removed member loses access to future content.

No. The vault name is encrypted, and only the icon is stored in plaintext.

The recovery code restores access to your key (e.g., after a forgotten master password). The COD's regular backup protects against server-side data loss.

Through the COD login (JWT, ES384, verified via JWKS). The vault is reachable exclusively through the COD proxy.

Configurations of all devices reachable via SSH as well as MariaDB/MySQL databases. The solution is vendor-independent and extensible via 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.

Yes. Optionally, COD-Backup transfers SSH command and SFTP backups to an SCP server after every successful run and deletes the local copy. The retention rule then applies on the SCP server.

Yes, through a jump-host tunnel.

Backups can be downloaded through the interface. Restoring to the device is done manually with the usual tools.

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.