Skip to main content
Live. This area is documented as current, user-reliable behavior.

​
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

1
Use a project if you have an app or Docker image.
2
Use a stack if you already have a Compose workload.
3
Use a template if you want a pre-curated service like a one-click stack.
4
Verify logs, health, and connection info after the first deploy.

​
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

You complete a first deployment and know which surface to use next time.

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.

Deploy a Compose stack

Bring a Compose-defined workload to StackShift with domains, placement, and persistent volumes.

Deploy from a template

Launch a curated service by supplying template inputs, choosing placement, and reviewing the rendered summary.

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