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

# Deploy your first workload

> Choose the right first deployment path based on whether you are deploying an app, a Compose service, or a curated template.

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

## Goal

Make the first successful deployment without picking the wrong runtime surface.

## Prerequisites

* At least one healthy node
* Optional GitHub connection for project deployments

## Workflow

<Steps>
  <Step>
    Use a project if you have an app or Docker image.
  </Step>

  <Step>
    Use a stack if you already have a Compose workload.
  </Step>

  <Step>
    Use a template if you want a pre-curated service like a one-click stack.
  </Step>

  <Step>
    Verify logs, health, and connection info after the first deploy.
  </Step>
</Steps>

## Pick the right surface

* Project: an application from a GitHub repo or a Docker image — the default for most apps.
* Stack: a multi-container or service workload you already describe with Compose.
* Template: a curated, versioned blueprint when you want a service deployed for you.

## Or let the deploy agent do it

You can also describe the deployment in plain language to the deploy AI agent — it resolves the repo, infers the runtime and branch, and hands you a confirmable action card. See the AI agents guide.

## After it deploys

* Check the build and runtime logs.
* Confirm the workload reports healthy.
* Grab the domain or connection info to reach it.

## Expected result

<Check>
  You complete a first deployment and know which surface to use next time.
</Check>

## Related guides

<CardGroup cols={2}>
  <Card title="Deploy a Docker image" href="/projects/deploy-a-docker-image">
    Run a raw container image through the project flow when you already have an image and need runtime configuration, resource sizing, storage, domains, and placement.
  </Card>

  <Card title="Deploy a Compose stack" href="/stacks/deploy-a-compose-stack">
    Bring a Compose-defined workload to StackShift with domains, placement, and persistent volumes.
  </Card>

  <Card title="Deploy from a template" href="/templates/deploy-from-a-template">
    Launch a curated service by supplying template inputs, choosing placement, and reviewing the rendered summary.
  </Card>

  <Card title="StackShift AI agents" href="/ai-features/ai-agents">
    StackShift runs specialized agents that can create projects, fix failed builds, manage databases, triage incidents, and operate WordPress — each one proposing a confirmable action before anything changes.
  </Card>
</CardGroup>