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
The five deployment shapes
| No. | Deployment shape | Hosts | When it makes sense |
|---|---|---|---|
| 1 | Everything on one server | 1 | Getting started, testing, small environments |
| 2 | COD first, modules later on the same host | 1 | The set of modules is not decided yet |
| 3 | COD server plus module servers for NAC, Backup, Passkeepr, Ansible or TACACS+ | 2 or more | Segmentation, RADIUS close to the network devices, a module in a DMZ |
| 4 | Existing or remote database servers | 2 or more | A database team or your backup takes care of MariaDB and PostgreSQL |
| 5 | Several locations, several instances per host | 1 or more | Several 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
| Service | Where | Instances per host |
|---|---|---|
COD (cod-backend) with web interface and collector | COD server | one |
Key service (cod-jwks) | COD server, optionally its own server | one |
| Cache (Redis, Valkey on Ubuntu 26.04) | always the COD server | one |
| NAC with FreeRADIUS | COD server or its own server | one |
| TACACS+ | COD server or its own server | one, single tenant |
| Backup | COD server or its own server | several possible |
| Passkeepr | the COD server where possible | several possible |
| Ansible | COD server or its own server | several possible |
| Hypervisor | always the COD server | several 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
| Component | Database engine |
|---|---|
| COD | MariaDB |
| GRC | PostgreSQL |
| Backup | MariaDB |
| NAC and FreeRADIUS | MariaDB, two databases with one shared user |
| Passkeepr | PostgreSQL |
| TACACS+ | PostgreSQL |
Prepare the following on your database servers:
- The servers accept connections from the COD server and the module servers over the network.
- 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.
- PostgreSQL runs version 18 or later. The installation rejects older versions.
- PostgreSQL authenticates clients with scram-sha-256, per database for the addresses of the hosts that connect.
- 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.