Managed vs. unmanaged hosting: the key differences
Unmanaged hosting rents server resources and gives you technical access; everything else is yours: web-server and programming-language updates, certificates, firewalls, backups, uptime monitoring, and security patches. A failure at 3 AM is yours to diagnose and fix. This suits developers and technical teams, but is unworkable for owners who need reliable online presence.
Managed hosting assigns configuration, updates, certificates, uptime, and backups to a provider, or ArdinGate's original developer. Infrastructure problems have an accountable fixer without requiring your server/log expertise.
The premium buys expertise, permissions, secure settings/headers, working backups, and ongoing scheduled attention. Correct setup alone doesn't replace continued management.
Squarespace, WordPress.com, and Wix combine managed infrastructure with proprietary templates, features, and pricing. Exports may reconstruct imperfectly elsewhere. Custom managed hosting separates rented infrastructure from your outright-owned, portable files.
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.
Know what you are buying
Some plans bundle services: ArdinGate Care adds one monthly content-edit hour to infrastructure. Pure hosting doesn't include site work. Confirm the defined service layer and record important scope before signing.
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 places sometimes hundreds of sites on common CPU/RAM/disk I/O. Neighbor spikes/processes can slow yours, minimally at low traffic on well-managed servers, more at scale. Managed shared plans add service without eliminating contention; cheap versions are often unmanaged.
VPS reserves CPU/RAM other tenants cannot consume, improving predictability and configuration control. It costs more than shared hosting but benefits business-critical stability/performance. Most serious custom-site managed plans use VPS infrastructure.
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 platforms, AWS, Hetzner, DigitalOcean, sit between VPS/dedicated with elastic virtual resources. ArdinGate uses the common custom-PHP model: Hetzner/DigitalOcean VPS plus management above the OS, providing VPS performance/isolation at VPS prices.
Ask shared versus dedicated VPS. On shared plans, request site counts and per-tenant limits; these distinguish quality hosting from overcrowded profit maximization.
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 buying.
Firewalls permit normal web connections, reject unwanted/known-malicious sources, and throttle repeated requests against brute force. This infrastructure layer reduces attack surface substantially without preventing every attack.
Scheduled OS/software patches close major small-business attack routes. Scanners exploit disclosures within days; managed hosts apply fixes on defined schedules instead of leaving known flaws 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 scans detect, not prevent. Finding infection within 24–48 hours limits search penalties, browser warnings, and trust damage compared with three weeks of malicious service.
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 plans range $25–$150/month: $25 shared SSL/backups versus $100+ VPS, daily offsite copies, uptime, updates, edits, and SEO reports. Coverage/infrastructure/bundles explain variation.
The factors that 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 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. Included content-edit time buys developer hours below project rates. The plan price covers recurring availability for small tasks; it is not padding.
SEO reporting. Monthly SEO audits and analytics reviews require labor. If a hosting plan includes this, the price reflects it.
Almost universally unmanaged shared hosting. These are legitimate products, but the management is on you.
Where you find genuine managed hosting for small business sites.
Commonly 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 deliver. These questions give you a concrete basis for comparison rather than relying on marketing copy.
What infrastructure? Ask shared-site resource limits or dedicated virtual CPU/memory. Evasive providers likely use shared systems they prefer not to explain.
Backup specifics? Files and database, frequency, separate storage, retention, restore duration, recent restore tests. Files-only backups cannot recover a known-good complete site.
Monitoring specifics? Automated or manual, frequency, alert recipient, response commitment? Five-minute checks/two-hour response differs materially from waiting for customer complaints.
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.
Leaving must include files/data exports. Hosting purchases service, not ownership transfer. Withheld or hard-to-retrieve files are warning signs.
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:
Core covers certificate installation/auto-renewal, nightly remote backups with 30-day retention, continuous monitoring/alerts, DNS, and scheduled server patches. Someone is notified immediately of failures. Content edits/application patching aren't included.
Care adds up to one editing hour a month, proactive application patches, and quarterly performance reviews to Core. Copy, photos, prices, hours, and contact changes, including 10–15-minute tasks, need no separate quote/invoice. Hours reset monthly without rollover; availability is the value.
Priority adds two editing hours, three total monthly, same-day critical response, staging previews, and monthly analytics to Care. Suits urgent turnaround and larger reviewed changes; reports clarify what's working between check-ins.
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 a rolling 30 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.
Managed hosting questions
Can I switch to managed hosting if my site was built by someone else?
Yes, infrastructure is builder-independent. Export files/data, prepare server, verify, then repoint domain settings. Straightforward moves take two to four hours. Arrange hosting/registrar access and required settings/API keys first; competent providers handle or guide migration. Test before switching and allow propagation of hours, sometimes 48 hours.
Is managed hosting worth it for a small business site?
For revenue/lead/booking sites, $30–$100/month usually pays for itself versus self-managed SSL, updates, backups, and alerts. One or two billable hours can cover it; three-hour outages or warnings lose prospects. Unmanaged hosting suits personal projects/portfolios with little downtime impact.
Is managed hosting better than WordPress.com or Squarespace?
Yes. WordPress.com/Squarespace lock hosting to builders, templates, features, and prices. Custom sites avoid CMS overhead/unnecessary database work, measurably improve Google speed scores, and move to compatible servers. Squarespace stays on Squarespace. Understanding ownership limits prevents expensive later changes.
What happens to my site if I stop paying for managed hosting?
Lapsed hosting takes sites offline. ArdinGate cancellation supplies complete files/database for another compatible host. Squarespace/WordPress.com exports may reconstruct only partially because platforms own the system. Custom sites separate rented servers from owned assets. Request exports before expiration to avoid access complications.
How is managed hosting different from a maintenance plan?
Hosting covers servers, certificates, monitoring, backups, versions, and patches. Site maintenance adds content/design/pages, code bugs, SEO, and features requiring edit/test/deploy work. Care bundles one monthly hour; that's an added service layer. Record scope so pure-hosting contracts don't imply content changes.
Do I need managed hosting if my site gets low traffic?
Business impact matters more than traffic. At 50 or 5,000 monthly visitors, one missed client can exceed hosting fees. Restaurants, contractors, therapists, consultants, and other services rely on availability. Personal/hobby sites tolerating six-hour outages can reasonably use cheaper unmanaged hosting.
What programming language version does managed hosting need to support?
In 2026, use supported versions; retired software leaves new flaws unpatched. Ask available language versions and automatic/requested upgrades without rebuilding. Outdated versions in 2026 indicate neglected, insecure infrastructure.