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

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.

Reload Application

Restart the application services inside the pod:
What gets restarted depends on the preset:
  • Static: nginx
  • PHP: nginx + PHP-FPM
  • Node.js: app systemd service
  • Python: 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 automatically before restarting the service.

Delete

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: