Hosted App Delivery: What Users & Providers Should Know

Hosted application delivery, also known as software-as-a-service (SaaS) or cloud-based app delivery, is a model where software runs on a provider’s infrastructure and users access it over the internet, typically through a web browser or thin client. Users should know that they are renting access to software rather than owning it, and providers must understand that they are responsible for availability, security, and performance. This article explains the key aspects of hosted app delivery for both sides, covering how it works, benefits, challenges, and selection criteria.

Background and Evolution

The concept of hosted applications dates back to the 1960s with time-sharing mainframes, but the modern era began in the late 1990s with the rise of the internet and the first application service providers (ASPs). These early ASPs offered remote access to enterprise software like ERP and CRM, but limited bandwidth and clunky interfaces hindered adoption. The 2000s brought software-as-a-service (SaaS) pioneers like Salesforce, which demonstrated that web-based apps could be reliable and scalable. The 2010s saw the explosion of cloud infrastructure (IaaS and PaaS) from providers like Amazon Web Services and Microsoft Azure, making it easier for vendors to build and host applications. Today, hosted delivery is the default for most new business software, from collaboration tools like Slack to complex ERP systems like NetSuite.

How Hosted Application Delivery Works

At its core, hosted application delivery involves a provider managing the hardware, operating system, middleware, and application itself, while users connect via a network. The most common architectures include:

• Web-based (SaaS): The application runs in the provider’s data center, and users interact with it through a web browser. Examples: Google Workspace, Salesforce, Microsoft 365.
• Virtual Desktop Infrastructure (VDI): The provider hosts full desktop operating systems (e.g., Windows 10) on virtual machines. Users connect via a remote desktop protocol (RDP) or Citrix, seeing a complete desktop environment. This is common for legacy apps or high-security needs.
• Remote Application Access: Individual applications are streamed to the user’s device, but the processing happens on the server. This is often achieved with technologies like Microsoft RemoteApp or Citrix Virtual Apps.
• Containerized Delivery: Applications are packaged in containers (e.g., Docker) and run on a cloud platform like Kubernetes. Users access them via a web interface or API. This is popular for microservices-based apps.

The delivery chain involves several components: the user’s device (PC, tablet, phone), the network (internet, VPN), the provider’s edge (load balancers, firewalls), and the application servers. Providers often use content delivery networks (CDNs) to cache static content closer to users, reducing latency. For dynamic content, they may use multiple data centers in different regions to ensure redundancy and low latency.

Benefits for Users and Providers

For users, hosted delivery offers several advantages over traditional on-premises software:

• Accessibility: Work from anywhere with an internet connection, on any device.
• Lower upfront costs: No need to buy servers or licenses; pay a subscription fee.
• Automatic updates: The provider handles patches and upgrades, so users always have the latest version.
• Scalability: Easily add or remove users as needs change.
• Disaster recovery: Data is backed up in the cloud, reducing the risk of loss due to local hardware failure.

For providers, the benefits include:

• Recurring revenue: Subscription models provide predictable income.
• Centralized management: Easier to maintain and update software compared to distributing to many on-premises installations.
• Market reach: Can serve customers globally without shipping physical media.
• Data insights: Can collect usage data to improve the product and target features.

Challenges and Common Problems

Despite the benefits, hosted delivery has its share of challenges. Users often face:

• Latency and performance: If the provider’s servers are far away, the application may feel sluggish. This is especially critical for real-time apps like video editing or CAD.
• Dependence on internet connectivity: No internet, no work. Offline modes are limited.
• Data security and privacy concerns: Sensitive data resides on third-party servers, raising compliance issues (e.g., GDPR, HIPAA).
• Vendor lock-in: Migrating data and workflows to another provider can be difficult and costly.
• Hidden costs: Bandwidth, storage, and API calls may incur extra charges.

Providers face their own set of problems:

• Ensuring uptime and reliability: Even a few minutes of downtime can damage reputation and violate SLAs.
• Security management: They must protect against breaches, DDoS attacks, and insider threats.
• Scaling infrastructure: Handling spikes in demand requires robust auto-scaling.
• Multi-tenancy issues: A noisy neighbor (one customer hogging resources) can affect others.
• Compliance burden: They must comply with various regulations depending on their customers’ locations.

