# StackShift

## Docs

- [StackShift AI agents](https://docs.stackshift.cloud/ai-features/ai-agents.md): 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.
- [AI build diagnosis](https://docs.stackshift.cloud/ai-features/ai-diagnosis.md): Automatic root-cause analysis for failed builds: a known-pattern matcher backed by Claude LLM analysis produces a categorized diagnosis with confidence and concrete fix steps.
- [Current status and limitations](https://docs.stackshift.cloud/ai-features/current-status-and-limitations.md): Exactly what the AI agents and diagnosis can and cannot do today, and the guardrails that constrain them.
- [AI DAM and versioning](https://docs.stackshift.cloud/assets/ai-dam-and-versioning.md): Use OpenAI-backed asset intelligence, moderation, transcripts, smart crops, background removal, collections, saved searches, and branching versions.
- [Direct browser uploads](https://docs.stackshift.cloud/assets/direct-browser-uploads.md): Create a short-lived signed upload URL on your server, then PUT the file directly from the browser.
- [Image optimization](https://docs.stackshift.cloud/assets/image-optimization.md): Use named presets and signed dynamic transforms for strict, cached, responsive image delivery.
- [StackShift Assets overview](https://docs.stackshift.cloud/assets/overview.md): StackShift Assets is now a live media platform: storage, CDN delivery, image optimization, upload sessions, DAM, video, scanning, governance, AI metadata, and version history.
- [Private assets and signed URLs](https://docs.stackshift.cloud/assets/private-assets-and-signed-urls.md): Keep files private by default and generate short-lived URLs only when a user should download them.
- [Assets SDK quick start](https://docs.stackshift.cloud/assets/sdk-quick-start.md): Install a StackShift SDK and upload files from Node/TypeScript, NestJS, Python, or Go.
- [Upload UX and DAM](https://docs.stackshift.cloud/assets/upload-ux-and-dam.md): Use resumable upload sessions, progress-aware browser uploads, tags, folders, search, bulk actions, and usage summaries.
- [Video, scanning, and governance](https://docs.stackshift.cloud/assets/video-scanning-and-governance.md): Process video asynchronously, deliver HLS and posters, scan uploads, quarantine infected assets, and enforce account policies.
- [Billing dashboard behavior](https://docs.stackshift.cloud/billing/current-billing-status.md): A guide to what the billing dashboard currently exposes and how to read its plan, subscription, and spending-limit surfaces.
- [Plans and usage](https://docs.stackshift.cloud/billing/plans-and-usage.md): Use the billing area to inspect plans, subscription state, usage, transactions, payment methods, and spending limits.
- [Back up and restore a database](https://docs.stackshift.cloud/databases/back-up-and-restore-a-database.md): Use the current S3-backed database backup and restore model with the correct operational expectations.
- [Create a database](https://docs.stackshift.cloud/databases/create-a-database.md): Provision a managed database and understand the minimum runtime and recovery expectations around it.
- [Credentials, pooling, and usage expectations](https://docs.stackshift.cloud/databases/credentials-pooling-and-usage.md): Understand how to consume database connection details and what to assume about pooling and access patterns.
- [Database troubleshooting](https://docs.stackshift.cloud/databases/database-troubleshooting.md): Common issues around provisioning, connectivity, backup configuration, and restore progress.
- [Managed database overview](https://docs.stackshift.cloud/databases/managed-database-overview.md): How StackShift databases fit into the platform and how they differ from stack-hosted stateful services.
- [DNS records and project connection](https://docs.stackshift.cloud/domains-and-email/dns-records-and-project-connection.md): Manage DNS records and connect domains to projects or other runtime surfaces.
- [Domain search, purchase, and portfolio](https://docs.stackshift.cloud/domains-and-email/search-purchase-and-portfolio.md): Find and acquire domains, then understand how they appear in the domain portfolio.
- [Transfers, email hosting, orders, and settings](https://docs.stackshift.cloud/domains-and-email/transfers-email-and-settings.md): Use the broader domain-management surfaces for transfers, email hosting, orders, and settings from the main domains product area.
- [Best Practices](https://docs.stackshift.cloud/durable-jobs/best-practices.md): Short rules for writing Durable Jobs that behave well in production.
- [Core Concepts](https://docs.stackshift.cloud/durable-jobs/core-concepts.md): The vocabulary behind Durable Jobs: jobs, steps, runs, queues, state, events, and idempotency.
- [Event Waiting + Correlation](https://docs.stackshift.cloud/durable-jobs/event-waiting-and-correlation.md): Pause a workflow until the right external event arrives, then resume the correct run.
- [Idempotency](https://docs.stackshift.cloud/durable-jobs/idempotency.md): Use idempotency keys so duplicate requests do not create duplicate work.
- [Observability](https://docs.stackshift.cloud/durable-jobs/observability.md): Inspect each job run through status, attempts, logs, payload, result, errors, and timeline.
- [Durable Jobs overview](https://docs.stackshift.cloud/durable-jobs/overview.md): Durable Jobs is the reliable execution engine for backend work on StackShift. Deploy the app. Offload the work.
- [Quick Start](https://docs.stackshift.cloud/durable-jobs/quick-start.md): Install the SDK, initialize a client, enqueue a job, add a worker handler, and inspect the run.
- [Real-World Examples](https://docs.stackshift.cloud/durable-jobs/real-world-examples.md): Common backend flows that fit Durable Jobs: verification email, payment provisioning, and file processing.
- [Retries & Failure Handling](https://docs.stackshift.cloud/durable-jobs/retries-and-failure-handling.md): Durable Jobs retries transient failures, preserves completed steps, and gives failed work a clear recovery path.
- [Scheduling & Delayed Jobs](https://docs.stackshift.cloud/durable-jobs/scheduling-and-delayed-jobs.md): Run jobs later for reminders, follow-ups, retry windows, cleanup, and recurring backend work.
- [State Store](https://docs.stackshift.cloud/durable-jobs/state-store.md): Use durable state for progress, deduplication, counters, TTL-backed markers, and locks.
- [Using Queues](https://docs.stackshift.cloud/durable-jobs/using-queues.md): Use queues for background execution, retry policy, delayed jobs, and concurrency control.
- [Durable Jobs workflows](https://docs.stackshift.cloud/durable-jobs/workflows.md): Use steps and events to build multi-step jobs that can retry, pause, and resume.
- [Connect GitHub](https://docs.stackshift.cloud/getting-started/connect-github.md): Link GitHub so project-style deployments can pull repositories and deployment metadata cleanly.
- [Connect your first node](https://docs.stackshift.cloud/getting-started/connect-your-first-node.md): Bootstrap a Linux host into StackShift and verify it is healthy enough to host workloads.
- [Create your account](https://docs.stackshift.cloud/getting-started/create-your-account.md): Create an account, verify access, and understand the first-run requirements before deploying anything.
- [Deploy your first workload](https://docs.stackshift.cloud/getting-started/deploy-your-first-workload.md): Choose the right first deployment path based on whether you are deploying an app, a Compose service, or a curated template.
- [StackShift Documentation](https://docs.stackshift.cloud/index.md): The control plane, connected-node model, deployment surfaces, recovery behavior, and product areas — documented as the platform actually works today.
- [Provider resources and imports](https://docs.stackshift.cloud/infrastructure-as-code/resources-and-imports.md): Implementation reference for StackShift provider resources, import IDs, action semantics, and caveats.
- [Terraform and OpenTofu provider](https://docs.stackshift.cloud/infrastructure-as-code/terraform-provider.md): Use the StackShift provider implementation to declare StackShift resources and run explicit StackShift actions from Terraform or OpenTofu.
- [Core concepts](https://docs.stackshift.cloud/introduction/core-concepts.md): A glossary and mental model for projects, stacks, templates, nodes, databases, deployments, and operations.
- [Current platform status and terminology](https://docs.stackshift.cloud/introduction/current-platform-status.md): A maturity guide for reading the platform docs without collapsing every user-visible surface into the same confidence level.
- [How StackShift works](https://docs.stackshift.cloud/introduction/how-stackshift-works.md): A product-level walkthrough of how the control plane, worker, agent, and runtime hosts cooperate.
- [What is StackShift](https://docs.stackshift.cloud/introduction/what-is-stackshift.md): A precise description of StackShift as it exists today: a self-hosted application platform control plane for deploying and operating workloads across connected nodes.
- [BYOCloud overview](https://docs.stackshift.cloud/nodes/byocloud-overview.md): Connect customer-owned cloud accounts to StackShift, provision cloud-backed nodes, and operate them through the same node workflows used elsewhere in the product.
- [BYOCloud cloud resources](https://docs.stackshift.cloud/nodes/byocloud-resource-add-ons.md): Manage provider-backed node resources such as volumes, snapshots, placement metadata, stable public IPs, refresh, retry, reboot, and delete actions from the node detail surface.
- [Connect a BYOCloud node](https://docs.stackshift.cloud/nodes/connect-a-byocloud-node.md): Save provider credentials, choose a tested region and StackShift tier, and wait for the provisioned cloud node to become healthy and schedulable.
- [Install the agent](https://docs.stackshift.cloud/nodes/install-the-agent.md): Bootstrap a new node and understand what the install command is doing on the target host.
- [Maintenance mode](https://docs.stackshift.cloud/nodes/maintenance-mode.md): Use maintenance as a safety control before upgrades or disruptive host changes.
- [Node health, diagnostics, and deletion](https://docs.stackshift.cloud/nodes/node-health-diagnostics-and-deletion.md): Read node diagnostics correctly and understand when deletion is safe or blocked.
- [Node overview](https://docs.stackshift.cloud/nodes/node-overview.md): What a node is, what the agent does, and what node health means in StackShift.
- [Upgrade the agent](https://docs.stackshift.cloud/nodes/upgrade-agent.md): Use the maintenance-first path to move an existing node to a newer agent version.
- [Alerts view](https://docs.stackshift.cloud/operations/alerts-view.md): Use alerts to focus on active operational problems instead of scanning every resource manually.
- [Nodes view](https://docs.stackshift.cloud/operations/nodes-view.md): Use the node-focused operations surface when you need to think about capacity, health, and runtime readiness across hosts.
- [Operations overview](https://docs.stackshift.cloud/operations/operations-overview.md): The operations area is the cross-resource health and runtime visibility surface for StackShift.
- [Recovery states, logs, and troubleshooting](https://docs.stackshift.cloud/operations/recovery-logs-and-troubleshooting.md): 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.
- [Services view](https://docs.stackshift.cloud/operations/services-view.md): Track stack-backed services and databases in one place with health, backup posture, and upgrade cues.
- [Builds, deployments, and logs](https://docs.stackshift.cloud/projects/builds-deployments-and-logs.md): Understand the project execution lifecycle: build output, deploy state, rollback behavior, and where to inspect logs.
- [Configure email providers](https://docs.stackshift.cloud/projects/configure-email-providers.md): Use your own SMTP server or provider account for outbound email on projects and stacks, including BYOS connected-node workloads.
- [Deploy a Docker image](https://docs.stackshift.cloud/projects/deploy-a-docker-image.md): 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 from GitHub](https://docs.stackshift.cloud/projects/deploy-from-github.md): 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.
- [Project environment, domains, and previews](https://docs.stackshift.cloud/projects/environment-domains-and-previews.md): Configure the project surfaces that most often decide whether a deployment works after it builds, including runtime shape, domains, previews, and storage.
- [Project troubleshooting](https://docs.stackshift.cloud/projects/project-troubleshooting.md): Common project-side failure modes, especially when the app built successfully but does not come up healthy.
- [Scheduled jobs (cron)](https://docs.stackshift.cloud/projects/scheduled-jobs.md): Run a command from your deployed image on a recurring standard-cron schedule, with run history and exit-code tracking.
- [StackShift Functions](https://docs.stackshift.cloud/projects/stackshift-functions.md): Deploy Node.js serverless-style functions from an `api/` directory with HTTP handlers, async invokes, queue triggers, schedules, retries, replayable runs, and instant HTTPS routing.
- [Worker and background processes](https://docs.stackshift.cloud/projects/worker-processes.md): Run a project as a background process type (worker, queue, scheduler, reverb) instead of a public web service.
- [Global environment variables](https://docs.stackshift.cloud/settings/global-environment-variables.md): Understand the global env surface and how it differs from project- or stack-specific runtime configuration.
- [Notifications](https://docs.stackshift.cloud/settings/notifications.md): Use the notifications surfaces to stay aware of platform activity and alerts.
- [Profile and account settings](https://docs.stackshift.cloud/settings/profile-and-account-settings.md): Use account-level settings for user profile and basic account administration.
- [Security and connections](https://docs.stackshift.cloud/settings/security-and-connections.md): Manage password changes, active sessions, GitHub app installs, and other connected-account behavior from the settings area.
- [Back up and restore a stack](https://docs.stackshift.cloud/stacks/back-up-and-restore-a-stack.md): Use S3-backed named-volume archives to protect and recover stateful stack data.
- [Deploy a Compose stack](https://docs.stackshift.cloud/stacks/deploy-a-compose-stack.md): Bring a Compose-defined workload to StackShift with domains, placement, and persistent volumes.
- [Stack logs, health, and placement](https://docs.stackshift.cloud/stacks/logs-health-and-placement.md): Use the stack detail, logs, and placement information to understand how the stack is actually running.
- [Reassign and migration expectations](https://docs.stackshift.cloud/stacks/reassign-and-migration-expectations.md): Understand what stack reassignment and migration mean today, especially for stateful stacks.
- [Stack troubleshooting](https://docs.stackshift.cloud/stacks/stack-troubleshooting.md): Common stack-side failures around placement, logs, health, template drift, and restore behavior.
- [What stacks are](https://docs.stackshift.cloud/stacks/what-stacks-are.md): Stacks are the service-oriented workload model in StackShift, built around Compose, named volumes, and node-aware placement.
- [Bounces, suppressions, and reputation](https://docs.stackshift.cloud/stackshift-mail/bounces-suppressions-and-reputation.md): Handle hard and soft bounces, workspace-scoped suppressions, sending limits, warmup stage, domain reputation, and reputation events.
- [Events, webhooks, and timelines](https://docs.stackshift.cloud/stackshift-mail/events-webhooks-and-timelines.md): List mail events, inspect per-message timelines, subscribe webhooks, rotate secrets, retry deliveries, and verify webhook signatures.
- [StackShift Mail overview](https://docs.stackshift.cloud/stackshift-mail/overview.md): A verified map of the current StackShift Mail surface: outbound send, sender domains, bounces, suppressions, templates, OTP, events, webhooks, reputation, scheduled mail, batch mail, inbound mail, attachments, and analytics.
- [Scheduled, batch, inbound, attachments, and analytics](https://docs.stackshift.cloud/stackshift-mail/scheduled-batch-inbound-and-analytics.md): Use the Mail APIs for scheduled delivery, batch sending, batch-template sending, inbound domain capture, asset-backed attachments, and aggregate analytics.
- [Send email](https://docs.stackshift.cloud/stackshift-mail/send-email.md): Send a single outbound email with the official SDK or REST API, then inspect the message, attempts, logs, and timeline.
- [Sender domains and DNS](https://docs.stackshift.cloud/stackshift-mail/sender-domains-and-dns.md): Create and verify outbound sender domains, inspect SPF, DKIM, DMARC, and return-path record status, and know what the domain status fields mean.
- [Templates and OTP](https://docs.stackshift.cloud/stackshift-mail/templates-and-otp.md): Create versioned templates, preview and test them, send from a template, and use the built-in one-time-code challenge flow.
- [Invitations](https://docs.stackshift.cloud/team-and-access/invitations.md): Accepting and managing invitations is a user-visible part of the collaboration model.
- [Roles and collaboration expectations](https://docs.stackshift.cloud/team-and-access/roles-and-collaboration.md): Understand owner, admin, and member style collaboration capabilities in the current team model.
- [Teams overview](https://docs.stackshift.cloud/team-and-access/teams-overview.md): The teams area lets you create teams, view team membership, and manage team-level collaboration flows.
- [Deploy from a template](https://docs.stackshift.cloud/templates/deploy-from-a-template.md): Launch a curated service by supplying template inputs, choosing placement, and reviewing the rendered summary.
- [Template inputs and secrets](https://docs.stackshift.cloud/templates/template-inputs-and-secrets.md): Understand which template values are required, which are sensitive, and how they affect rendering and upgrades.
- [Template upgrade safety and service notes](https://docs.stackshift.cloud/templates/template-upgrade-safety.md): Understand why an upgrade is safe, risky, or blocked, and how template readiness notes should influence operator decisions.
- [Updating template-backed stacks](https://docs.stackshift.cloud/templates/updating-template-backed-stacks.md): Preview diffs, resolve missing inputs, and apply the latest published template version safely.
- [What templates are](https://docs.stackshift.cloud/templates/what-templates-are.md): Templates are versioned service blueprints that render into stacks with saved inputs and provenance.
- [Access and permissions](https://docs.stackshift.cloud/terminal/access-and-permissions.md): How terminal permissions are derived from team role, project ownership, per-user grants, and platform admin, and what each permission unlocks.
- [Terminal workspace overview](https://docs.stackshift.cloud/terminal/overview.md): The per-project operations workspace where you open application and database shells, run runbooks and commands, and review session history and recordings.
- [Terminal policy and file transfer](https://docs.stackshift.cloud/terminal/policy-and-file-transfer.md): The policy controls owners/admins use to govern terminal behavior, plus browsing and transferring files within a session.
- [Production safeguards and approvals](https://docs.stackshift.cloud/terminal/production-safeguards.md): How a target’s environment is classified, why production access is gated, and the reason/approval flow members must follow.
- [Session recordings and history](https://docs.stackshift.cloud/terminal/recordings-and-history.md): Review, play back, and download terminal session recordings, and audit session history — including how retention and purging work.
- [Runbooks and one-off commands](https://docs.stackshift.cloud/terminal/runbooks-and-commands.md): Run versioned platform and project runbooks, and execute ad-hoc one-off commands, within the project terminal policy.
- [Back up and restore a WordPress stack](https://docs.stackshift.cloud/wordpress/back-up-and-restore-a-wordpress-stack.md): Use StackShift stack backups for WordPress content and bundled MariaDB data, then validate the app after restore.
- [Connect a custom domain to WordPress](https://docs.stackshift.cloud/wordpress/connect-a-custom-domain-to-wordpress.md): Understand how StackShift routing and WordPress site URLs interact before and after first boot.
- [Deploy WordPress for agencies](https://docs.stackshift.cloud/wordpress/deploy-wordpress-for-agencies.md): Use the WordPress + Elementor template when you want visual editing and builder-friendly PHP defaults available immediately after launch.
- [Deploy WordPress on StackShift](https://docs.stackshift.cloud/wordpress/deploy-wordpress-on-stackshift.md): Launch single-site WordPress as a template-backed stack with bundled MariaDB and persistent storage.
- [WordPress Control Surface](https://docs.stackshift.cloud/wordpress/wordpress-control-surface.md): A first-class operational surface for direct WordPress projects: overview, narrow safe actions, diagnostics, and recent history.
- [WordPress plugin and theme releases](https://docs.stackshift.cloud/wordpress/wordpress-plugin-theme-releases.md): Connect a WordPress plugin or theme repo, let StackShift package it into a release, preview it, promote draft/beta/stable channels, and install the exact release on a running StackShift WordPress site.