Environment Visibility

How Termina shows what’s live, where, and what’s drifting.

Environment visibility is the foundation of production awareness.
Termina separates environments to ensure changes are understood in the correct context.

Production risk is never mixed with non-production noise.

What Is an Environment

An environment represents a distinct runtime context for a system.

Common environments include:

• Production

• Staging

• Preview

• Development

Environments are identified automatically based on connected system signals and metadata.

Production vs Non-Production

Termina treats production differently from all other environments.

Production is:

• Continuously monitored

• Used for risk and incident context

• Prioritized in insights and summaries

Non-production environments are tracked for comparison, validation, and drift detection.

Current Live State

For each environment, Termina maintains a live view of:

• Running services

• Active versions

• Recent deployments

• Configuration and infrastructure signals

This view reflects what is actually running now, not what was intended or configured.

Environment Drift

Drift occurs when an environment deviates from expected or previous state.

Examples include:

• Configuration changes outside CI/CD

• Infrastructure updates without corresponding deployments

• Differences between staging and production

Termina surfaces drift so it can be addressed before it becomes a production issue.

Why Environment Visibility Matters

Clear environment boundaries allow teams to:

• Understand where changes occurred

• Avoid misattributing incidents

• Detect risk early

• Maintain confidence in production state

Without environment visibility, production context breaks down.