Managed vs. unmanaged hosting: the key differences
With unmanaged hosting, you rent server resources and the provider stops there. You get technical access and responsibility for everything on the server: maintaining the web server software, keeping your site's programming language current, managing security certificates, configuring firewalls, backing up your files, monitoring whether your site is online, and applying security updates to the server and its software. If your server breaks at 3 AM, you're the one diagnosing and fixing it. This model makes sense for developers and technical teams. For a business owner who needs reliable online presence, it's not workable.
Managed hosting covers the infrastructure layer on your behalf. The provider—or in ArdinGate's case, the developer who built the site—takes ownership of server configuration, software updates, security certificate management, uptime monitoring, and backup execution. You don't need to understand technical server details or error logs. The infrastructure runs, and when it doesn't, someone is accountable for fixing it.
The price difference between unmanaged and managed hosting pays for two things: expertise and ongoing time. Expertise means the person managing your server understands what a secure, well-configured hosting environment looks like—correct file permissions, secure settings, security headers, a working backup system. Ongoing time means someone is actually doing those things on a regular schedule, not just setting them up once and hoping nothing breaks.
There's a third option that complicates the comparison: platform-hosted site builders like Squarespace, WordPress.com (the hosted version), and Wix. These bundle hosting with a proprietary builder. The hosting is managed in the sense that you don't touch a server, but you're locked into their platform: their templates, their feature limitations, their pricing structure. If you want to move your site, you're exporting into a format that may or may not reconstruct elsewhere. Managed hosting for a custom-built site is different because you own the files outright. The hosting is infrastructure; the site is yours.
What a legitimate managed hosting plan covers
The specifics vary by provider, but a credible managed hosting plan for a small business website covers the following. Any plan that omits items from this list without explanation is worth asking about specifically.
Security certificate installation and automatic renewal. A security certificate (often called SSL or HTTPS) makes your site secure: it encrypts visitor data, is required for any site accepting form submissions or handling customer information, and helps your Google ranking slightly. Free certificates exist, which is great. But free doesn't mean automatic. Someone still has to install the certificate on your server, and renew it every 90 days. If a certificate expires, browsers show visitors a big scary warning before they can see your site. A managed host handles all this—installation and renewal—without you doing a thing.
Automated daily backups stored far away. This is your recovery point for anything that goes wrong: a software update that breaks your site, a hack, accidental deletion of content, or data corruption. "The host has backups" isn't enough information. You want specifics: what's backed up (your files only, or files plus your database?), how often, how long they're kept, where they're stored (same server or a completely different location?), and how long a restore takes. Backups on the same server as your site don't protect you if the server itself fails. Backups stored in a completely different location are the actual safety net.
Around-the-clock monitoring so you're never surprised. Automated monitoring checks your site every few minutes and alerts the hosting team if your site stops responding or returns an error. Without monitoring, you find out your site is down when a customer emails you—maybe six hours later. With monitoring, the problem is caught within minutes and routed to someone who can fix it before it costs you leads. For a service business where the website is the main way customers reach you, downtime has a direct revenue cost. A managed host that doesn't monitor your site isn't managing your hosting—they're just renting you space.
Regular security updates for your site's programming language and server. Your site's code runs on a programming language (PHP) that releases security patches regularly. Older versions eventually stop receiving patches altogether. Running an old unpatched version means known security vulnerabilities exist on your server with no fix available. Attackers specifically scan for and exploit these outdated versions because the servers are well-documented and defenseless. A managed host keeps your programming language current and applies server security patches on a regular schedule. This isn't glamorous, but it's what separates a server that becomes a liability from one that stays secure.
Server configuration tuned for performance. Technical settings on your server—caching, compression, how requests are processed—determine how fast your site responds to visitors. A properly tuned server makes a meaningful difference in page load time even on identical hardware. A managed host sets these correctly when provisioning and maintains them. An unmanaged host gives you default settings that may or may not be optimized.
What a full website maintenance plan includes (and how it differs from hosting) →
What managed hosting does not cover
Managed hosting covers the server. It does not cover the site. This distinction is consistent across the industry, and conflating the two leads to frustrated clients and unmet expectations.
Content updates are not a hosting function. Changing copy, swapping photos, updating pricing, correcting a phone number, adding a new service description — these require editing site files and redeploying. That is development work or a maintenance plan deliverable, not something a hosting plan provides. A hosting plan has no concept of what your site says. It just serves the files you have put on the server.
Application-level bug fixes are not a hosting function. If a contact form stops working because of a PHP error in the form handler code, that is an application bug. The server is working fine; the code on the server has a problem. Hosting plans do not diagnose or fix application code. That requires someone to look at the error logs, identify the issue in the source files, fix it, and redeploy.
SEO work is not a hosting function. Updating meta descriptions, restructuring page content for target keywords, fixing crawlability issues, adding schema markup, improving internal linking — none of this is infrastructure. It is site-level work that requires someone who understands both the code and the SEO strategy.
Design changes and new pages are not hosting work. The server does not care what your site looks like or how many pages it has.
Some managed hosting tiers blur this line deliberately by bundling a monthly maintenance hour with the hosting plan. ArdinGate's Care plan, for example, includes infrastructure hosting plus one hour of content edits per month. That is a bundled product, not hosting doing more than hosting. Know which you are buying. A pure hosting plan is infrastructure only. A bundled plan adds a defined service layer. Ask before you sign, and get the scope in writing if it matters to your business.
Shared, VPS, and dedicated: what kind of server you're on
Managed hosting is a service layer on top of some underlying server infrastructure. The infrastructure type matters because it determines performance ceilings, resource limits, and isolation from other tenants. Most small business websites end up on shared hosting or a VPS, and the distinction is worth understanding even if you never touch the server yourself.
Shared hosting puts multiple sites (sometimes hundreds of them) on the same physical server, sharing CPU, RAM, and disk I/O. When another site on the same server gets a traffic spike or runs a resource-heavy process, your site may slow down. This resource contention is the primary limitation of shared hosting. At low traffic levels on a well-maintained server, the effect is minimal. At higher traffic levels, or with a noisy neighbor on the same machine, performance can degrade in ways that are outside your control. Cheap shared hosting is often unmanaged; managed shared hosting puts a service layer on top but still carries the resource contention risk.
VPS (Virtual Private Server) gives your site a virtualized environment with dedicated allocations of CPU and RAM. Other tenants on the same physical machine cannot consume your allocated resources. Performance is more predictable, and you have more control over server software configuration. VPS hosting costs more than shared hosting, but for a business-critical site it provides a meaningful stability and performance advantage. Most serious managed hosting plans for custom websites run on VPS infrastructure.
Dedicated servers give you the entire physical machine. No resource sharing at all. This is the highest-performance option but also the most expensive, and overkill for the vast majority of small business sites. A typical service business site with a few thousand monthly visitors has no need for dedicated server resources.
Cloud hosting and managed cloud platforms (AWS, Hetzner, DigitalOcean, and similar) sit between VPS and dedicated in practical terms. The underlying resources are virtual, but the provider's infrastructure scales more elastically than a traditional VPS. Many professional managed hosting setups for custom PHP sites run on Hetzner or DigitalOcean VPS instances with a managed service layer on top — this is the architecture ArdinGate uses. You get VPS-grade performance and isolation at VPS prices, with a managed service layer handling everything above the OS.
For evaluating a hosting plan, ask whether your site will be on shared infrastructure or a dedicated VPS. If shared, ask how many sites share the server and what resource limits are in place per tenant. The answer tells you whether the provider is running a quality operation or packing as many sites onto a machine as possible to maximize profit.
The security layer: what managed hosting protects against
Web server security is a layered problem, and managed hosting covers the infrastructure layers. Understanding what those layers protect against — and where they stop — helps set realistic expectations about what you are actually buying.
Firewall rules block unwanted traffic before it reaches your site. A properly configured firewall restricts which types of connections can reach your server (allowing normal web traffic while rejecting harmful traffic), drops requests from known malicious sources, and throttles repeated requests to prevent brute-force attacks. This is infrastructure-level protection. It doesn't stop every attack, but it reduces the attack surface significantly by eliminating traffic that should never reach your server.
Regular patches for your server's operating system and software fix vulnerabilities at the server level. Unpatched server software is one of the most common attack vectors for small business websites. When security researchers discover a vulnerability in server software, automated scanners find affected servers and attempt to exploit them within days. A managed host applies security patches on a defined schedule rather than leaving known vulnerabilities unpatched indefinitely.
File permission hardening restricts what the web server process can read, write, and execute. Overly permissive permissions are a common configuration error that allows attackers to escalate by writing or modifying files they shouldn't be able to touch. Correct permissions are set at provisioning time and maintained.
Malware scanning periodically scans your site files for signs of infection. This is detective work, not prevention—it finds compromises already in place rather than blocking them at entry. Catching an infection quickly limits the damage. An infected site serving malware to visitors for three weeks causes far more damage (search engine penalties, browser warnings, lost trust) than one caught and cleaned within 24–48 hours.
What managed hosting security doesn't cover: vulnerabilities in your site's own code. If your contact form has a security flaw or your login page lacks proper protections, those are application-level issues, not server configuration problems. Server security and application security are separate concerns. Website security basics: what the application layer needs →
How managed hosting is priced and what drives the cost
Managed hosting for small business websites commonly runs $25–$150 per month depending on coverage, infrastructure quality, and bundled services. The price spread is wide because "managed hosting" applies to many service levels: a $25/month plan adding basic SSL and backups to shared hosting, or $100+/month plans including VPS, daily offsite backups, uptime monitoring, software updates, content edits, and SEO reporting.
The factors that legitimately drive cost upward:
Dedicated vs. shared server infrastructure. A dedicated virtual server costs more to run than shared infrastructure. A plan priced at $25/month on shared infrastructure may be a good value; a plan at the same price claiming dedicated performance deserves scrutiny about what's actually being offered.
Backup retention and storage. Keeping 30 days of daily backups offsite costs more than keeping 7 days on the same server. What you are paying for is genuine recovery options: if you discover today that your site was compromised 10 days ago, you want a 10-day-old clean backup available to restore from.
Response time commitments. A plan committing to investigate and communicate on incidents within two hours costs more to staff than one with no stated response time. For a service business, knowing someone is monitoring your site and will respond promptly when something breaks is worth paying for.
Bundled maintenance hours. When a hosting plan includes content edit time, you are paying for a developer's hours at a better rate than project work. The cost of that hour is built into the plan price. This is not padding; it is the cost of making a developer available for small tasks on a recurring basis.
SEO reporting. Monthly SEO audits and analytics reviews require labor. If a hosting plan includes this, the price reflects it.
The low end of the market—$5–$15/month hosting plans—is almost universally unmanaged shared hosting. These are legitimate products, but the management is on you. The middle range ($25–$75/month) is where you find genuine managed hosting for small business sites. The upper range ($75–$150+/month) typically includes bundled maintenance or covers more complex infrastructure for higher-traffic sites or sites with specific performance requirements.
How to evaluate a managed hosting provider
The label "managed hosting" appears on products that differ dramatically in what they actually deliver. These questions give you a concrete basis for comparison rather than relying on marketing copy.
What infrastructure does the site run on? A shared server with many sites, or a dedicated virtual server with resources reserved just for you? If shared, what are the resource limits per site? If dedicated, what's the allocated memory and processing power? A provider that can't or won't answer this clearly is probably running shared infrastructure and hoping you don't ask questions.
What exactly is backed up and how often? Ask specifically: are both your files and your database backed up? Daily or less often? Are backups stored in a different location? How many days of backups are kept? How long does a restore take, and have they tested one recently? A plan that backs up files but not the database leaves you unable to restore your site to a known-good state.
What does uptime monitoring look like? Is there automated monitoring, or does someone check the site periodically? How often is it checked? Who gets alerted when your site goes down, and how fast is the expected response? A provider that checks every five minutes and commits to responding within two hours is materially different from one that relies on customers reporting problems.
What programming language version is available? The current, actively maintained version is the correct answer in 2026. Older versions no longer receive security patches—running an outdated version is a security liability. A provider running an outdated version as their default is not maintaining their infrastructure. Ask before migrating to avoid finding out afterward.
Who is the contact for server problems? Is there a named person or team, a ticket system, or just a generic support email? For urgent issues—site down, security certificate expired, contact form broken—you need a clear escalation path and a realistic expectation of how long it takes to reach someone who can fix it.
What is not included? Ask explicitly what the plan doesn't cover. Content updates, application bug fixes, design changes—are these in or out? If there's a maintenance hour included, what can it be used for and how is it tracked? Get this in writing to prevent disputes later.
What happens to your files if you leave? You should receive your files and a complete export of your data, period. Any arrangement where the provider keeps your files or makes them difficult to retrieve when you cancel is a red flag. Your site is yours. The hosting plan is a service you're buying; it doesn't transfer ownership of your files.
What ArdinGate's managed hosting covers
ArdinGate's hosting plans are available for sites built on the ArdinGate platform. Here is what each tier includes without the marketing vagueness:
Stable ($30/mo) is the infrastructure baseline. It covers security certificate installation and automatic renewal, nightly automated backups stored far away with 30 days of retention, around-the-clock monitoring with alerts, regular security updates for your site's software, and server configuration maintenance. This is what "managed hosting" should mean at minimum: your site stays online, your certificate doesn't expire, your files are backed up far away from the server, and someone gets notified immediately when something breaks. There are no content edits or SEO monitoring in this tier.
Care ($50/mo) adds one hour of content edits per month to everything in Stable. This covers changes you'd otherwise need to file a separate project for: updating copy, swapping photos, changing pricing, correcting business hours, adjusting contact information. Minor tasks that take 10–15 minutes get handled without a separate quote and invoice. The hour resets each month; unused time doesn't roll over, because the value is in having the service available, not in banking hours.
Growth ($75/mo) adds monthly SEO monitoring and analytics reviews to everything in Care. This covers a structured check of your Google Search visibility: which searches bring visitors, whether your pages are showing up, indexing issues, plus a review of what's working and what isn't. If something drops (a page stops appearing in results, your ranking for a target search term declines), you find out from a monthly report instead of noticing lead volume falling. The SEO layer doesn't include executing optimization changes; those are scoped separately. It's a monitoring and reporting function giving you informed visibility on search performance rather than flying blind.
All three tiers run on dedicated virtual server infrastructure (Hetzner), not shared hosting. Your server isn't competing for resources with hundreds of other sites. If you have questions about what's included or how migration from your current host would work, the contact form is the right next step.
Key takeaways
- Managed hosting covers the server layer: SSL, backups, uptime monitoring, software updates, and server configuration. It does not cover the site layer: content changes, design work, new pages, or application bug fixes.
- The difference between managed and unmanaged hosting is who owns the maintenance work. Unmanaged hosting is cheaper because you are the one doing it or deciding not to do it. Managed hosting transfers that responsibility to the provider.
- Backups should cover both files and database, stored offsite, with at least 7–14 days of daily retention. Backups on the same server do not protect you if the server fails.
- Programming language version matters for security. A managed host running an outdated version as their default is running unpatched software with known vulnerabilities. This is an important question to ask before migrating.
- Dedicated virtual server infrastructure provides resources reserved just for your site. Shared hosting pools resources among many sites. For business-critical sites, dedicated infrastructure-based managed hosting is worth the price difference.
- Platform-hosted builders like Squarespace and WordPress.com bundle hosting with a proprietary builder, which creates lock-in. Managed hosting for a custom-built site gives you infrastructure without dictating what you can build or own.
- When evaluating any managed hosting plan, get clear answers on: infrastructure type, what's backed up and how often, monitoring specifics, programming language version, and what happens to your files when you leave. Vague answers to these questions are informative.