Check application requirements first: supported operating systems, versions and required packages. Choose a system you can operate and keep updated.
Choose an operating system from the VPS order options that suits your application. Provisioning the operating system does not include installing, configuring or security-testing your own application.
What to check before choosing
- The application's supported operating system and exact version.
- Availability of required runtimes, databases and extensions.
- The system's support lifecycle and update plan.
- The operator's experience with the system.
The version number is not the only factor
A command written for Ubuntu may not work unchanged on Rocky Linux. Check application compatibility separately on Alpine, which may use different base libraries.
- Select the required operating system and version on the VPS page.
- Describe the application you want to run in your request.
- After ordering and handover, check the supplied system and access. Create a verified backup before reinstalling an existing server.
Create a version matrix for the whole application
| Component | Details to check |
|---|---|
| Operating system | Release, architecture, support and update channel. |
| Runtime | The specific supported PHP, Node.js, Python or Java version. |
| Database | Engine, version, character set and migration options. |
| Binary dependencies | Package availability, matching architecture and system libraries. |
| Operations | Backups, monitoring, package updates and emergency access. |
Have a recovery path before reinstalling
Replacing the operating system can erase server data; do not treat it as a simple settings change. Verify the application and database restore in the new environment before replacing the production system.
- Inventory files, databases and configuration.
- Store the backup separately from the server being replaced.
- Test startup and key user journeys on the chosen system.
- Agree on downtime, new connection details and who is responsible for recovery.
