Operating system
User access, SSH/RDP policy, package updates, service configuration and safe restart procedures.
Choose unmanaged VPS when your team is comfortable owning the operating system, firewall, updates, monitoring, backups and application runtime.
An unmanaged VPS is infrastructure you administer yourself. The provider supplies the virtual server and underlying platform; your team is responsible for securing and operating the guest OS and software unless a separate support service says otherwise.
User access, SSH/RDP policy, package updates, service configuration and safe restart procedures.
Firewall rules, exposed ports, keys/password policy, patching, log review and application hardening.
Backups, restore tests and a recovery path for accidental deletion, corruption or failed upgrades.
Resource usage, service health, disk space, certificate expiry and alerting that reaches a person who can act.
You want package-level control, custom runtimes or deployment workflows and can operate them safely.
VPN gateways, internal tools and other services that need OS-level configuration outside a managed hosting template.
Isolated systems where flexibility matters and your technical team owns the lifecycle.
Do not assume application or OS administration is included. Use the managed option or request a separate scope if you need ongoing operational assistance.
Use key-based administration where possible, remove unnecessary exposure, patch the OS, configure a firewall, set up monitoring and backups, and document how to recover access.
A useful recommendation starts with the workload, not a package name. Share current usage, expected traffic and whether you want server administration included.
If you know the resources you need, open the live catalogue. If not, send the workload and we will help narrow the choice.