Browse this section

Your deployment and service handover checklist

A service is ready for your workload when the delivered configuration and agreed operating arrangements have been checked. Record the handover details so that your team knows how to access the system and how to request changes.

Check before going live

  • Confirm the service reference, location, CPU, RAM, storage layout, operating system and network addresses against the accepted quote.
  • Test access using the agreed account and secure channel. Store credentials in your password manager and remove temporary access when no longer needed.
  • Verify application health, DNS and certificates, and test the monitoring or backups included in your service.
  • Agree the maintenance contact, escalation route, permitted administrators and any remaining deployment tasks.

Report mismatches in the deployment ticket before moving production traffic. A successful login is not the same as a tested recovery plan: if backups are required, record the destination, retention and the result of a restore test.

Was this guide helpful?

Related guides

How to request a server configuration

You can start with a listed configuration or request a custom one. Selecting a plan opens a support request with the plan reference, advertised price, specifications and conditions. This is…

What does managed and secured by OvHosting mean?

Our services are managed and secured within the scope agreed for your configuration. The scope should identify the systems we operate, the tasks we perform and the responsibilities retained…

Need help applying this to your service?

Tell us your service reference and what you need to achieve. Never include passwords or private keys in a ticket.

Contact support →
← All knowledgebase topics