# Status

Show what is deployed: the running release, the domain it serves and whether the services are up.

### Syntax

```
$ vela status
```

```
$ vela status -t staging
```

Reports on one [target](/deploy) of this project, defaulting to `production`. Nothing is deployed locally, so `-t local` has nothing to report — [`vela dev`](/dev) prints what it is running. A [preview](/deploy/previews) is named as `-t preview:<branch>`.

A `Managed` row lists the `velastack.app` hostnames the target is served or redirected on, when it has any. See [Domains](/deploy/domains).

### Options

- `-t, --target <target>` - Which copy of the app to act on, defaults to `production`
- `--server <ssh>` - Server this target runs on, recorded on first use
- `--all` - Show every app on the server, not just this project
- `--json` - Print raw JSON
- `-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)

### Every app on a server

`--all` is a question about the machine rather than about this project, so it works outside a project directory as long as a server is given:

```
$ vela status --all --server root@example.com
```

`--json` prints the same information unformatted, for scripting.