Technical checklist before ordering hosting

One checklist helps the project owner, developer and administrator verify that the selected hosting meets the website's real operating needs. Mark an item only when you have evidence from the service terms or your own test. RPO is the greatest acceptable data loss; RTO is the longest acceptable recovery time.

Checklist

Technical hosting checklist

Project owner: Have you set RPO and RTO for the critical parts of the website? Document the greatest acceptable data loss and the longest recovery time.
Project owner: Do you know the total cost for the first two years? Add the renewal price, domain, mail, backups and management.
Project owner: Who controls the domain, and how will you leave? Verify access to registration, DNS and exports of files and the database.
Developer: Does the environment meet the application's requirements? Compare versions, extensions, the database, scheduled jobs and queues.
Developer: Can a change be deployed and rolled back safely? Test staging, the deployment process and restoration of the previous version.
Developer: Do you know the limits of critical operations? Check CPU, memory, disk operations and concurrent requests under load.
Administrator: Are backups complete and recovery tested? Check files, the database, retention, separate storage and a record of the restoration test.
Administrator: Are access rights separated and traceable? Require multifactor authentication, roles, key management and a change log.
Administrator: Is there an incident procedure? Verify monitoring, alerts, available logs, contacts and escalation.

First set measurable requirements for the project, then compare them with the provider's documentation. Ask for a demonstration of the backup, deployment and recovery procedures, or try them in a test environment. Leave an unverified item open until you have a specific answer.