Go dedicated when…
You need control over the whole system: client copies, transports across clients, kernel or patch levels, or Basis activities that would affect other tenants.
- Basis and security practice
- Institutes running repeated batches with resets
- Project teams needing DEV/QA separation
- Demo and POC systems shown to a customer
The cost comparison people miss
A dedicated landscape looks expensive per month until you divide it across a batch or a project team. For ten or more users it is usually cheaper than ten shared subscriptions, and you get the reset ability as well.
Key takeaways
- Shared covers almost all individual practice
- Basis, security and client copies need dedicated
- Above roughly ten users, dedicated is usually the cheaper option