Command reference

Every panda command, grouped. Most list/info commands accept --json for raw output; destructive delete commands accept -y/--yes to skip the confirmation prompt. See Install & auth for setup.

At a glance

Command	Description	Example
`panda login`	Paste `psk_` token, verify via `/v1/whoami`, save org	`panda login`
`panda logout`	Clear stored credentials (keeps `api_url`)	`panda logout`
`panda org list`	Show the org the token belongs to (`--json`)	`panda org list`
`panda org use [name]`	Explains tokens are per-org; log in with that org’s token	`panda org use`
`panda status`	Org + plan + resource-count overview (`--json`)	`panda status`
`panda monitor`	Health overview for projects/functions/cronjobs (`--json`)	`panda monitor`
`panda projects list`	List projects (`--page`, `--limit`, `--json`)	`panda projects list`
`panda projects info <id>`	Project details by name (`--json`)	`panda projects info my-app`
`panda projects deploy <id>`	Deploy + stream build logs (`--no-stream`)	`panda projects deploy my-app`
`panda projects logs <id>`	Stream latest deployment logs (`--type`)	`panda projects logs my-app --type application`
`panda projects env list <id>`	List project env vars (`--json`)	`panda projects env list my-app`
`panda projects env set <id> KEY=VALUE`	Upsert an env var	`panda projects env set my-app API_KEY=abc`
`panda projects env unset <id> KEY`	Remove an env var	`panda projects env unset my-app API_KEY`
`panda projects delete <id>`	Delete a project (`-y`)	`panda projects delete my-app -y`
`panda projects upload [dir]`	Build+zip+deploy a local folder	`panda projects upload ./ --build-dir dist`
`panda projects create`	Interactive project wizard	`panda projects create`
`panda functions list`	List edge functions (`--json`)	`panda functions list`
`panda functions info <id>`	Function details + endpoint (`--json`)	`panda functions info weather`
`panda functions deploy <name> <source>`	Zip+upload; create or new version	`panda functions deploy weather ./my-fn/`
`panda functions invoke <id>`	Invoke (`-d/--data`, `--json`)	`panda functions invoke weather -d '{"city":"London"}'`
`panda functions logs <id>`	Recent invocation logs (`-n/--limit`)	`panda functions logs weather -n 20`
`panda functions delete <id>`	Delete function (`-y`)	`panda functions delete weather -y`
`panda cronjobs list`	List cronjobs (`--json`)	`panda cronjobs list`
`panda cronjobs info <id>`	Cronjob details (`--json`)	`panda cronjobs info nightly`
`panda cronjobs create`	Interactive GitHub-based create wizard	`panda cronjobs create`
`panda cronjobs trigger <id>`	Manual run (`--stream`)	`panda cronjobs trigger nightly --stream`
`panda cronjobs logs <id>`	Execution logs (`--stream`, `-n/--limit`)	`panda cronjobs logs nightly --stream`
`panda cronjobs delete <id>`	Delete cronjob (`-y`)	`panda cronjobs delete nightly -y`
`panda db list`	List databases (`--json`)	`panda db list`
`panda db info <id>`	DB details + connection strings + password	`panda db info my-pg`
`panda db create`	Interactive provision wizard	`panda db create`
`panda db delete <id>`	Delete database, all data lost (`-y`)	`panda db delete my-pg -y`
`panda ask [query...]`	AI assistant (currently a stub)	`panda ask "why did my deploy fail?"`
`panda "<query>"`	Shorthand: bare unknown arg routes to `ask`	`panda "show failing projects"`

Auth & account

`panda login` / `panda logout`

See Install & auth. login verifies a psk_ token via /v1/whoami and stores the resolved org; logout clears credentials but keeps api_url.

`panda org`

Subcommand	Behavior
`panda org list`	Shows the single org the token belongs to. Add `--json`.
`panda org use [name]`	Explains that tokens are per-org; to switch, log in with that org’s token. There is no in-CLI org switching.

`panda status`

Aggregates GET /v1/whoami, /v1/projects, /v1/functions, /v1/cronjobs, and /v1/databases (via Promise.allSettled) and prints org name/id/role/plan, resource counts (from each list’s .total), and any failed projects. Supports --json.

panda status
panda status --json

`panda monitor`

Aggregates /v1/projects, /v1/functions, and /v1/cronjobs and prints per-resource health tables, flagging any failed resources. Supports --json. There is no dedicated metrics endpoint behind this — it is a health overview.

panda monitor

Projects

Projects are resolved by name. list uses GET /v1/projects; info/deploy/logs/env/delete resolve via GET /v1/projects/:name.

`panda projects list`

Flag	Purpose
`--page`	Page number
`--limit`	Page size
`--json`	Raw output

panda projects list --page 1 --limit 10 --json

`panda projects info <id>`

Shows project details by name. --json for raw.

panda projects info my-app

`panda projects deploy <id>`

Calls POST /v1/projects/:name/deploy, then streams the build logs.

Flag	Purpose
`--no-stream`	Trigger the deploy without streaming logs

panda projects deploy my-app
panda projects deploy my-app --no-stream

`panda projects logs <id>`

Streams the latest deployment’s logs. The latest deployment is resolved from GET /v1/projects/:name/deployments.

Flag	Purpose	Default
`--type`	`build` or `application`	`build`

