Project Limits and Best Practices for Multi-Tenant Setups

Soufiane E. · 2025-05-05T13:17:20.965Z

Hi there Phoenix community! I was wondering if there is a limit to the number of created projects? And for instance, if I go above 50 projects, is there pagination/search? As I am handling a multi-tenant setup, it makes sense to split traces across independent projects. Is this the intended practice? Also what is the impact in terms of performance? (one project and filter on attribute/tag vs. multiple projects) Thanks for your help!

Project Limits and Best Practices for Multi-Tenant Setups | Arize AI Community

5 comments

· Sorted by Oldest

RunLLM
APP
·
There is no documented hard limit to the number of projects you can create in Phoenix; users have reported handling hundreds of projects. Pagination and search are supported in the UI and API, and as of version 4.31.0, a project auto-refresh toggle was added to improve usability with many projects (GitHub Issue #4398, Projects API Docs).Splitting traces across independent projects is the intended and recommended practice for multi-tenant setups, as projects provide logical separation and organizational clarity. Filtering by attribute/tag within a single project is possible, but using multiple projects is preferred for isolation and comparative analysis. Performance-wise, the main impact is on the project page load time as the number of traces grows, but Phoenix has implemented optimizations like pagination and lazy loading to mitigate this (Projects Feature Docs, Performance Issue #6201). Would you like more detail on performance or best practices?Sources: - GitHub Issue #4398 - Projects API Docs - Performance Issue #6201
💡 Hint: Mention RunLLM in the thread for followups.
Soufiane E.
·
RunLLM How are the projects sorted? How can I look up a specific projects by name once there are too many to show in one page
Soufiane E.
·
RunLLM How are the projects sorted? How can I look up a specific projects by name once there are too many to show in one page
RunLLM
APP
·
Projects are sorted by their ID in ascending order by default in the backend (queries.py). To look up a specific project by name, you can use the REST API or Python client to fetch a project directly by its name, or use the GraphQL API to paginate and search through projects (Projects API Docs).For example, with the Python client: LBKSfrom phoenix.client import Client client = Client(base_url="your-server-url") project = client.projects.get(project_name="My Project")LBKSThis retrieves the project by name regardless of pagination. Would you like more detail on using the API or GraphQL for searching?Sources: - queries.py - Projects API Docs
💡 Hint: Mention RunLLM in the thread for followups.
Anthony P.
·
Hey there Soufiane E., thanks for using Phoenix and thanks for the great questions! The Phoenix UI does not currently support filtering or pagination on projects. I have filed a ticket to capture your request here https://github.com/Arize-ai/phoenix/issues/7419 It would be great to hear more about your use case in the ticket, or here in slack, so we can get a better picture of what we can do to improve the Phoenix UI
✅1

RunLLM
APP
·
There is no documented hard limit to the number of projects you can create in Phoenix; users have reported handling hundreds of projects. Pagination and search are supported in the UI and API, and as of version 4.31.0, a project auto-refresh toggle was added to improve usability with many projects (GitHub Issue #4398, Projects API Docs).Splitting traces across independent projects is the intended and recommended practice for multi-tenant setups, as projects provide logical separation and organizational clarity. Filtering by attribute/tag within a single project is possible, but using multiple projects is preferred for isolation and comparative analysis. Performance-wise, the main impact is on the project page load time as the number of traces grows, but Phoenix has implemented optimizations like pagination and lazy loading to mitigate this (Projects Feature Docs, Performance Issue #6201). Would you like more detail on performance or best practices?Sources: - GitHub Issue #4398 - Projects API Docs - Performance Issue #6201
💡 Hint: Mention RunLLM in the thread for followups.
Soufiane E.
·
RunLLM How are the projects sorted? How can I look up a specific projects by name once there are too many to show in one page
Soufiane E.
·
RunLLM How are the projects sorted? How can I look up a specific projects by name once there are too many to show in one page
RunLLM
APP
·
Projects are sorted by their ID in ascending order by default in the backend (queries.py). To look up a specific project by name, you can use the REST API or Python client to fetch a project directly by its name, or use the GraphQL API to paginate and search through projects (Projects API Docs).For example, with the Python client: LBKSfrom phoenix.client import Client client = Client(base_url="your-server-url") project = client.projects.get(project_name="My Project")LBKSThis retrieves the project by name regardless of pagination. Would you like more detail on using the API or GraphQL for searching?Sources: - queries.py - Projects API Docs
💡 Hint: Mention RunLLM in the thread for followups.
Anthony P.
·
Hey there Soufiane E., thanks for using Phoenix and thanks for the great questions! The Phoenix UI does not currently support filtering or pagination on projects. I have filed a ticket to capture your request here https://github.com/Arize-ai/phoenix/issues/7419 It would be great to hear more about your use case in the ticket, or here in slack, so we can get a better picture of what we can do to improve the Phoenix UI
✅1