Describe the service before the machine
Suppose a small publisher is moving a site with public articles, a search function and a weekly download. Its brief should identify those operations, who maintains the application and which interruption would cause the most trouble. Include a representative workload and the measurements behind it. If no measurements exist, label estimates as estimates. Giving every supplier the same brief makes the replies easier to compare than asking each one to recommend its favourite server.
Keep capacity figures in separate columns
Processor, memory and storage describe resources available to the workload. A network interface speed describes a rate; a monthly transfer allowance describes an amount over a period. A filtering figure concerns another part of the service again. KoDDoS lists these separately in its range of DDoS-protected dedicated servers. Copy the headings into a worksheet, keep the units attached and ask what each published limit means for the quoted configuration. A large number in one column cannot answer a missing question in another.
Ask what happens at a limit
The normal monthly allowance is only part of the buying decision. Ask about exceeding clean-traffic allowances, storage exhaustion and the procedure when traffic needs investigation. Request an explanation of any restriction or extra charge, and keep the answer with the quotation. Avoid treating a sales headline as a detailed operating policy. Where the contract and a product page use different wording, ask the supplier to resolve that difference before relying on either interpretation.
Price the work around the server
An example cost sheet might contain a monthly server charge, a backup service, migration work and the staff time needed for updates. These are planning categories, not a price estimate for any provider. Check which responsibilities remain with your team, including application faults and restore testing. A cheaper rental can still be an expensive arrangement if it requires more maintenance than the team can provide. Conversely, paying for a task twice adds cost without clarifying ownership.
Keep the evidence that supported the decision
Save the dated quotation, the agreed task list and the answers to unresolved questions. Plan a small acceptance check covering a real page, a critical operation and the agreed support route. Ubuntu’s backup documentation is a useful reference when defining a recoverable copy, but the recovery process must match your own application. Review the purchase when the workload changes. Do not wait until an incident to discover which part of the original brief nobody accepted.
Put it into practice
| Line | Record | Clarify |
|---|---|---|
| Compute and storage | CPU, RAM, usable disk | Who maintains the application? |
| Network | Port rate and transfer allowance | What happens beyond the allowance? |
| Protection | Covered services and agreed limits | Who investigates an incident? |
| Recovery | Copy location and retention | Who performs and tests a restore? |
Sources & further reading
Examples and worksheets on this page are illustrative. Documentation links were checked in November 2026; follow the relevant product’s current instructions.
