Ir al contenido
  •  +49 (861) 88 00 32 00
COD powered by extocode GmbH
  • 0
  • Iniciar sesión
  • English (US) Français Deutsch Español Türkçe
  • Abrir la demo
  • Inicio
  • Resumen COD
    Plataforma
    ResumenPlataforma: clientes y marcaFuncionesProblemas y solucionesArquitecturaDocumentationIntegracionesPrecios
    Operación y Red
    MonitoringRedNetwork Access Control (NAC)TACACS+Captive PortalFirewall
    Seguridad y Resiliencia
    Governance, Risk & ComplianceBackupHypervisorOTPPasskeeprAutomatización
    Soluciones y Más
    NIS2 & CompliancecodPassDocumentación con IA (módulo InfraScan)Abrir la demoReferenciasDescargasFAQ
  • Precios
  • Novedades
    • Blog
    • Hoja de ruta
  • FAQ
  • Sobre nosotros
    • Sobre nosotros
    • Empleo
    • Socios
    • Referencias
  • Academy
  • Contacto
COD powered by extocode GmbH
  • 0
    • Inicio
    • Resumen COD
    • Precios
    • Novedades
      • Blog
      • Hoja de ruta
    • FAQ
    • Sobre nosotros
      • Sobre nosotros
      • Empleo
      • Socios
      • Referencias
    • Academy
    • Contacto
  •  +49 (861) 88 00 32 00
  • English (US) Français Deutsch Español Türkçe
  • Iniciar sesión
  • Abrir la demo
  1. Home
  2. Documentation
  3. Installation
  4. Deployment shapes

Deployment shapes

This page shows how to spread COD across one or more hosts with Self Hosted and which rules always apply.

As of: November 2026, COD 3.8.6

Documentation contents
  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

Documentation

  • Overview
  • Getting started
  • Requirements
  • Names and addresses
  • Network devices
  • Time and DNS
  • Installation
  • Deployment shapes
  • Initial setup
  • Updates
  • Modules
  • Troubleshooting
  • Security
  • Versions
  • Version history
  • Support

The five deployment shapes

No.Deployment shapeHostsWhen it makes sense
1Everything on one server1Getting started, testing, small environments
2COD first, modules later on the same host1The set of modules is not decided yet
3COD server plus module servers for NAC, Backup, Passkeepr, Ansible or TACACS+2 or moreSegmentation, RADIUS close to the network devices, a module in a DMZ
4Existing or remote database servers2 or moreA database team or your backup takes care of MariaDB and PostgreSQL
5Several locations, several instances per host1 or moreSeveral locations share module servers

The shapes can be combined. One server is enough to begin with. You receive the setup script command together with the repository credentials.

Your partner gives you guide values for your size.

Services and where they run

ServiceWhereInstances per host
COD (cod-backend) with web interface and collectorCOD serverone
Key service (cod-jwks)COD server, optionally its own serverone
Cache (Redis, Valkey on Ubuntu 26.04)always the COD serverone
NAC with FreeRADIUSCOD server or its own serverone
TACACS+COD server or its own serverone, single tenant
BackupCOD server or its own serverseveral possible
Passkeeprthe COD server where possibleseveral possible
AnsibleCOD server or its own serverseveral possible
Hypervisoralways the COD serverseveral possible

Fixed rules

  • Hypervisor always on the COD server. COD reaches the service only locally.
  • Passkeepr on the COD server where possible.
  • Cache always on the COD server.
  • Only once per host: NAC (one FreeRADIUS installation per host), TACACS+ (single tenant), COD (cod-backend) and the key service (cod-jwks).
  • Several times per host: Backup, Passkeepr, Ansible and Hypervisor. Each instance belongs to one location and has its own module address.
  • Rollout wizard: It covers only Ansible, Backup, NAC and Passkeepr. You set up TACACS+ and Hypervisor manually on the host.
  • Ansible on its own server: By default the service listens only locally. If it runs on a host of its own, you set the network address there. Agree on running it on a separate server with your partner.
  • Trusted network: The connection between COD and module servers belongs in a trusted network.

Module servers

The setup script runs on every module server just as on the COD server. The interface never talks directly to a module. Every call goes through COD. The modules fetch the signing keys from the key service and check every sign-in with them themselves. Network devices speak RADIUS directly with the NAC server and TACACS+ directly with the TACACS+ server.

Customers and partners receive the list of connections and firewall rules as part of the project.

Several locations

  • One COD serves all locations.
  • Each location gets its own Backup instance with its own server register and its own storage. Several locations can also share one instance. They then use the same module address.
  • The same pattern applies to Passkeepr and Ansible.
  • You maintain the module addresses per location under "Location > Module URLs".

Your own database servers

ComponentDatabase engine
CODMariaDB
GRCPostgreSQL
BackupMariaDB
NAC and FreeRADIUSMariaDB, two databases with one shared user
PasskeeprPostgreSQL
TACACS+PostgreSQL

Prepare the following on your database servers:

  1. The servers accept connections from the COD server and the module servers over the network.
  2. Each database gets its own user. This user has rights on its own database only. The exception is NAC, with one user for both databases.
  3. PostgreSQL runs version 18 or later. The installation rejects older versions.
  4. PostgreSQL authenticates clients with scram-sha-256, per database for the addresses of the hosts that connect.
  5. NTP also runs on the database servers.

Customers and partners receive the list of connections and firewall rules as part of the project.

Shared Hosted and Private Hosted

With Shared Hosted and Private Hosted, extocode operates the instance. With Private Hosted, you provide and operate components in your own network yourself, for example the NAC component. See Getting started: operating models.

Further reading

  • COD architecture
  • Installation
  • Requirements
  • Updates with separate servers
  • FAQ: installation and updates
← Previous: InstallationNext: Initial setup →
Folgen Sie uns
​
  • Resumen COD
  • Funciones
  • Demo
  • Precios
  • Integraciones
  • NIS2
  • codPass
  • Referencias

Help

  • FAQ
  • Documentation
  • Descargas
  • Contacto

Kotzinger Straße 21 • 83278 Traunstein • Deutschland

  • ​+49 (861) 88 00 32 00
  • ​info@extocode.com
Datenschutz Impressum ​
Copyright © extocode GmbH
English (US) Français Deutsch Español Türkçe

Utilizamos cookies para proporcionarle una mejor experiencia de usuario en este sitio web. Política de privacidad

Rechazar Aceptar