> For the complete documentation index, see [llms.txt](https://docs.vega365.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vega365.com/tandem/recovering-from-recorder-failure/third-party-software.md).

# Third Party Software

Why PSIM, access control, analytics and every other XProtect integration keep working through a failover, with nothing to configure.

## Third-party integrations

XProtect rarely stands alone. PSIM platforms, access control, video analytics, LPR, video walls, alarm management, and custom integrations all connect to it, and each one holds its own view of which cameras live on which recorder.

Tandem is transparent to all of them, for one reason: **it is transparent to XProtect.**

### Why it is transparent

A Tandem cluster presents itself to XProtect as a single recording server with a single identity. The two members share that identity, and only one is attached to the Management Server at any moment. XProtect sees one recorder with one set of cameras—before, during, and after a failover.

Integrations learn about recorders and cameras from XProtect. Whatever XProtect sees, they see. So when the member serving the cluster changes:

* **The recorder identity does not change.** It is the same recorder.
* **The cameras do not move.** They stay on the same recorder, under the same names and IDs.
* **Nothing about the configuration changes.** The integration has nothing new to discover.

From an integration's point of view, no failover has happened.

<figure><img src="https://92057524-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fi0mCLda4cGtI3Jwb6IQA%2Fuploads%2F5OMF2oUf53ZcLaCxQW6Q%2Ftandem_integrations_transparency.svg?alt=media&amp;token=e8193a78-6e2e-4fad-9b53-1cb462fe5aed" alt="" width="563"><figcaption><p>Integrations see XProtect. XProtect sees one recorder.</p></figcaption></figure>

### What this covers

Anything that integrates with XProtect through its standard interfaces inherits the same transparency, including:

| Category                        | Examples                                                  |
| ------------------------------- | --------------------------------------------------------- |
| PSIM and command-and-control    | Incident management, site-wide situational awareness      |
| Access control                  | Door events linked to cameras, credential-triggered video |
| Video analytics                 | Object detection, behavior analysis, forensic search      |
| LPR / ANPR                      | Plate recognition bound to specific cameras               |
| Video walls                     | Wall layouts and operator-driven wall control             |
| Alarm and event management      | Rules, alarms and event-driven actions                    |
| Plugins and custom integrations | MIP plugins, SDK- and API-based applications              |

The list is illustrative, not a compatibility matrix. Tandem doesn't rely on integrations knowing about it, so there is no per-vendor support to check.

### What you do not need to do

* **No re-pointing.** Integrations are not reconfigured to find cameras on another recorder, because the cameras never leave the one they are on.
* **No mapping of camera pairs.** There is no primary camera and backup camera for an integration to track — one camera, one identity.
* **No redundancy configuration in the integration.** The integration does not need its own failover settings, scripts, or awareness of the second member.
* **Nothing to do from the integration vendor.** No plugin, integration, update, or Tandem-specific support is needed on their side.

### What integrations experience during failover

An integration that is pulling live video from the cluster at the moment of failure experiences what Smart Client does: its connection to the failed member drops for a few seconds and is automatically restored.

### Where Tandem fits alongside RMF

Vega Systems' [RMF](https://docs.vega25.com/redundancy-management-framework/introduction) provides active-active redundancy across independent sites or systems, with the cybersecurity benefits of keeping those systems isolated from each other. In that design, two distinct recorders record a camera, and integrations that need to follow a failover must be aware of both—RMF provides integrations for exactly that.

Tandem takes the opposite approach inside a single XProtect system: one recorder identity, two members behind it. That makes it a natural fit for deployments with a large or varied set of integrations that aren't redundancy-aware, where adapting each one isn't practical.
