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

# Deploy

> Deploy your Chain on Baseten

Deploying a Chain is an atomic action that deploys every Chainlet
within the Chain. Each Chainlet specifies its own remote
environment: hardware resources, Python and system dependencies, autoscaling
settings.

### Published deployment

By default, pushing a Chain creates a published deployment:

```sh theme={"system"}
truss chains push ./my_chain.py
```

Where `my_chain.py` contains the entrypoint Chainlet for your Chain.

Published deployments have access to full autoscaling settings. Each time you
push, a new deployment is created.

### Development

To create a development deployment for rapid iteration, use `--watch`:

```sh theme={"system"}
truss chains push ./my_chain.py --watch
```

Development deployments are intended for testing and can't scale past one
replica. Each time you make a development deployment, it overwrites the existing
development deployment.

Development deployments support rapid iteration with live code patching. See the
[watch guide](/development/chain/watch).

### Environments

To deploy a Chain to an environment, run:

```sh theme={"system"}
truss chains push ./my_chain.py --environment {env_name}
```

Environments are intended for live traffic and have access to full
autoscaling settings. Each time you deploy to an environment, a new deployment is
created. Once the new deployment is live, it replaces the previous deployment,
which is relegated to the published deployments list.
[Learn more](/deployment/environments) about environments.