--- title: "Managed vs unmanaged VPS: what really changes" description: "Managed vs unmanaged VPS: see what each model includes, what support covers, what stays on your plate and which profile fits each option." url: "https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps" type: "page" language: "en-US" --- VPS · 9 min · Beginner Published on Sep 15, 2026 · Updated on Sep 15, 2026 # What changes between a managed and an unmanaged VPS The question is not about hardware, it is about who looks after the system when something breaks. Understanding where support ends saves you frustration and shows how much of your time the model you pick will take. By [Equipe StreetHosting](https://streethosting.com.br/en/autores#equipe-streethosting) · StreetHosting infrastructure and support team [Costs, plans and billing](https://streethosting.com.br/en/guides/topics/costs) Summarize with: [](https://chat.openai.com/?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "ChatGPT") [](https://claude.ai/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Claude") [](https://www.google.com/search?udm=50&aep=11&q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Google AI Mode") [](https://x.com/i/grok?text=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Grok") [](https://www.perplexity.ai/search/new?q=Summarize%20the%20key%20points%20of%20this%20StreetHosting%20guide%3A%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps.%20Highlight%20the%20step-by-step%20instructions%2C%20the%20prerequisites%20and%20the%20most%20common%20mistakes. "Perplexity") Share: [](https://x.com/intent/tweet?text=Managed%20vs%20unmanaged%20VPS%3A%20which%20one%20to%20choose&url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps "Share on X") [](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps "Share on Facebook") [](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps "Share on LinkedIn") [](https://wa.me/?text=Managed%20vs%20unmanaged%20VPS%3A%20which%20one%20to%20choose%20https%3A%2F%2Fstreethosting.com.br%2Fen%2Fguides%2Fvps%2Fmanaged-vs-unmanaged-vps "Share on WhatsApp") For agents: Copy as Markdown [.md](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps.md) In this guide 6 sections * [The line between the two models](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#a-fronteira) * [Item by item: who does what](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#tabela-escopo) * [What support covers on an unmanaged VPS](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#o-que-o-suporte-cobre) * [What stays with you](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#o-que-fica-com-voce) * [Which profile picks which model](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#perfil-de-cada-um) * [The path for those who stay unmanaged](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#caminho-do-nao-gerenciado) Quick answer The difference between a managed and an unmanaged VPS is **who administers the operating system**. On a managed VPS, the provider takes care of updates, service configuration, system security and troubleshooting inside the machine. On an unmanaged VPS, the provider guarantees the infrastructure, meaning the network, hardware, control panel, console and reinstallation, while the system, packages, firewall, application backups and the application itself stay with you. StreetHosting VPS plans are unmanaged, with full root access. ## The line between the two models[](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#a-fronteira) Both models deliver the same machine. Same processor, same memory, same NVMe disk, same uplink. What changes is who is responsible for what happens inside the operating system. Picture the boundary as a horizontal line. Below it is the infrastructure: power, network, physical host, virtualization, IP, control panel and the initial system image. That part always belongs to the provider, in both models. Above it are the installed system, the packages, the configuration, the services and your application. On an unmanaged VPS, that part is yours. On a managed one, the provider moves the line up and takes over a slice of what sits above it too. Exactly where the line stops moving up varies from provider to provider, and that is the biggest source of misunderstanding. Management rarely covers your application code, for example. Before you sign up for any managed plan, ask for the scope in writing. Another common misunderstanding is worth clearing up. Unmanaged does not mean abandoned, and it does not mean an inferior product. It is the default model of the virtual server market worldwide, and it is what keeps the monthly price where it is. When a provider offers management, it is selling system administrator hours built into the plan, and that is the most expensive item in any infrastructure operation. The price difference between the two models is basically the cost of those hours. There is also a middle ground that shows up under different names, such as semi-managed or partially managed. There the provider takes on a limited set of tasks, usually system updates and firewall configuration, and leaves the rest to the customer. The rule is the same: what counts is the list of items in the contract, not the commercial name given to the package. ## Item by item: who does what[](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#tabela-escopo) | Item | Managed VPS | Unmanaged VPS | | ----------------------------------------------- | ----------------------- | --------------------------------- | | Network, uplink and routing | Provider | Provider | | Hardware and virtualization host | Provider | Provider | | Control panel, console and reinstallation | Provider | Provider | | Operating system installation | Provider | Provider delivers the ready image | | System updates and patches | Provider | Customer | | Firewall configuration | Provider | Customer | | SSH and user hardening | Provider | Customer | | Installing services such as Nginx and databases | Provider | Customer | | SSL certificate and renewal | Provider, when in scope | Customer | | Application and data backups | Provider, when in scope | Customer | | Monitoring and alerts | Provider, when in scope | Customer | | Application code and performance | Customer | Customer | | Monthly cost | Higher | Lower | | Level of control | Limited by the scope | Full, with root access | Look at the last row. Management and control tend to pull in opposite directions. The more the provider administers, the more standardized the environment has to be, and the less freedom you have to install anything outside the standard. ## What support covers on an unmanaged VPS[](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#o-que-o-suporte-cobre) Unmanaged does not mean unsupported. It means support with a defined scope. Support is available 24 hours a day in Portuguese and covers everything you have no way of fixing on your own. * **Network and connectivity.**If the IP does not respond, if there is packet loss along the path or if routing is degraded, the problem is the provider's and a ticket resolves it. * **Hardware and host.**A failed disk, failed memory or a failure of the physical server hosting your virtual machine are the infrastructure's responsibility. * **Control panel and power actions.** Powering the VPS on, off and rebooting it when the system does not respond to any command. * **Emergency console.**Direct access to the machine's screen when SSH or RDP stop responding, whether because of a wrong firewall rule or a broken service. * **System reinstallation.** Done from the control panel, free of charge and without a ticket, when you want to start over from scratch or switch distributions. * **Account and billing questions.** Billing cycle, upgrades, payment method and invoice issuance. What falls outside the scope is just as clear: support does not debug your code, does not optimize your database queries, does not set up your web server for you and cannot restore data you never backed up. Knowing this up front saves you from disappointed expectations at the worst possible moment. ## What stays with you[](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#o-que-fica-com-voce) This is the list that defines the real cost of an unmanaged VPS. It is not long, but it is constant. * **An up-to-date operating system.** Apply security patches regularly, not only when something breaks. * **Hardened remote access.** Keys instead of passwords, an unprivileged user for day-to-day work and direct root login disabled. * **A configured firewall.** Only the ports the service actually needs. Everything else closed by default. * **Protection against intrusion attempts.** Automatic blocking of anyone who keeps trying to guess SSH passwords. * **Tested backups.** Automatic copies stored outside the VPS itself, plus an occasional test restore to prove they work. * **Monitoring.** Knowing the service is down before your users tell you. * **The application itself.** Deployment, dependencies, logs, performance and bug fixes. As for time, the initial setup of all this takes somewhere between two and four hours for someone with some Linux familiarity. Maintenance after that usually takes a few minutes per week, as long as the basics were done right the first time. The time cost has two very different components, and it is important to separate them when you decide. The first is setup time, which happens once and is predictable. The second is reaction time, which happens when something breaks at an inconvenient hour and is unpredictable by definition. If you have room for the first but no availability for the second, you need a plan: a colleague who also has access, monitoring that alerts your phone or an agreed response time with the people who depend on the service. Without that, an unmanaged VPS becomes a bet that nothing will ever go wrong. The good news is that a large part of the work can be automated. Security updates can apply themselves, backups run on a schedule, blocking of intrusion attempts works unattended and monitoring warns you before users complain. Once those four things are set up, the recurring effort drops a lot and concentrates on your application, which is where it should have been all along. ## Which profile picks which model[](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#perfil-de-cada-um) There is no superior model. There is a fit between the model and the time and knowledge you actually have. | Situation | Recommended model | Reason | | ---------------------------------------------- | ----------------- | ---------------------------------------------------------------- | | Developer who already uses the terminal | Unmanaged | Full control, lower cost and no environment limits | | Owner of a game server or community | Unmanaged | Game panels are self-contained and the learning curve is short | | Agency with several clients on the same server | Unmanaged | Lets you standardize the environment the way your own team works | | Company with nobody in-house for technology | Managed | Someone has to answer for the system, and there will be nobody | | Critical application with no on-call team | Managed | The cost of downtime outweighs the cost of management | | Anyone who wants to learn infrastructure | Unmanaged | It is the only model where you really learn | A common middle path is to get an [unmanaged VPS](https://streethosting.com.br/en/vps) and pay a trusted professional for the initial setup. You keep the control and the lower cost, and you pay once for the technical work you do not want to do. Notice that most cases land on the unmanaged side. That is not a quirk of the Brazilian market. Most projects that reach the point of needing a virtual server already have someone with some technical familiarity nearby, even if it is just the project owner. The managed model makes more sense when the operation belongs to a company whose business is not technology but which still depends on a production system to bring in revenue. ## The path for those who stay unmanaged[](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#caminho-do-nao-gerenciado) If you chose the unmanaged VPS, this is the sequence that covers the essentials. Doing it in this order keeps you from locking yourself out of your own server. * **Access first.** Set up SSH with a key, create a user without permanent privileges and disable direct root login by following [secure SSH on a Linux VPS](https://streethosting.com.br/en/guides/vps/secure-ssh-linux-vps). * **Then the firewall.** Close everything and open only what the service uses, using the step-by-step guide to [the UFW firewall on an Ubuntu VPS](https://streethosting.com.br/en/guides/vps/ufw-firewall-ubuntu-vps). * **Next, automatic blocking.** Repeated login attempts should lead to an IP ban, as shown in [setting up Fail2ban for SSH](https://streethosting.com.br/en/guides/vps/fail2ban-ssh-vps-setup). * **Finally, backups.** Automate the copy and send it off the VPS, as described in [automating backups with Restic and cron](https://streethosting.com.br/en/guides/vps/vps-backup-restic-cron). With those four items in place, you have an environment more secure than the average you see out there, and without paying a management fee. The hardware to run all of it is in the [Ryzen VPS line](https://streethosting.com.br/en/vps/ryzen), with automatic activation in about 60 seconds and infrastructure in São Paulo. In this guide * [The line between the two models](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#a-fronteira) * [Item by item: who does what](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#tabela-escopo) * [What support covers on an unmanaged VPS](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#o-que-o-suporte-cobre) * [What stays with you](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#o-que-fica-com-voce) * [Which profile picks which model](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#perfil-de-cada-um) * [The path for those who stay unmanaged](https://streethosting.com.br/en/guides/vps/managed-vs-unmanaged-vps#caminho-do-nao-gerenciado) ## Frequently asked questions What is the difference between a managed and an unmanaged VPS? On a managed VPS the provider administers the operating system, applies updates, configures services and fixes problems inside the server. On an unmanaged VPS the provider hands over a ready machine and guarantees the network, hardware, control panel and reinstallation, while the system, packages and application stay with the customer. Is the StreetHosting VPS managed? Our VPS plans are delivered as unmanaged, with full root or administrator access. 24/7 support covers the network, hardware, control panel, emergency console and operating system reinstallation. Administering the operating system internals and the application is up to you. Do I need to know Linux to use an unmanaged VPS? You need basic command line skills: connecting over SSH, installing packages, editing configuration files and reading logs. You do not have to be an expert, but you do have to be willing to learn, because nobody will log in to the server for you. Does support help if I break the VPS system? Support does not go into your application, but it gets you unstuck: if SSH stopped responding, there is an emergency console in the control panel, and if the system became unusable, you can reinstall it yourself in a few minutes at no extra cost. Is an unmanaged VPS cheaper? Yes, because you are not paying for a system administrator's time. The real cost shows up in your own hours: updates, firewall, backups and monitoring become your job, and it is worth counting that in the project budget. Next step See VPS plans Root VPS in Brazil with NVMe and Anti-DDoS. [See VPS plans](https://streethosting.com.br/en/vps) [See Ryzen VPS Ryzen 9 9950X VPS in São Paulo with root access, NVMe and gamer Anti-DDoS.](https://streethosting.com.br/en/vps/ryzen) ## Related guides [VPS Intermediate How to secure SSH on a Linux VPS: keys, passwords, fail2ban SSH is usually the first target on any VPS with a public IP. This guide walks through a practical routine that cuts the risk without complicating your day: an ED25519 key, password-free login, admin access through sudo, blocking of automated attempts and a periodic review of authorized keys. 4 min Read guide](https://streethosting.com.br/en/guides/vps/secure-ssh-linux-vps) [VPS Beginner UFW on Ubuntu VPS: firewall rules without losing SSH UFW makes the Ubuntu firewall simpler, but one rule in the wrong order locks you out of your VPS. Learn how to enable it without losing SSH, open only what you need, deal with Docker, and get back in through the console if something goes wrong. 10 min Read guide](https://streethosting.com.br/en/guides/vps/ufw-firewall-ubuntu-vps) [VPS Advanced How to automate VPS backups with restic and cron A backup that depends on you remembering does not work. With restic and cron you create encrypted snapshots, send them off the VPS, control retention and test restores without daily effort. 9 min Read guide](https://streethosting.com.br/en/guides/vps/vps-backup-restic-cron) [← Back to the Guide Center](https://streethosting.com.br/en/guides)