Skip to main content

List Pods

Displays a table with name, preset, plan, CPU, memory, disk, status, and domain.

Create a Pod

The pod name can also be passed as a flag:
By default, the CLI returns immediately after the API accepts the request. Use -w to wait until the pod is fully running before returning.

Create Flags

The --preset flag is optional. If omitted, the CLI auto-detects the preset from your current directory by looking for signature files like package.json (Node.js), composer.json (PHP), requirements.txt (Python), or index.html (Static).

Examples

Get Pod Details

Shows all pod information including status, IP, domain, resources, server, and creation time.

Start / Stop / Restart

restart stops and starts the whole container, so everything inside comes back up: your app, nginx, and any database service you installed. It does not install dependencies and does not build anything
  • it runs whatever is already on disk. That makes it the command for picking up a file you uploaded or edited on the pod, or clearing a stuck process.
While a Git deploy is building, restart and resize are refused - wait for the deploy to finish. stop always works, and cancels the running deploy; start the pod and deploy again afterwards.

Lifecycle Flags

Resize

Change a pod’s plan (and its associated resources):
The --plan flag is required. Resources (CPU, memory, disk) are automatically set based on the target plan.
Downgrades check disk usage — if the pod’s current disk usage exceeds the new plan’s storage limit, the resize will fail.

Switch Node Version

Move a Node.js pod to another Node major in place (22 or 24), keeping its files, environment variables, domain and plan:
Without --wait the command returns as soon as the switch starts; with it, the CLI waits and prints the result. If the app doesn’t start on a new major, the pod is switched back to the old one. See Switching Version Later for what the switch does.
pods node-version needs a CLI release newer than v1.16.0. Until then, use the Node version picker on the pod’s page in the dashboard.

Reload Application

Restart the application services inside the pod, without restarting the pod itself:
What gets restarted depends on the preset:
  • Static: nginx
  • PHP: nginx + PHP-FPM
  • Node.js, Python, Go: app systemd service
Reload also installs dependencies and runs the build. A package.json, requirements.txt, composer.json or go.mod in the app directory triggers npm install, pip install, composer install or go mod download before the restart, and the nodejs and go presets are rebuilt. If the pod is stopped, reload starts it first. This is the same step instapods deploy runs after uploading your files, so after a deploy you do not need to reload as well.
reload restarts your app; restart restarts the whole pod. If you are not sure which one you want, see Deploy, Reload, Restart.

Delete

After you confirm an interactive delete, the CLI asks one optional question about why. Press Enter to skip it. It is skipped entirely under -f, --json, or a non-interactive stdin, so it never blocks a script.
Deletion is permanent. All files, databases, and configurations are destroyed. Deleted pod names are reserved for 7 days to prevent SSH host key conflicts.

JSON Output

Add --json to any command for machine-readable JSON output: