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

​
Goal

Pick a region and an app size that your plan allows before you create an app, so it lands where you expect with the resources it needs.

​
Prerequisites

  • A StackShift account
  • The CLI or an API client if you are automating

​
Workflow

1
List regions with stackshift project regions. Regions where apps are available show apps.available: true.
2
List app sizes with stackshift project sizes. Pick a size whose plans include your plan.
3
Create the app with that region and resource_preset. Leave region empty or set it to auto to let StackShift choose.
4
Check the app page: it shows the region and size you chose.

​
Regions

A region is listed only when at least one product can run there right now. Each region shows which products it offers: apps (with the tier, shared for Free and Ignite apps and isolated for Pro and Enterprise apps), databases and servers. status: "degraded" means some machines in that region are not ready; new apps may wait longer to start. The region is fixed when you create an app. Moving an existing app to another region is not supported yet: create a new app in the target region and move your traffic and data.
GET /api/v1/regions (no sign-in needed)

​
App sizes

Each size sets the CPU and memory for every copy of your app. memory_mb and cpu_millicores show the resources; min_plan and plans show which plans can use it. Sizes with listed: false still work for apps that already use them but are hidden from the size picker. included_in_plan: true means the size costs nothing extra on top of your plan. See https://stackshift.cloud/pricing for plan prices. Changing a size in the catalog never resizes your running apps; it applies when you next choose a size.
  • Set the size with resource_preset when you create or update an app. An unknown slug is refused with the list of valid ones.
  • Your plan still caps memory and CPU per app. max_cpu_millicores: -1 means no CPU cap.
  • To see your plan’s default size, read default_resource_preset from GET /api/v1/billing/subscription.

​
Terraform

The Terraform provider has a stackshift_regions data source (filter with product = "apps", "databases" or "vps") and a stackshift_app_sizes data source (listed_only = true keeps the picker sizes). A project’s region is optional; when you leave it out, StackShift chooses and records it.

​
Expected result

Your app runs in the region you chose, with the CPU and memory of the selected size.

​
Common failures

  • region "x" isn't available for apps on this plan: pick a region from stackshift project regions where apps are available for your plan’s tier, or leave the region empty.
  • Changing the region of an existing app is refused: create a new app in the other region instead.
  • A size is refused for your plan: choose a size whose plans include your plan, or upgrade the plan.

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.