# Targets

List the targets this project can deploy to.

### Syntax

```
$ vela targets
```

Each row is a copy of the app — `local` first, then every target bound to a server in `.vela/project.json` — with the server behind it, the domain it serves, the release it is running and whether it answered:

```
TARGET       KIND    SERVER              DOMAIN                    RELEASE
local        local   —                   http://localhost:5173     —
production   remote  root@example.com    example.com               20260827T120000Z-3f2a
staging      remote  root@example.com    staging.example.com       20260826T094500Z-b17c
```

One connection is made per machine rather than per target, since a server usually hosts several. Listing never mints an app id — running `vela targets` has no side effects.

### Options

- `--json` - Print raw JSON
- `--offline` - Skip connecting to servers
- `-i, --identity <file>` - SSH private key to authenticate with
- `--ssh-port <port>` - SSH port
- `--accept-host-keys` - Trust an unknown host key on first connect (CI)

`--offline` reports what the project is bound to without reaching out, which is quicker and works without network access. Release and reachability are left blank.

### Previews

[Previews](/deploy/previews) of a project share one server binding, so they appear as a single `preview` row with no domain and no release, however many branches are deployed. To see the previews that are actually running, ask the server with [`vela status --all`](/status), or name one with `vela status -t preview:<branch>`.