What managed and unmanaged mean on a VPS
Every VPS has two layers. The provider always runs the bottom one: the physical hosts, the virtualisation, the network, DDoS protection and billing. The question is who runs the top one, everything inside the virtual machine.
On an unmanaged (self-managed) VPS that top layer is yours: the operating system, updates, the firewall, the web server or app, and copies of your data. On a managed VPS the provider takes on some of it, typically OS updates, security hardening, a control panel and help with the software you run. There is no standard definition of "managed", so the useful question is always which tasks, exactly, the provider will do inside your server.
- Unmanaged: you get root or administrator access and full control; you are responsible for what runs inside the server.
- Managed: the provider shares that responsibility for a named list of tasks, and the price usually includes their time.
- Both: the provider still keeps the hardware, network and platform running.
Choose an unmanaged VPS if
Self-managed is the usual choice when you, or someone on your team, is comfortable on a command line or Remote Desktop:
- You are a developer, a sysadmin or an agency that sets up servers routinely.
- You need software or settings a managed plan would not allow, such as a custom stack, a game server, a VPN or a trading platform.
- You want the lowest running cost and do not want to pay for admin time you will not use.
- You are testing or running short projects, where an hourly server you can rebuild at will is more useful than support.
Choose a managed option if
If nobody on your side wants to look after a server, paying someone else to do it is cheaper than a site that stays down. Before you look for a managed VPS, check whether you need a server at all:
- You want a website or app online, not a server: BMH Apps deploys a Git repo or a one-click app such as WordPress or n8n on HTTPS without a server to manage.
- You want TallyPrime for your team: Tally on Cloud is priced per user, with TallyPrime installed and no server for you to look after.
- You do need your own server but not the setup work: CloudAIBot sizes, deploys and configures the server from a plain description, then hands it over.
What the VPS here is: self-managed, with help on hand
A BookMyHost VPS is self-managed (unmanaged): you get root or administrator access, a browser VNC console for when SSH or Remote Desktop is not reachable, one-click OS reinstall and a free snapshot. Human support for the platform, the network and billing is included.
If you would rather not do the setup yourself, CloudAIBot (in beta) installs and configures common stacks at no extra charge: Windows Server with IIS and RDP, cPanel/WHM, LAMP/LEMP, WordPress, Docker hosts, MT4/MT5 and game servers. It also helps with resizing, snapshots and common troubleshooting, and hands you to a human support engineer when needed.
Every plan includes a public IPv4 address, a 1 Gbps port, Cloudflare DDoS protection and one snapshot. The smallest general VPS starts at ₹336 a month or ₹0.66 an hour, before 18% GST, billed per started hour with a 1 hour minimum or on a monthly or longer term.
Questions to ask any provider about "managed"
Get the answers in writing before you pay for a managed plan, or before you rely on an unmanaged one:
- Which tasks inside the server are included: OS updates, security patches, software installs, troubleshooting your app?
- Who restores the server if an update breaks it, and from what: a snapshot, a backup, or nothing?
- Is there a console that works when SSH or Remote Desktop does not?
- Are snapshots and DDoS protection in the price or charged separately?
- Does support cover only the platform and network, or also the software you install?
- Is the management charged per server per month, per ticket, or included?
How to run a self-managed VPS safely
- Deploy and update
Create the server from a Linux or Windows image and install the operating system updates before anything else.
- Lock down access
On Linux, log in with SSH keys and use a normal user with sudo; on Windows, set a strong administrator password. Open only the ports your application needs.
- Snapshot before big changes
Take a snapshot from the panel before an upgrade or a new install, so a bad change can be rolled back.
- Keep copies of your data elsewhere
A snapshot is not a backup of record. Copy databases and files off the server on a schedule, for example to S3-compatible storage.
- Know your way back in
If you lock yourself out, use the VNC console from the panel; if the system is beyond repair, reinstall the image in one click and restore your data.