Docs for the actual StackShift platform.

A precise description of StackShift as it exists today: a self-hosted application platform control plane for deploying and operating workloads across connected nodes.

A glossary and mental model for projects, stacks, templates, nodes, databases, deployments, and operations.

A product-level walkthrough of how the control plane, worker, agent, and runtime hosts cooperate.

A maturity guide for reading the platform docs without collapsing every user-visible surface into the same confidence level.

Create an account, verify access, and understand the first-run requirements before deploying anything.

Link GitHub so project-style deployments can pull repositories and deployment metadata cleanly.

Bootstrap a Linux host into StackShift and verify it is healthy enough to host workloads.

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

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.

Use the repository-backed project flow when you want StackShift to detect the app, build from source, and let you override runtime behavior before the first deploy.

Understand the project execution lifecycle: build output, deploy state, rollback behavior, and where to inspect logs.

Configure the project surfaces that most often decide whether a deployment works after it builds, including runtime shape, domains, previews, and storage.

Stacks are the service-oriented workload model in StackShift, built around Compose, named volumes, and node-aware placement.

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

Use the stack detail, logs, and placement information to understand how the stack is actually running.

Use S3-backed named-volume archives to protect and recover stateful stack data.

Templates are versioned service blueprints that render into stacks with saved inputs and provenance.

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

Launch single-site WordPress as a template-backed stack with bundled MariaDB and persistent storage.

Use the WordPress + Elementor template when you want visual editing and builder-friendly PHP defaults available immediately after launch.

What a node is, what the agent does, and what node health means in StackShift.

Use customer-owned cloud accounts as StackShift node hosts without turning the product into a generic cloud console.

Save provider credentials, choose a tested region and StackShift tier, and wait for the provisioned cloud node to become healthy and schedulable.

Manage provider-backed node resources such as volumes, snapshots, placement metadata, and stable public IP actions from the node-scoped cloud resources surface.

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

Provision a managed database and understand the minimum runtime and recovery expectations around it.

Understand how to consume database connection details and what to assume about pooling and access patterns.

Use the current S3-backed database backup and restore model with the correct operational expectations.

The operations area is the cross-resource health and runtime visibility surface for StackShift.

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

Use alerts to focus on active operational problems instead of scanning every resource manually.

Use the node-focused operations surface when you need to think about capacity, health, and runtime readiness across hosts.

Find and acquire domains, then understand how they appear in the domain portfolio.

Manage DNS records and connect domains to projects or other runtime surfaces.

Use the broader domain-management surfaces for transfers, email hosting, orders, and settings from the main domains product area.

The teams area lets you create teams, view team membership, and manage team-level collaboration flows.

Accepting and managing invitations is a user-visible part of the collaboration model.

Understand owner, admin, and member style collaboration capabilities in the current team model.

Use the billing area to inspect plans, subscription state, usage, transactions, payment methods, and spending limits.

A guide to what the billing dashboard currently exposes and how to read its plan, subscription, and spending-limit surfaces.

The AI diagnosis surface helps investigate issues, but should be treated as assistance rather than a guaranteed automated operator.

A maturity note for the AI product area.

Use account-level settings for user profile and basic account administration.

Manage password changes, active sessions, GitHub app installs, and other connected-account behavior from the settings area.

Understand the global env surface and how it differs from project- or stack-specific runtime configuration.

Use the notifications surfaces to stay aware of platform activity and alerts.