Skip to main content

​
Pod Lifecycle

Pods have the following statuses:

​
Start / Stop / Restart

On the pod detail page, use the action buttons in the header to Start, Stop, or Restart your pod.
Stopping a pod preserves all files but terminates running processes. Any in-memory data not written to disk will be lost.

​
Resize

Change the CPU, memory, or disk allocation of a running pod.
The --plan flag is required. Resources (CPU, memory, disk) are automatically set based on the target plan.

​
Delete

Deleting a pod permanently removes the container and all its data.
Go to the pod detail page, click the delete button, and confirm.
Deletion is irreversible. All files, databases, and configurations inside the pod will be permanently destroyed. Deleted pod names are reserved for 7 days before they can be reused.
Once the pod is gone you can no longer reach its backups from the dashboard or the API. If you might want the data later, download a backup first - and if you’re handing the project to someone else, transfer the pod instead of deleting and recreating it.

​
Back Up and Restore

Every pod is backed up daily by default, and you can take a backup by hand at any time. See Backups.

​
Convert to a Worker

A pod that runs a bot, a queue consumer or a scheduled job doesn’t need a public URL. Converting it to a worker removes its URL and stops the platform health-checking an address nothing is listening on. See Worker Pods.

​
Transfer to Another Account

You can hand a pod, its data and its billing to a different InstaPods account. See Transfer a Pod.

​
List Pods

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

​
Get Pod Details

​
Reload Application

Restart the application service inside the pod without restarting the container itself. Useful after deploying new code.
This restarts different services depending on the preset:
  • Static: Reloads nginx
  • PHP: Restarts nginx and PHP-FPM
  • Node.js: Restarts the app systemd service
  • Python: Restarts the app systemd service
Reload also auto-detects and installs dependencies: if a package.json (Node.js) or requirements.txt (Python) is present, npm install or pip install runs before restarting the service.