How to Choose a Hosted Application Provider

Selecting the right provider is crucial. Users should evaluate:

1. Performance and reliability: Check uptime history, SLAs, and whether they have data centers near you.
2. Security certifications: Look for SOC 2, ISO 27001, or industry-specific certifications.
3. Data residency: Ensure data is stored in regions that comply with your legal requirements.
4. Integration capabilities: Can it connect with your existing tools (e.g., CRM, ERP)?
5. Support and documentation: What is the support response time? Are there thorough guides?
6. Cost transparency: Understand pricing per user, per feature, and any overage charges.

Providers should consider the same criteria from their perspective: choosing a cloud infrastructure provider (IaaS) that offers the right regions, compliance, and performance. They also need to plan for capacity, disaster recovery, and monitoring.

Costs and Pricing Models

Hosted apps are typically priced per user per month, but there are variations:

• Flat-rate per user: Common for collaboration tools (e.g., $10/user/month).
• Tiered plans: Basic, Pro, Enterprise with different features and limits.
• Usage-based: Pay for compute time, storage, or API calls (common in cloud platforms).
• Freemium: Free tier with limited features, paid upgrades.

Users should calculate the total cost of ownership (TCO), including subscription fees, training, integration, and any additional costs for premium support or data egress. Providers must price to cover infrastructure, development, support, and profit, while remaining competitive. It’s important to read the fine print about data caps, API limits, and early termination fees.

Security and Compliance Considerations

Security is a shared responsibility between the provider and the user. Providers must ensure physical security of data centers, network security (firewalls, intrusion detection), application security (code reviews, penetration testing), and data encryption in transit and at rest. They should also have incident response plans and comply with regulations like GDPR, HIPAA, or PCI-DSS. Users, on the other hand, are responsible for their own account management (strong passwords, multi-factor authentication), managing user access, and ensuring their own network is secure. They should also understand the provider’s data backup and retention policies, and whether they can export their data at any time.

Alternatives to Hosted Delivery

Hosted delivery isn’t the only option. On-premises software is installed and run on the user’s own hardware, offering full control but requiring IT staff and capital investment. Hybrid approaches combine both, with some applications on-premises and others in the cloud. Open-source self-hosted options give users more freedom but require technical expertise. Desktop virtualization (local VMs) is another alternative for isolation. The choice depends on factors like cost, control, compliance, and technical capability.

Frequently Asked Questions

Q: What is the difference between SaaS and hosted application delivery?
SaaS is a subset of hosted delivery. All SaaS is hosted, but not all hosted apps are SaaS. For example, a hosted virtual desktop (VDI) is not SaaS because it’s not a software application per se, but a full desktop environment. SaaS specifically refers to software delivered over the web as a service.

Q: How do I ensure my data is safe with a hosted provider?
Look for providers with strong security certifications (SOC 2, ISO 27001), encryption in transit and at rest, and regular third-party audits. Also, enable multi-factor authentication, use strong passwords, and understand the provider’s data breach notification policy. You can also encrypt data before uploading it.

Q: What internet speed do I need for hosted apps?
It depends on the app. For typical business apps like email or CRM, a stable 10 Mbps connection is often enough. For video conferencing or graphics-heavy apps, you may need 25 Mbps or more. Low latency is more important than raw speed for real-time interactions.

Q: Can I use hosted apps offline?
Some apps offer offline modes (e.g., Google Docs offline, Microsoft 365 mobile apps). However, most hosted apps require an internet connection. Check the provider’s documentation for offline capabilities.

Q: What happens if the provider goes out of business?
This is a real risk. To mitigate it, ensure you have regular data exports and backups. Some providers offer data escrow services, where a third party holds a copy of your data. Always read the terms of service regarding data ownership and termination.

Q: How do I migrate from one hosted provider to another?
Migration involves exporting your data (e.g., CSV, API), cleaning it, and importing it into the new system. It’s crucial to plan ahead, test the migration in a sandbox, and consider integration with other tools. Some providers offer migration tools or partners to assist.

Related

• Game Demos vs Early Access: Key Differences
• Choosing an Accounting Firm for a Growing Business
• Parallel vs Serial: Data & Processing Explained