Why it matters
Shared hosting, dedicated accounts and customer-owned infrastructure trade operational simplicity for isolation and control. The deployment model shapes onboarding, support and upgrade paths.
Some customers need a different hosting or isolation model before they can buy. Each option changes upgrade ownership, observability, support and the way secrets reach the application.
Decisions to make
- List the data and control boundaries customers actually require.
- Decide who owns credentials, upgrades and incident response.
- Plan how a customer can move between deployment modes.
- Define the support boundary for shared, dedicated and customer-hosted deployments.
- Choose how updates and configuration changes are delivered in every model.
Build checklist
- Keep configuration and service contracts explicit.
- Exercise install, update and removal for each supported mode.
- Document which components still depend on a shared control plane.
- Use the same release artifact and compatibility checks across deployment modes.
- Document network, data residency and incident responsibilities.
Common mistakes
- Promising customer ownership of everything when parts of the control plane remain hosted.
- Promising self-hosting without an upgrade path.
- Treating a dedicated account as a security boundary without testing all integration paths.
Tools & references
3 starting points to compare or study. Check fit, maintenance, terms and current capabilities before choosing one.
