Best approach for thousands of projects: One Org per project vs. one Project per project?
❌Unsolved❓Question🏗️Architecture
Hello everyone! 
We are planning to implement ZITADEL service accounts into our architecture and would love some guidance on the best way to scale.
Our Use Case:
- Our app allows users to create projects. We expect to scale to thousands of projects.
- Each project needs its own isolated "space" for Machine Accounts (Service Users) and their associated keys.
- We want to ensure that machine accounts from Project A cannot access or see anything in Project B.
Our Question:
Given this scale, what is the recommended ZITADEL approach?
1. One Organization per project: Creating a new ZITADEL Org for every user project.
2. One Project per project: Using a single "Master Org" and creating a new ZITADEL Project for every user project.
Specific Concerns:
Is ZITADEL designed to handle thousands (or tens of thousands) of Organizations/Projects in terms of performance and management?
We are planning to implement ZITADEL service accounts into our architecture and would love some guidance on the best way to scale.
Our Use Case:
- Our app allows users to create projects. We expect to scale to thousands of projects.
- Each project needs its own isolated "space" for Machine Accounts (Service Users) and their associated keys.
- We want to ensure that machine accounts from Project A cannot access or see anything in Project B.
Our Question:
Given this scale, what is the recommended ZITADEL approach?
1. One Organization per project: Creating a new ZITADEL Org for every user project.
2. One Project per project: Using a single "Master Org" and creating a new ZITADEL Project for every user project.
Specific Concerns:
Is ZITADEL designed to handle thousands (or tens of thousands) of Organizations/Projects in terms of performance and management?
