# Manage the edge
URL: https://openship.io/docs/cli/edge.md

Set up the reverse proxy, attach domains, apply rules, and inspect traffic.

The edge is Openship's reverse proxy and TLS layer. Use these commands with an authorized HTTP
context on a self-hosted installation. See [the edge guide](/docs/guides/the-edge) for the routing model.

## Inspect and set up

```bash
openship edge status
openship edge up
```

Running `openship edge` opens the interactive panel. The `up` command configures the managed edge;
its [reference](/docs/cli/reference/edge#openship-edge-up) lists target and setup options.

If another reverse proxy owns the HTTP/HTTPS ports, inspect its sites before taking over. Use
`edge takeover` or `edge migrate` only after reviewing their detected configuration and options.
The [existing-proxy guide](/docs/guides/the-edge#taking-over-a-server-thats-already-serving) explains the workflow.

## Domains and rules

```bash
openship edge domains list
openship edge rules list
openship edge sites
```

| Task | Reference |
| --- | --- |
| Add or remove edge hostnames | [Domain commands](/docs/cli/reference/edge#openship-edge-domains) |
| Add or remove access, redirect, or traffic rules | [Rule commands](/docs/cli/reference/edge/rules#openship-edge-rules) |
| Inspect sites managed outside project records | [Sites](/docs/cli/reference/edge#openship-edge-sites) |
| Repair managed edge configuration | [Repair](/docs/cli/reference/edge#openship-edge-repair) |

Project-owned custom domains can also be managed with [domain commands](/docs/cli/reference/domain).

## Inspect traffic

```bash
openship edge logs
openship edge traffic
openship edge analytics
```

The [command reference](/docs/cli/reference/edge) lists filters, time windows, and target options.
For certificate failures, see [DNS and TLS troubleshooting](/docs/troubleshooting/domains-ssl).