What this article covers
This article explains the core meaning of hosted, how the term is used across technology and business, and what it implies for users and operators. You will find concrete examples, comparison signals, and practical considerations to judge when something is hosted versus self-hosted, and how that distinction affects cost, control, and risk.
Definition of hosted in a technology and business context
At its simplest, hosted means a service, application, or resource is operated and made available to users by a provider on owned infrastructure, typically accessed over a network such as the internet. The provider manages the hardware, software, storage, networking, and often the day-to-day operations, while customers or tenants use the service without needing to manage those underlying components themselves. Common examples include web-based email, cloud office suites, SaaS platforms, and managed databases.
The term can also describe the party or entity that makes a service available, as in “the event was hosted by the city,” but in technology the focus is on access, ownership, and management boundaries. A hosted offering is usually delivered via a subscription or usage-based model and is accessed remotely through APIs, web interfaces, or client apps.
The opposite model: self-hosted
The counterpart to hosted is self-hosted, where you acquire, install, configure, and maintain software and infrastructure yourself, typically on your own servers or on infrastructure you directly control. Self-hosted solutions demand internal expertise, ongoing maintenance, and capital expenses for hardware, while hosted solutions trade some control for operational convenience and, often, predictable operating expenses.
Key decision factors include:
- Control over configuration, data, and upgrades
- Required internal staff and skills
- Upfront versus recurring costs
- Security, compliance, and data residency needs
- Scalability and performance requirements
Hosted in everyday technology examples
Many widely used services are hosted by a provider. Examples include:
- Email as a service (hosted in the cloud via Microsoft 365 or Google Workspace)
- Collaboration suites and document storage (e.g., Google Docs, Microsoft 365 web apps)
- Customer relationship management (CRM) and sales platforms (e.g., Salesforce)
- Enterprise resource planning (ERP) and human resources applications delivered as SaaS
- Website builders and content management systems offered as hosted platforms (e.g., Wix, Squarespace)
- Development tools and runtime environments, such as GitHub Codespaces or cloud-based CI/CD
In each case, the provider runs the infrastructure, applies updates, handles scaling, and typically offers support, while customers focus on using the tool to accomplish their goals.
Hosted software as a service (SaaS): how it works
Software as a Service (SaaS) is a common form of hosted software. The provider delivers a complete, managed application over the internet, often with multitenancy, where multiple customers share the same application instance while retaining data separation. Key characteristics include:
- Centralized hosting and management
- Automatic updates and feature rollouts
- Usage-based or subscription billing
- Access from multiple devices and locations
- Standardized security, monitoring, and support processes
Tenants typically do not manage servers or the operating system, and customization is often limited to configuration options provided by the application. Integration with other systems is usually achieved through APIs, webhooks, and prebuilt connectors.
SaaS value proposition and trade-offs
The value of hosted SaaS includes faster time to value, reduced operational overhead, and elasticity to match usage. Organizations can avoid maintaining data centers and large internal IT teams for the application layer. Trade-offs include reduced control over the runtime environment, potential vendor lock-in, and dependence on the provider’s roadmap, availability, and data policies.
Hosted infrastructure and platforms: IaaS and PaaS
Hosted is also used to describe infrastructure and platform offerings that remove the need to buy and manage physical hardware. Examples include:
- Infrastructure as a Service (IaaS): virtual machines, storage, and networking provided by a cloud provider, such as Amazon EC2, Microsoft Azure VMs, or Google Compute Engine
- Platform as a Service (PaaS): platforms for developing and running applications without managing the underlying infrastructure, such as Heroku, Google App Engine, or Azure App Service
With IaaS, you manage the operating system, middleware, runtime, and applications, while the provider handles the physical infrastructure and virtualization layer. With PaaS, the provider often manages the operating system and runtime as well, enabling developers to focus on application code. Both are hosted models compared with on-premises deployments where you own and manage the physical data center.
Implications for security, compliance, and cost
Choosing a hosted model affects security responsibilities, compliance posture, and cost structure. In shared responsibility models, the provider secures the cloud infrastructure, while you are responsible for securing your applications, data, identities, and configurations. Compliance certifications (such as ISO 27001, SOC 2, GDPR, HIPAA) often apply to the provider, but you must ensure your use of the service also meets regulatory requirements.
Cost implications include:
- Predictable operational expense (OpEx) versus capital expense (CapEx)
- Potential economies of scale and volume discounts
- Costs for data egress, API calls, and add-ons that can vary by provider
- The need to account for integration, migration, and ongoing subscription fees
For many teams, a hosted strategy reduces undifferentiated heavy lifting and allows focus on product and domain differentiation.
Evaluating hosted offerings: practical criteria
When assessing a hosted service, consider:
- Service level agreements (SLAs) for uptime, performance, and support response
- Security and compliance certifications, data handling practices, and encryption controls
- Data portability, export formats, and backup/restore options
- API capabilities, integration ecosystem, and extensibility points
- Geographic presence, latency, and data residency options
- Cost transparency, pricing tiers, and long-term cost forecasts
- Vendor stability, roadmap clarity, and community or support availability
Documenting these factors helps compare hosted options and make informed decisions aligned with organizational risk appetite and operational constraints.
Summary and key takeaways
Hosted means a provider operates and delivers a service or infrastructure over a network, managing the underlying components while users access the service remotely. It commonly refers to SaaS applications, hosted infrastructure (IaaS), and platform services (PaaS). The model offers faster deployment, reduced operational burden, and elastic scaling, at the cost of some control, potential vendor lock-in, and ongoing subscription expenses. Understanding shared responsibility, compliance implications, and total cost of ownership is essential when choosing hosted solutions.
Use this explanation as a durable reference to evaluate hosted versus self-hosted options, compare providers, and communicate clearly about what “hosted” means in technology and business contexts.
Quick comparison: hosted versus self-hosted at a glance
| Aspect | Hosted (SaaS/PaaS/IaaS) | Self-hosted |
|---|---|---|
| Management responsibility | Provider manages infrastructure and often application | |
| Upfront cost | Lower; typically subscription-based | |
| Ongoing operational burden | Low; provider handles patching, scaling, hardware | |
| Scalability and elasticity | Provider-driven, often automated | |
| Control and customization | Limited to provider’s APIs and configuration | |
| Security and compliance shared model | Provider secures infrastructure; you secure application and data |
Use this comparison to quickly assess whether a hosted or self-hosted approach better fits your constraints and priorities.