> ## Documentation Index
> Fetch the complete documentation index at: https://docs.stackshift.cloud/llms.txt
> Use this file to discover all available pages before exploring further.

# Services view

> Track stack-backed services and databases in one place with health, backup posture, and upgrade cues.

<Tip>
  **Live.** This area is documented as current, user-reliable behavior.
</Tip>

## Goal

Use the Services view as a platform operations inventory, not just a list page.

## Prerequisites

* Live stacks or databases

## Workflow

<Steps>
  <Step>
    Review service status and health from the operations surface.
  </Step>

  <Step>
    Use service cards to jump into more specific detail when needed.
  </Step>

  <Step>
    Read backup and update signals as operational cues, not decoration.
  </Step>
</Steps>

## What appears in the service hub

* Template-backed stacks and direct stacks
* Standalone managed databases
* Operational cues like backup posture, update availability, node assignment, and recovery state

## Reading the cues

* Health and status tell you whether a service is actually serving.
* Update availability reflects template upgrade status (update\_available, upgrade\_blocked).
* Backup posture flags services without a usable recent backup.
* Node assignment shows where the service landed, which matters when one node is unhealthy.
* Recovery state surfaces an in-flight or failed operation so you catch it from the hub, not after the fact.

## Expected result

<Check>
  You can reason about the live service ecosystem from one surface.
</Check>

## Related guides

<CardGroup cols={2}>
  <Card title="Operations overview" href="/operations/operations-overview">
    The operations area is the cross-resource health and runtime visibility surface for StackShift.
  </Card>

  <Card title="Recovery states, logs, and troubleshooting" href="/operations/recovery-logs-and-troubleshooting">
    Read the operation state on a resource — its status, current step, attempt count, retryable flag, and last error — together with logs, instead of treating a single “error” badge as the whole story.
  </Card>

  <Card title="Stack logs, health, and placement" href="/stacks/logs-health-and-placement">
    Use the stack detail, logs, and placement information to understand how the stack is actually running.
  </Card>
</CardGroup>