Is There a Limit to the Number of Projects in a Space for Tenant Data and RBAC?

·Mar 19, 2026 05:43 PM·

Hi, is there any limit to number of projects in a space ? I am trying to explore redirecting tenant data into a dedicated project for better RBAC

5 comments

· Sorted by Oldest

RunLLM
APP
·
·
There is no documented hard limit to the number of projects you can create in a Phoenix instance or space. Projects are designed to provide logical separation for traces, datasets, and experiments, and are commonly used for tenant isolation and RBAC purposes. However, as the number of projects grows, UI usability (e.g., project list filtering and pagination) and query performance may be affected, especially in multi-tenant or high-volume scenarios. Recent updates have improved project management and navigation to address these scaling needs, but no explicit maximum is enforced by the platform itself according to the documentation and release notes <https://arize.com/docs/phoenix/tracing/llm-traces/projects|[Projects - Phoenix>], <https://github.com/Arize-ai/phoenix/issues/7419|[Filter / Paginate Projects on the projects page>], <https://arize.com/docs/phoenix/release-notes/04-2025/04-09-2025-new-rest-api-for-projects-with-rbac|[New REST API for projects with RBAC>]. For advanced multi-tenant isolation (beyond project-level), Arize AX (the enterprise version) provides "spaces" and organizational boundaries, but in open-source/self-hosted Phoenix, projects are the main mechanism for tenant data separation and RBAC. You can safely redirect tenant data into dedicated projects for better access control, leveraging the built-in RBAC features <https://arize.com/docs/phoenix/settings/access-control-rbac|[Access Control (RBAC) - Phoenix>], <https://arize.com/docs/phoenix/self-hosting/features/authentication#permissions|[Permissions>]. Would you like more detail on project creation, RBAC configuration, or scaling considerations? Sources: - <https://arize.com/docs/phoenix/tracing/llm-traces/projects|Projects - Phoenix> - <https://github.com/Arize-ai/phoenix/issues/7419|Filter / Paginate Projects on the projects page> - <https://arize.com/docs/phoenix/release-notes/04-2025/04-09-2025-new-rest-api-for-projects-with-rbac|New REST API for projects with RBAC> - <https://arize.com/docs/phoenix/settings/access-control-rbac|Access Control (RBAC) - Phoenix> - <https://arize.com/docs/phoenix/self-hosting/features/authentication#permissions|Permissions>
💡 Hint: Mention RunLLM in the thread for followups.
Mikyo
·
·
hey Ramesh, good to see you here. You are talking about phoenix cloud correct?
Ramesh N.
·
·
Hi Mikyo, no I was talking about self-hosted open source version. Do projects have RBAC control in open source version ?
Mikyo
·
·
No, they currently do not, one phoenix is considered one tenant. See https://arize.com/docs/phoenix/self-hosting/architecture#tenancy There are some solutions for this in Phoenix documented on that page. We have some plans for this but not right at this second. For space level access control I'd consider Arize AX a good solution here.
Ramesh N.
·
·
Got it, thanks. let me take a look at those links and get back

RunLLM
APP
·
·
There is no documented hard limit to the number of projects you can create in a Phoenix instance or space. Projects are designed to provide logical separation for traces, datasets, and experiments, and are commonly used for tenant isolation and RBAC purposes. However, as the number of projects grows, UI usability (e.g., project list filtering and pagination) and query performance may be affected, especially in multi-tenant or high-volume scenarios. Recent updates have improved project management and navigation to address these scaling needs, but no explicit maximum is enforced by the platform itself according to the documentation and release notes <https://arize.com/docs/phoenix/tracing/llm-traces/projects|[Projects - Phoenix>], <https://github.com/Arize-ai/phoenix/issues/7419|[Filter / Paginate Projects on the projects page>], <https://arize.com/docs/phoenix/release-notes/04-2025/04-09-2025-new-rest-api-for-projects-with-rbac|[New REST API for projects with RBAC>]. For advanced multi-tenant isolation (beyond project-level), Arize AX (the enterprise version) provides "spaces" and organizational boundaries, but in open-source/self-hosted Phoenix, projects are the main mechanism for tenant data separation and RBAC. You can safely redirect tenant data into dedicated projects for better access control, leveraging the built-in RBAC features <https://arize.com/docs/phoenix/settings/access-control-rbac|[Access Control (RBAC) - Phoenix>], <https://arize.com/docs/phoenix/self-hosting/features/authentication#permissions|[Permissions>]. Would you like more detail on project creation, RBAC configuration, or scaling considerations? Sources: - <https://arize.com/docs/phoenix/tracing/llm-traces/projects|Projects - Phoenix> - <https://github.com/Arize-ai/phoenix/issues/7419|Filter / Paginate Projects on the projects page> - <https://arize.com/docs/phoenix/release-notes/04-2025/04-09-2025-new-rest-api-for-projects-with-rbac|New REST API for projects with RBAC> - <https://arize.com/docs/phoenix/settings/access-control-rbac|Access Control (RBAC) - Phoenix> - <https://arize.com/docs/phoenix/self-hosting/features/authentication#permissions|Permissions>
💡 Hint: Mention RunLLM in the thread for followups.
Mikyo
·
·
hey Ramesh, good to see you here. You are talking about phoenix cloud correct?
Ramesh N.
·
·
Hi Mikyo, no I was talking about self-hosted open source version. Do projects have RBAC control in open source version ?
Mikyo
·
·
No, they currently do not, one phoenix is considered one tenant. See https://arize.com/docs/phoenix/self-hosting/architecture#tenancy There are some solutions for this in Phoenix documented on that page. We have some plans for this but not right at this second. For space level access control I'd consider Arize AX a good solution here.
Ramesh N.
·
·
Got it, thanks. let me take a look at those links and get back