Updates
This page describes how to update, back up and remove COD with Self Hosted. If extocode operates COD for you, extocode installs new versions itself.
As of: November 2026, COD 3.8.6
Documentation
Installing an update
You update COD like any other Ubuntu package. Run on every host:
sudo apt update
sudo apt upgrade
If packages were renamed, upgrade is not enough. Then you need:
sudo apt full-upgrade
| Version | Reason for full-upgrade |
|---|---|
| 3.8.0 | The vault is now called Passkeepr (Stronghold until 3.7) |
| 3.8.1 | The package with the help videos is now called cod-help |
- Each service applies its database changes itself at start-up. There is no separate migration step.
- Afterwards, check the installation as described under Check the installation.
apt policy cod-backendshows the installed version.
What is new is listed on the Roadmap page, under Versions and in the Version history. The version history also names what you need to do for each release when you update.
No automatic updates by default
By default the COD packages are not set up for automatic updates. Automatic updates are only available on explicit request. Schedule your updates yourself.
Backup before database changes
Before a database change, an update creates a backup of its own. This applies to the databases of the platform, of GRC and of the Backup, NAC and Passkeepr modules. The exception is the switch to Passkeepr with COD 3.8. The vault starts empty there.
Important: This backup does not replace your regular data backup.
Order with separate servers
| Case | Order |
|---|---|
| Update to 3.8.6, Passkeepr on its own server | Update COD and Passkeepr together. The Passkeepr module reaches 3.8.6 with COD or before COD |
| General rule for all module servers | Agree on the order with your partner. |
The notes for each version are on the Roadmap page.
Going back to an earlier version
Agree on a rollback with your partner beforehand. Technical questions to extocode go through the helpdesk form.
Backing up COD itself
Include all COD servers and database servers in your regular data backup. These parts belong to it:
| What | Why |
|---|---|
| COD configuration with the keys of the installation | Without these keys COD does not start, and encrypted credentials are lost |
| Signing keys of the key service | Modules use them to check sign-ins |
| Configuration and key of each module | Each module has a key of its own |
| Configuration of the TACACS+ service with its master key | The master key must never change |
| All databases (MariaDB and PostgreSQL) | Data of COD, GRC and all modules |
| Storage of the Backup module | the backed-up device configurations |
You receive the complete list as part of the project.
Important: Back up the keys of the installation right after the setup wizard. Without them COD does not start, and encrypted credentials are lost.
Removing COD
sudo apt purge 'cod-*'
apt purgeremoves the packages. Configuration and data stay on the host.- Before reinstalling on the same host, clear the cache (Redis or Valkey). See Troubleshooting.
Moving from older installations
Up to COD 3.6.5, COD ran as a ZIP installation. Since 3.7.0 there are packages for Ubuntu. An existing installation can be switched to the packages once, following a guide. Ask your partner about it.
Shared Hosted and Private Hosted
If extocode operates COD for you, extocode installs new versions itself.
Further reading
- Roadmap with notes per version
- Versions
- Version history with update notes
- Deployment shapes
- Troubleshooting and diagnosis
- FAQ: installation and updates