panda projects logs my-app --type application

`panda projects env`

Subcommand	Endpoint	Purpose
`panda projects env list <id>`	`GET /v1/projects/:name`	List env vars (`--json`)
`panda projects env set <id> KEY=VALUE`	`PATCH /v1/projects/:name`	Upsert an env var (rebuilds the env array)
`panda projects env unset <id> KEY`	`PATCH /v1/projects/:name`	Remove an env var

panda projects env list my-app
panda projects env set my-app API_KEY=abc
panda projects env unset my-app API_KEY

`panda projects delete <id>`

DELETE /v1/projects/:name. Add -y/--yes to skip the confirmation prompt.

panda projects delete my-app -y

`panda projects upload [dir]`

Builds, zips, and deploys a local folder via POST /v1/projects/static-upload — no GitHub connection needed. The upload uses raw multipart/form-data with the Bearer token. Uploaded static projects are served at https://<name>.pandastack.app.

Flag	Purpose
`-n`, `--name`	Project name
`--build-cmd`	Build command
`--build-dir`	Output directory to upload
`--skip-build`	Skip the build step

panda projects upload ./ --name my-site --build-cmd "npm run build" --build-dir dist

`panda projects create`

Interactive wizard. The chosen name gets a random 5-character suffix. Options:

static-upload — build+zip+deploy a local folder.
static — GitHub → build.
container — GitHub → Docker → Kubernetes.

GitHub-based paths call GET /v1/integrations/github/repositories and /v1/integrations/github/branches, then POST /v1/projects. Container languages: docker, nodejs, python, go.

panda projects create

Functions

Edge functions are resolved by id or name.

Command	Endpoint	Notes
`panda functions list`	`GET /v1/functions`	`--json`
`panda functions info <id>`	`GET /v1/functions/:id`	Shows runtime/timeout/version/endpoint + a curl example
`panda functions deploy <name> <source>`	`POST /v1/functions` (create) or `POST /v1/functions/:name/deploy` (new version)	Zips a file/dir. `-r`/`--runtime` (default `nodejs`), timeout default 30000
`panda functions invoke <id>`	`POST /v1/functions/:id/invoke`	`-d`/`--data` JSON body, `--json`
`panda functions logs <id>`	`GET /v1/functions/:id/invocations`	`-n`/`--limit`, `--json`
`panda functions delete <id>`	`DELETE /v1/functions/:id`	`-y`

panda functions deploy weather ./my-fn/ --runtime nodejs
panda functions invoke weather -d '{"city":"London"}'
panda functions logs weather -n 20
panda functions delete weather -y

Function-deploy uploads use raw multipart/form-data (not the shared API client).

Cronjobs

Cronjobs are resolved by name.

Command	Endpoint	Notes
`panda cronjobs list`	`GET /v1/cronjobs`	`--json`
`panda cronjobs info <id>`	`GET /v1/cronjobs/:name`	`--json`
`panda cronjobs create`	`POST /v1/cronjobs`	Interactive GitHub wizard
`panda cronjobs trigger <id>`	`POST /v1/cronjobs/:name/trigger`	`--stream` for live logs
`panda cronjobs logs <id>`	`GET /v1/cronjobs/:name/executions`	`--stream` live, `-n`/`--limit`, `--json`
`panda cronjobs delete <id>`	`DELETE /v1/cronjobs/:name`	`-y`

panda cronjobs create
panda cronjobs trigger nightly-sync --stream
panda cronjobs logs nightly-sync --stream
panda cronjobs delete nightly-sync -y

Databases

Databases are resolved by name.

Command	Endpoint	Notes
`panda db list`	`GET /v1/databases`	`--json`
`panda db info <id>`	`GET /v1/databases/:name` + `GET /v1/databases/:name/password`	Inlines the real password + connection URLs (`--json`)
`panda db create`	`POST /v1/databases`	Interactive provision wizard
`panda db delete <id>`	`DELETE /v1/databases/:name`	`-y` — all data lost

The create wizard collects: engine (POSTGRESQL | MYSQL | MONGODB | REDIS, with pinned versions), architecture (standalone | replicaset), instanceType (free-tier), region: us, backups enabled with backupsToKeep: 7, a name with a random 6-character suffix, and an auto-generated 16-character password if you leave it blank.

panda db info my-pg
panda db create
panda db delete my-pg -y

AI assistant (`panda ask`)

panda ask gathers your project, function, cronjob, and database context, but the assistant is currently a stub: it reports that the AI assistant is not available on this API yet and prints your current infra summary. No LLM call is made.

A bare, non-flag first argument that is not a known command is rewritten to ask as a shorthand:

panda ask "why did my last deploy fail?"
panda "show me failing projects"

Global conventions

Flag	Applies to	Purpose
`--json`	Most `list` / `info` / `status` / `monitor` commands	Raw JSON output
`-y`, `--yes`	Destructive `delete` commands	Skip the confirmation prompt

Install & auth — install, login, config, base URL.
Projects overview
Functions overview
Cronjobs overview
Databases overview

Command reference

At a glance

Auth & account

panda login / panda logout

panda org

panda status

panda monitor

Projects

panda projects list

panda projects info <id>

panda projects deploy <id>

panda projects logs <id>

panda projects env

panda projects delete <id>

panda projects upload [dir]

panda projects create