Skip to main content

From the Dashboard

  1. Navigate to the Dashboard and click Create Pod
  2. Fill in the creation form:
    • Name: A unique name for your pod. Must be lowercase alphanumeric with hyphens (e.g., my-app, staging-api). This becomes your subdomain.
    • Preset: Choose your development stack - Static, PHP, Node.js, Python, or Go
    • Version (optional): For PHP, Node.js, Python, and Go, pick a runtime version (e.g., Node.js 22, PHP 8.4). Defaults to the latest stable.
    • Plan: Select a resource tier - Launch, Build, Grow, Scale, or Turbo. Every preset starts on Launch ($3/mo) unless you change it
    • Region: Pick where the pod runs, or leave it on the suggested one
    • SSH Key (optional): Paste a public SSH key for immediate access
  3. Click Create
Your pod will be ready in 1-2 seconds. You’ll be redirected to the pod detail page.

Choosing a Region

Your pod runs in one region and stays there. Pick the one closest to the people who will use the app - it’s the difference between a fast page and a slow one, and for some workloads it’s also where your data has to live. Leave the region unset and InstaPods picks the closest one to you automatically. The picker shows live availability, not a static list: a region that can’t currently fit the plan you selected is shown as unavailable, so you never get a capacity error after filling in the form. Choosing a bigger plan can therefore change which regions are offered.
A pod can’t change region on its own. If you need one somewhere else, create it there and move your code across - or contact support, who can migrate an existing pod between servers.

From the CLI

Available Flags

The CLI returns immediately by default. Use -w to wait until the pod is fully running. If --preset is omitted, the CLI auto-detects from your current directory (e.g., package.json → Node.js, requirements.txt → Python).

Examples

From the API

What Happens During Creation

  1. Server selection — The orchestrator picks the best server in your chosen region (or the closest region if unspecified)
  2. Container launch — A container is created from the pre-built image for your preset
  3. Network setup — A unique SSH port is allocated and the proxy route is configured
  4. DNS — Your pod’s subdomain is immediately available via wildcard DNS

Pod Naming Rules

  • Lowercase letters, numbers, and hyphens only
  • Must start with a letter
  • 3-40 characters long
  • Must be unique within the platform
  • The name becomes your subdomain: {name}.{server-domain}