Web hosting is the service or infrastructure that stores and serves a website or application. A domain name is a separate registration, DNS points names toward services, and hosting runs or delivers the site. Some companies bundle all three, but the underlying responsibilities remain different.
Quick answer: shared hosting can suit a small, relatively simple site; a VPS offers a more isolated virtual environment and greater control; dedicated servers provide a whole physical server; and cloud hosting uses provider infrastructure that can scale or be distributed. The labels are not guarantees—compare actual limits, support, security, backups, and renewal costs.
The main hosting models
| Model | What is shared or allocated | Often considered for | Main trade-off |
|---|---|---|---|
| Shared hosting | Multiple accounts use a provider-managed server environment | A simple website with modest resource needs | Lower control; limits and neighboring workloads depend on provider design. |
| VPS | A virtual server with allocated resources on a physical host | Projects that need more configuration or predictable isolation | Requires more administration unless managed. |
| Dedicated server | One customer rents or leases a physical server | Workloads needing specific hardware or control | Higher responsibility and often higher operational cost. |
| Cloud hosting | Services use a provider’s pool of computing/storage/network resources | Applications with variable or distributed needs | Billing, architecture, and configuration can be more complex. |
| Managed platform/hosting | Provider handles some infrastructure and maintenance tasks | Teams that prefer a managed environment | Less low-level control; limits and vendor features matter. |
The categories overlap. A provider may sell managed VPS, cloud instances, shared WordPress hosting, or serverless services. Ask what the plan actually provides instead of choosing from the label alone.
What a hosting plan should explain
Resources and limits
Check storage, memory, CPU or execution limits, database capacity, bandwidth or request limits, concurrent processes, and file/inode limits where applicable. “Unlimited” marketing language still operates under a service’s fair-use or technical limits. Read the acceptable-use policy and know what happens if traffic exceeds the plan.
Management and support
A managed plan may include operating-system updates, backups, monitoring, and technical support. Unmanaged services can offer flexibility but require a person who can patch, secure, and troubleshoot the server. Ask which tasks are included, when support is available, and whether it covers application code or only the host’s infrastructure.
Reliability and recovery
Look for a clear backup schedule, retention period, restore process, and any recovery fees. A backup stored in the same account or region may not protect against every failure. Keep independent copies of important data and test restoration. Uptime claims or service-level agreements should be read in their exact terms and exceptions.
Security boundaries
Hosting should support current TLS, account protection, isolation appropriate to the plan, access controls, patching, and logging. A provider’s security controls do not replace secure application code, limited administrator access, and timely updates. Ask how vulnerabilities are handled and how a compromised account can be contained.
Renewal and exit
Compare the introductory price with renewal terms, taxes, add-ons, backups, email, dedicated IPs, and migration services. Review export options and cancellation rules. A low starting fee can become expensive if key services are separate or moving away is difficult.
Choosing for a real project
A personal brochure site with a contact form may not need the same architecture as a transactional service. Start with the website’s requirements: language/runtime, database, traffic pattern, storage, compliance needs, developer skills, and recovery target. Then choose the simplest option that meets those requirements and can be maintained responsibly.
Example: a small static site. A static site consists of prepared HTML, CSS, JavaScript, and assets. It may work on static hosting or a CDN without a traditional application server. The team still needs domain configuration, HTTPS, access control, deployment history, and a rollback plan.
Example: a content site with a database. A managed platform may reduce server administration. Compare database backups, plugin support, update responsibility, caching, and how to export content if the site moves.
Example: a custom application. A VPS or cloud platform may provide the needed runtime, but someone must own patches, secrets, monitoring, scaling, and incident response. Estimate total operational work, not only monthly infrastructure expense.
Migration and launch planning
Before migrating, inventory the application, files, database, DNS, certificates, scheduled tasks, mail, and third-party integrations. Create a test copy at the new host, verify it without changing the public domain, and test forms, authentication, redirects, backups, and mobile performance. Plan a DNS cutover only after the new environment is ready. Define a rollback decision and keep the previous environment until the new site is stable.
Do not treat DNS as the backup plan. DNS changes can take time to be observed because of caching, and the old host may still receive traffic. Preserve data synchronization or schedule a maintenance window if the application changes during migration.
Questions to ask a host
- Which runtime, database, and deployment methods are supported?
- What resource limits and traffic policies apply?
- Are backups included, where are they stored, and how is a restore tested?
- Who handles operating-system and application updates?
- What support is included and what is out of scope?
- What is the renewal price and how can data be exported?
- Does the host provide HTTPS, and what setup is required?
- How are incidents, abuse reports, and account recovery handled?
Frequently asked questions
Is cloud hosting always faster? No. Performance depends on application design, configuration, network, caching, and the specific service. Measure the actual site.
Do I need a VPS for more traffic? Not automatically. Optimize the application and identify the bottleneck first. A managed platform, cache, or better plan may be enough.
Does hosting include a domain? Some providers bundle a domain, but registration and hosting are still separate services. Check renewal and ownership details.
Is shared hosting unsafe? The security model depends on the provider and application. Review isolation, updates, access controls, backups, and your own maintenance duties.
Can I change hosts later? Usually, but the effort depends on application portability, database format, DNS, mail, and provider-specific features. Keep regular exports and documentation.
Compare current plan specifications directly with providers. Prices, resource limits, and included services change, so avoid decisions based on a stale comparison table.