> ## 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.

# Managed database overview

> How StackShift databases fit into the platform and how they differ from stack-hosted stateful services.

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

## Goal

Understand the managed database model before creating or restoring one.

## Prerequisites

* Basic knowledge of relational databases

## Workflow

<Steps>
  <Step>
    Treat databases as their own resource type, not as special cases of stacks.
  </Step>

  <Step>
    Use database views for connection info, backups, and restore flows.
  </Step>

  <Step>
    Expect current backup behavior to be S3-backed, not the older AWS/EBS model described in stale docs.
  </Step>
</Steps>

## What the database surface includes

* Provisioning and health state separate from stacks
* Dedicated credentials and connection details
* Dedicated backup and restore workflows

## How this differs from a database inside a stack

A managed database is tracked as its own platform resource. A database container inside a stack is still part of that stack. The operational surfaces, backup flows, and recovery expectations are different, so it is worth choosing deliberately instead of treating them as interchangeable.

## Expected result

<Check>
  You can reason about StackShift databases as a separate platform surface.
</Check>