I'm looking for advice on JSM architecture for our MSP environment and would love to hear from others who've faced similar decisions.
Our Situation
We're managing 100+ clients and currently debating between two approaches:
1. Current approach: Separate service project per client
2. Alternative: Single project with Organizations to manage multiple clients
The Challenge
Our current setup (separate projects) is becoming a maintenance nightmare:
- Identical configs across all projects but each needs individual updates
- Rolling out automation rule changes to 100+ projects is incredibly time-consuming
- Bulk ticket creation during incidents requires manual work across every project
- Management overhead scales linearly with client growth
What We're Weighing
- Operational efficiency vs Security isolation
- Scalability vs Flexibility
- Maintenance overhead vs Client data separation
Questions for the Community
1. Any other MSPs here? What architecture worked best for you at scale?
2. Has anyone successfully used the single-project + Organizations approach for true multi-tenancy?
3. Are there gotchas with client data isolation in the single-project model that we should know about?
Thanks in advance for any insights!