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

​
Goal

Understand the platform model before you start reading deployment or operations guides.

​
Prerequisites

  • None

​
Workflow

1
Use projects for individual applications and workers.
2
Use applications when projects and databases need explicit private relationships.
3
Use stacks for Compose-defined services and templates for StackShift-maintained blueprints.
4
Use managed databases, compute, assets, mail, and mobile services when the workload needs them.
5
Use Operations and Stackie for health, diagnosis, recovery, and governed actions.

​
How to think about the product

StackShift gives developers and operators one control plane for deploying software, running managed data services, operating compute, distributing assets and mobile releases, sending application mail, and investigating production systems. Runtime capacity can come from StackShift-managed infrastructure, StackShift Compute instances, connected nodes, or supported bring-your-own-cloud connections. The control plane owns identity, desired state, orchestration, audit records, billing, and the customer API.

​
Primary product surfaces

  • Projects: application-style deployments from GitHub or Docker images.
  • Applications: private service graphs that connect projects and databases through explicit bindings.
  • Stacks: multi-container and service-style workloads defined with Compose.
  • Templates: curated, versioned blueprints that deploy as stacks.
  • Databases and Compute: managed data services and virtual machines with day-two controls.
  • Nodes and BYO Cloud: connected or provisioned runtime capacity.
  • Operations: health, alerts, incidents, recovery, and controlled terminal access.

​
Additional product areas

Assets, domains, hosted email, transactional Mail, mobile delivery, Agency Cloud, billing, teams, and Stackie are first-class product areas in the current platform.

​
Expected result

You can choose the right StackShift surface for an application, service graph, managed service, infrastructure resource, or operational task.

Core concepts

A glossary for projects, applications, stacks, templates, nodes, compute, managed databases, durable operations, and approvals.

How StackShift works

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

Current platform status and terminology

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