> ## Documentation index
> Fetch the complete documentation index at: https://arize.com/llms.txt
> Ask it with GET https://arize.com/ask?q=<keywords or question>. Short keywords rank best.
> Use these to discover all available pages before exploring further.

# Start Phoenix

> Run Phoenix locally, in a container, or on your own infrastructure, then send it your first trace.

Phoenix serves its UI and OTLP HTTP on port **6006**, and OTLP gRPC on port **4317**. Start it one of these ways and leave it running while you work through [Observe](/docs/phoenix/get-started/get-started-tracing) and [Evaluate](/docs/phoenix/get-started/get-started-evaluations).

## Run Phoenix

<Tabs>
  <Tab title="Local">
    Phoenix is a Python package, so `uvx` is the quickest way to run it, whatever language your agent is in.

    ```bash
uvx arize-phoenix serve
```

No [uv](https://docs.astral.sh/uv/)? `pip install arize-phoenix && phoenix serve` does the same thing. See [Terminal setup](/docs/phoenix/environments#terminal) for customization.


    Open [http://localhost:6006](http://localhost:6006) to see the UI.
  </Tab>
  <Tab title="Container">
    ```bash
docker run -p 6006:6006 -p 4317:4317 arizephoenix/phoenix:latest
```

Images are published to [Docker Hub](https://hub.docker.com/r/arizephoenix/phoenix). See [Docker](/docs/phoenix/self-hosting/deployment-options/docker) for volumes, PostgreSQL, and other options.

  </Tab>
  <Tab title="Self-host">
    Run Phoenix on your own infrastructure, backed by PostgreSQL so traces persist beyond a single process. This is the option to reach for once Phoenix is shared across a team or environment.

The [self-hosting guide](/docs/phoenix/self-hosting) covers [Kubernetes](/docs/phoenix/self-hosting/deployment-options/kubernetes), [Helm](/docs/phoenix/self-hosting/deployment-options/kubernetes-helm), [Railway](/docs/phoenix/self-hosting/deployment-options/railway), [AWS CloudFormation](/docs/phoenix/self-hosting/deployment-options/aws-with-cloudformation), [Google Cloud Run](/docs/phoenix/self-hosting/deployment-options/google-cloud-run), [Azure](/docs/phoenix/self-hosting/deployment-options/azure), and [Render](/docs/phoenix/self-hosting/deployment-options/render), plus authentication and configuration.

  </Tab>
</Tabs>

## Connect to a remote Phoenix

The quickstarts assume a local Phoenix at `http://localhost:6006`. Anywhere else, only `PHOENIX_COLLECTOR_ENDPOINT` changes.

<Note>
  Pointing at a deployment with [authentication](/docs/phoenix/self-hosting/features/authentication) enabled? Set `PHOENIX_COLLECTOR_ENDPOINT` to that deployment's OTLP HTTP traces URL, for example `https://your-phoenix.example.com/v1/traces`, and `PHOENIX_API_KEY` to an API key from its **Settings** page. A local `phoenix serve` needs no key.
</Note>

## Have an existing app?

Run the Phoenix CLI setup from your app's root directory. It detects your coding agent, hands it the instrumentation, and finishes when the first trace arrives:

```bash
npx -y @arizeai/phoenix-cli setup
```

See [Connect a project with px setup](/docs/phoenix/integrations/developer-tools/cli#connect-a-project-with-px-setup) for the full flow, CI usage, and unsupported agents.