One VPS
This route brings a shared failure and maintenance boundary. Record who accepts that work and how recovery is checked.
Separate service hosts
This route brings more records and potentially clearer separation. Record its conditions and the person who reviews them.
Four decision axes
| Axis | Question to answer |
|---|---|
| Failure boundary | Which services stop together |
| Maintenance window | Which changes share a reboot or update |
| Ownership | Whether teams need separate administration |
| Recovery order | What returns first after an incident |
Illustrative decision record
Illustrative choice: a public project wiki and private documents have different maintainers and recovery priorities. It separates them, assigns each owner and reviews the boundary after the next access change.
Conditional outcome
Use the stated trade-off for this choice, assign the named owner and review on the condition described above. It is a planning example, not a service guarantee.