
Choose your Path
Phoenix Cloud
Connect to a pre-configured, managed Phoenix instance
As a Container
Self-host your own Phoenix
From the Terminal
Run Phoenix via the CLI on your local machine
If you’d prefer to self-host using alternative deployment services, see this guide for more details.
Setup & Run Phoenix Cloud
1
Log In & Create a Phoenix Space
- Make a free Phoenix Cloud account
- Click the Create a Space button in the upper-right corner of the dashboard.
- Enter a name for your new space.
- After creating your space, launch your Phoenix instance directly from the dashboard.
2
Set Up Keys
To create a new API key, go to your Settings page & click down to the API Keys section. Click the Add System Key button, then provide a name for your API key. You may also include an optional description and set an expiration date if desired. All your API keys will be listed and manageable in this section.
System vs User API Keys
- System API keys represent the actions taken by the system as a whole (not tied to specific user)
- User API keys represent the actions of a particular user. They are tied to lifespan of the user that created them.
3
(optional) Add Collaborators
Phoenix Cloud supports team collaboration by allowing you to invite members to your space. You can also assign roles and permissions to manage access levels securely.Congratulations! You now have Phoenix up and running. From here, you can start sending traces, create and upload datasets, run experiments, and explore everything else Phoenix has to offer.Continue to the next guide to send your first trace and begin working with Phoenix in action.
Roles
- Admins have full control over the space, including managing members, settings, system and user API keys, and roles.
- Members can access their own profile and manage their own user API keys
Adding Collaborators
On the Settings page, click the Add User button. Enter the user’s name, email address, and assign a role. The user will receive an email invitation to log in to the Phoenix instance.Run Phoenix through your Terminal
Running Phoenix through your terminal is the fastest way to get Phoenix up and running locally.1
Install the Phoenix Library
Run the following command in your terminal to install Phoenix:
pip install arize-phoenix2
Start Phoenix
Once installed, start the Phoenix server with:
phoenix serveThis will launch Phoenix locally and make the application available in your browser. It should look something like this:
3
Open Phoenix UI
Once Phoenix is running, you can open the UI directly from the links displayed in your terminal. By default, the Phoenix UI will be available at:👉 http://localhost:6006This launches the Phoenix dashboard in your browser, where you can begin exploring logs, traces, and other features.Congratulations! You now have Phoenix up and running. From here, you can start sending traces, create and upload datasets, run experiments, and explore everything else Phoenix has to offer.Continue to the next guide to send your first trace and begin working with Phoenix in action.
Run Phoenix using Docker
Docker Hub
1
Prerequisites
- Ensure Docker is installed and running on your system. You can verify this by running:
- Phoenix Version: Our Docker Compose files are pegged to the latest release of Phoenix. If you want to use a different version, you can specify it in the
docker-compose.ymlfile.
- Persistent Disc: You can configure external disc storage to store your data in a SQLite databse
-
External Postgres: You will need to set the
PHOENIX_SQL_DATABASE_URLenvironment variable to the connection string for your Postgres instance.
2
Run Local Instance of Arize Phoenix
- Docker
- compose.yaml
- PostgreSQL
- SQLite
Pull the image you would like to run:Pick an image you would like to run or simply run the latest:See for details on the ports for the container.Navigate to http://localhost:6006 and you should see your local Arize Phoenix.Note that the above simply starts the phoenix server locally. A simple way to make sure your application always has a running phoenix server as a collector is to run the phoenix server as a side car. Look at the next tab for an example compose.yaml file.

