Deployments

Model deployments serve a fine-tuned or catalog model within a project, backed by allocated GPU instances. Use inf deployment to create a deployment, inspect its effective config and instances, and manage its lifecycle — all without opening the dashboard.

Alias: inf deployments

Quickstart

# See what a model may be deployed on (GPU families and counts)
inf deployment allowed-instance-types --model-id <model-id>

# Create a deployment and watch the rollout converge
inf deployment create \
  --name my-deployment \
  --model-id <model-id> \
  --public-model-identifier <team>/<model-slug>
inf deployment watch <deployment-id>

# Inspect the deployment and the engine config it serves with
inf deployment get <deployment-id>
inf deployment config <deployment-id>

# Stop serving (reversible) or archive to free a slot
inf deployment stop <deployment-id> --yes
inf deployment start <deployment-id>

Super-admin pricing rules

Super-admins can set scheduled effective prices for a public serverless deployment. Prices are entered in USD per 1M tokens and stored as fixed per-token rates. Omitting --customer-team creates an all-team rule; a matching team rule takes precedence over an all-team rule.

inf admin deployments pricing-rules list <deployment-id>

inf admin deployments pricing-rules create <deployment-id> \
  --customer-team <team-id> \
  --input 1.05 \
  --cached-input 0.115 \
  --output 5.475 \
  --starts-at 2026-09-20T00:00:00Z \
  --ends-at 2026-09-27T00:00:00Z \
  --reason "Partner launch pricing"

inf admin deployments pricing-rules remove <deployment-id> \
  --rule <rule-id> \
  --yes

--cached-input defaults to the input price. Higher --priority wins among otherwise matching rules; disabled, future, and expired rules do not apply. The deployment's standard prices remain the fallback.

`inf deployment list`

List deployments for a team with their status, lifecycle, and served model alias.

inf deployment list

Alias: inf deployment ls

Options

Flag	Required	Description	Default
`--team <id>`	No	Team ID	`INF_TEAM_ID` / active team
`--project <id>`	No	Filter results to a single project ID	—
`-l, --limit <n>`	No	Max results to return (positive integer)	`50`

Shows the deployment ID (8-char prefix), name, status, lifecycle state, public model identifier, and creation date.

`inf deployment get`

Show a single deployment's full details — status, lifecycle, model alias, and timestamps. Omit the id to pick interactively.

inf deployment get <id>

Arguments

Argument	Required	Description
`id`	No	Deployment ID; omit to pick interactively

Options

Flag	Required	Description
`--team <id>`	No	Team ID

`inf deployment config`

Show the effective engine configuration a deployment serves with: the resolved flags, environment variables, and which layer set each.

inf deployment config <id>

Arguments

Argument	Required	Description
`id`	No	Deployment ID; omit to pick interactively

Options

Flag	Required	Description
`--team <id>`	No	Team ID

`inf deployment instances`

List a deployment's running and terminated instances with their status, version, and stop reason.

inf deployment instances <id>

Alias: inf deployment inst

Arguments

Argument	Required	Description
`id`	No	Deployment ID; omit to pick interactively

Options

Flag	Required	Description	Default
`--team <id>`	No	Team ID	Active team
`-l, --limit <n>`	No	Max results to return (positive integer)	`100`

`inf deployment watch`

Poll a deployment until its rollout converges — status Active and the target version Running.

inf deployment watch <id>

Arguments

Argument	Required	Description
`id`	No	Deployment ID; omit to pick interactively

Options

Flag	Required	Description	Default
`--team <id>`	No	Team ID	Active team
`--target-version <id>`	No	Require this version to be the live, `Running` one	Current desired version
`--timeout <sec>`	No	Max seconds to watch before giving up	`1800`
`--interval <sec>`	No	Seconds between polls	`10`

Exits 0 on convergence; fails if the timeout elapses.

`inf deployment stop` / `start`

stop archives a deployment so it stops serving (alias of archive). start restarts a previously archived deployment so it resumes serving. Both are reversible.

inf deployment stop <id> --yes
inf deployment start <id>

Options

Flag	Required	Description	Default
`--team <id>`	No	Team ID	Active team
`-y, --yes`	Yes in non-TTY environments (`stop` only)	Skip the confirmation prompt	Off

stop prompts for confirmation in an interactive terminal; in non-TTY environments (CI, scripts) it refuses to run without -y.

`inf deployment archive`

Archive a deployment so it stops serving and frees a slot against the team cap. Reversible with start.

inf deployment archive <id> --yes

Arguments

Argument	Required	Description
`id`	No	Deployment ID; omit to pick interactively

Options

Flag	Required	Description	Default
`--team <id>`	No	Team ID	Active team
`-y, --yes`	Yes in non-TTY environments	Skip the confirmation prompt	Off

`inf deployment create`

Create a deployment with its full config version.

inf deployment create \
  --name <name> \
  --model-id <model-id> \
  --public-model-identifier <team>/<model-slug>

Options

Flag	Required	Description	Default
`--name <name>`	Yes	Deployment name	—
`--model-id <id>`	Yes	Model to deploy	—
`--public-model-identifier <id>`	Yes	Public model slug, e.g. `<team>/<model>`	—
`--project-id <id>`	No	Project to create the deployment in	Active project
`--team-id <id>`	No	Team to create the deployment in	Active team
`--desired-instance-count <n>`	No	Instance count to scale to	—
`--instance-requirements <obj>`	No	GPU instance requirements (see `allowed-instance-types`)	—
`--is-serverless-deployment <bool>`	No	Deploy as a serverless model	`false`
`--model-config-flag-overrides <obj>`	No	Engine flag overrides	—
`--model-config-version-override <n>`	No	Pin a specific model-config version	—
`--billing-exempt <bool>`	No	Exempt the deployment from billing	`false`
`--queue-timeout-ms <n>`	No	Max wait for a free slot before a `429`; use `-1` to disable queueing	Engine default
`--total-req-timeout-ms <n>`	No	Positive wall-clock cap on the whole stream	Engine default
`--time-to-next-token-timeout-ms <n>`	No	Max gap between generation progress	Shared default
`--accepted-control-tower-ids <ids>`	No	Control towers this deployment's instances may be placed on	Any tower

These three timeout flags require super-admin access. They also work with inf deployment update --id <deployment-id>. Pass null to restore the inherited default.

--accepted-control-tower-ids also requires super-admin access and takes a comma-separated list. An empty list means any eligible tower, which is the default. The set constrains where new instances are placed: instances already running are never moved when it changes. The super-admin CLI spells the same setting as a repeatable inf admin deployment create|update --accepted-control-tower <id>, with --clear-control-towers to empty it.

Prints the new deployment ID. Run inf deployment watch <deployment-id> to track its rollout.

Examples

# Deploy on 1 GPU instance and watch the rollout converge
inf deployment create \
  --name support-model \
  --model-id <model-id> \
  --public-model-identifier acme/support-v1 \
  --desired-instance-count 1
inf deployment watch <deployment-id>

# Override an engine flag to lower max tokens served
inf deployment create \
  --name support-model \
  --model-id <model-id> \
  --public-model-identifier acme/support-v1 \
  --model-config-flag-overrides '{"max_tokens": 4096}'

Generated REST verbs

inf deployment also exposes the full deployment API surface as generated commands — versions, update, engine-config, engine-configs, inferences, inference-filter-options, public-identifier-available, training-job-for-model, open-source-models, and allowed-instance-types. Run inf deployment --help to list them and their flags.

Deployments

On this page