<commit_before>---
title: Introduction
---

# GoCD Business Continuity

This feature makes an active-standby (or active-passive) setup of GoCD Servers possible, to decrease the impact of a failure of your primary GoCD Server or its database node. During a primary GoCD Server failure, it is important that all the agents can be pivoted to use the standby server, without having to be reconfigured. This setup allows for that as well.

## History & current status

Before GoCD `20.6.0`, Business continuity support was made available as a commercial add-on. As part of the open-sourcing of all previously
commercial aspects of GoCD, the add-on was integrated into GoCD core in `20.6.0` and no-longer requires use of an add-on.

> **WARNING**: Unfortunately the _open-source_ business continuity version was discovered to have a **major security vulnerability** in its design, and was
**disabled in GoCD `21.3.0`**, as documented in [the release notes](https://www.gocd.org/releases/#21-3-0).
> 
> As of October 2022, there has not been any major complaint from the community and the project does not currently have 
> the resources or intention to reinstate this capability.

Summarised support matrix:

| GoCD Version         | BC Availability     | BC Security Status                                                                     | Wider GoCD Security Status                                                      |
|----------------------|---------------------|----------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
| <= `20.5.0`          | ✅ Commercial add-on | ✅                                                                                      | Known vulnerabilities exist                                                     |
| `20.6.0` -- `21.2.0` | ✅ Free, core GoCD   | ❌ [See advisory](https://github.com/gocd/gocd/security/advisories/GHSA-f8j3-9pqx-h88g) | Known vulnerabilities exist                                                     |
| >= `21.3.0`          | ❌ Removed           | ✅                                                                                      | Review [here](https://github.com/gocd/gocd/security/advisories?state=published) |
| latest               | ❌ Removed           | ✅                                                                                      | Supported                                                                       |

## Design<commit_msg>Remove unicode<commit_after>---
title: Introduction
---

# GoCD Business Continuity

This feature makes an active-standby (or active-passive) setup of GoCD Servers possible, to decrease the impact of a failure of your primary GoCD Server or its database node. During a primary GoCD Server failure, it is important that all the agents can be pivoted to use the standby server, without having to be reconfigured. This setup allows for that as well.

## History & current status

Before GoCD `20.6.0`, Business continuity support was made available as a commercial add-on. As part of the open-sourcing of all previously
commercial aspects of GoCD, the add-on was integrated into GoCD core in `20.6.0` and no-longer requires use of an add-on.

> **WARNING**: Unfortunately the _open-source_ business continuity version was discovered to have a **major security vulnerability** in its design, and was
**disabled in GoCD `21.3.0`**, as documented in [the release notes](https://www.gocd.org/releases/#21-3-0).
> 
> As of October 2022, there has not been any major complaint from the community and the project does not currently have 
> the resources or intention to reinstate this capability.

Summarised support matrix:

| GoCD Version         | BC Availability        | BC Security Status                                                                   | Wider GoCD Security Status                                                      |
|----------------------|------------------------|--------------------------------------------------------------------------------------|---------------------------------------------------------------------------------|
| <= `20.5.0`          | Yes, commercial add-on | No known issues                                                                      | Known vulnerabilities exist                                                     |
| `20.6.0` -- `21.2.0` | Yes, free in core GoCD | [See advisory](https://github.com/gocd/gocd/security/advisories/GHSA-f8j3-9pqx-h88g) | Known vulnerabilities exist                                                     |
| >= `21.3.0`          | No, removed            | No known issues                                                                      | Review [here](https://github.com/gocd/gocd/security/advisories?state=published) |
| latest               | No, removed            | No known issues                                                                      | Supported                                                                       |

## Design
{'fraction_non_alphanumeric': 0.15257244234180958, 'fraction_numerical': 0.01616400551941652, 'mean_word_length': 1.233274647887324, 'pattern_counts': {'":': 0, '<': 5, '<?xml version=': 0, '>': 13, 'https://': 6, 'lorem ipsum': 0, 'www.': 2, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 45, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '3312570', 'n_tokens_mistral': 1085, 'n_tokens_neox': 1029, 'n_words': 438}