How Termina detects and explains deployments.

Termina tracks deployments by observing change signals across connected systems.
It does not rely on a single tool or pipeline and does not require custom agents.

Deployments are inferred from verified events, not manual input.

How Deployments Are Detected

Termina detects deployments by correlating signals from connected systems, including:

• CI/CD pipeline runs

• Artifact or image version changes

• Infrastructure updates

• Runtime state transitions

A deployment is registered when a service’s runtime state changes in a way that affects an environment.

Supported Deployment Sources

Deployments can originate from multiple sources, such as:

• CI/CD tools (builds, releases, pipeline executions)

• Cloud providers (service updates, rollouts)

• Container registries (new image versions)

• Infrastructure changes applied to running services

Termina does not assume a single “source of truth”.
It resolves deployments based on observed outcomes.

Deployment Metadata Captured

For each detected deployment, Termina captures relevant metadata, including:

• Service and environment

• Timestamp

• Source system

• Version or artifact identifier

• Deployment type (application, config, infrastructure)

• Associated pipeline or change reference

Metadata availability depends on the connected systems and their permissions.

Correlating Deployments Across Systems

When multiple systems report related signals, Termina correlates them into a single deployment event.

This prevents:

• Duplicate deployments from appearing

• Partial or misleading change history

• Conflicting timelines across tools

The goal is one deployment, one explanation.

What Termina Does Not Do

To avoid false confidence, it’s important to note what Termina does not do:

• It does not execute deployments

• It does not modify pipelines

• It does not require SDKs or agents

• It does not guess deployment intent

Termina observes and explains deployments after they happen.

Why This Matters

Reliable deployment tracking allows Termina to:

• Explain why production changed

• Attribute incidents to specific changes

• Surface risk from unexpected updates

• Build accurate snapshots over time

Without trustworthy deployment data, production visibility breaks down.