Self-hosted ZITADEL scalability question (Cloud Run + Cloud SQL)
🏬Self-hosted❓Question📈Performance✅Solved
Hi 
I've been evaluating the self-hosted OSS version. As an initial test I deployed it on Google Compute Engine using Docker Compose, and set up several features including:
• multiple orgs
• federation
• SAML
• custom UI
• Terraform-based configuration
Everything works well so far.
Our planned production setup would likely run on Google Cloud Run with Cloud SQL, and the final thing I was asked to investigate is scalability.
Specifically: do you foresee any bottlenecks or operational issues when running ZITADEL with roughly 100k–10M users across many organizations in a self-hosted deployment?
Any guidance, known limits, or infrastructure recommendations would be greatly appreciated.
I've been evaluating the self-hosted OSS version. As an initial test I deployed it on Google Compute Engine using Docker Compose, and set up several features including:
• multiple orgs
• federation
• SAML
• custom UI
• Terraform-based configuration
Everything works well so far.
Our planned production setup would likely run on Google Cloud Run with Cloud SQL, and the final thing I was asked to investigate is scalability.
Specifically: do you foresee any bottlenecks or operational issues when running ZITADEL with roughly 100k–10M users across many organizations in a self-hosted deployment?
Any guidance, known limits, or infrastructure recommendations would be greatly appreciated.
