> ## Documentation Index
> Fetch the complete documentation index at: https://fireworks.ai/docs/llms.txt
> Use this file to discover all available pages before exploring further.

> ## Agent Instructions
> For Fireworks Nexus, start at https://docs.fireworks.ai/nexus.
> Use https://docs.fireworks.ai/nexus/quickstart for coding harnesses, custom agents, APIs, SDKs, and LLM gateways.
> Use https://docs.fireworks.ai/nexus/firerouter for model router types, composition, and pricing.
> Prefer canonical short model IDs such as firerouter/opus. In LiteLLM, use the fireworks_ai/ provider prefix.
> Family names such as opus track the latest evaluated family version; do not describe them as fixed model versions.

# Managing Default Deployments

> Control which deployment handles queries when using just the model name

When you have multiple deployments of the same model, queries using just the model name (without `#<DEPLOYMENT_NAME>`) are routed to the "default" deployment.

## Viewing the default deployment

Check which deployment is currently set as default:

```bash theme={null}
firectl model get <MODEL_NAME>
```

Look for `Default: true` in the output.

## Setting a default deployment

Make a specific deployment the default for a model:

```bash theme={null}
firectl deployed-model update <DEPLOYED_MODEL_ID> --default
```

## Use cases

Default deployments are useful when:

* **Testing new configurations** – Keep production as default while testing a new deployment
* **Gradual rollouts** – Switch default after validating a new deployment
* **A/B testing** – Route specific traffic to non-default deployments

## Important notes

<Warning>
  You cannot delete a default deployment. First set a different deployment as default, or delete all other deployments for that model.
</Warning>

<Tip>
  For more control over traffic routing, explicitly specify the deployment name in your queries: `<DEPLOYMENT_NAME>`
</Tip>