Solutions / Hosting
Hosting & Website Infrastructure
Hosting Solutions
Find the right place for your website, online store or application to run. Start with what you are working on, see the main options side by side, and go to a provider when you are ready.
- Start from your situationFour business contexts
- Same criteria throughoutSeven hosting dimensions
- Trade-offs up frontWhat to watch for, stated plainly
Which area are you working on?
Choose the closest match. Each context sets out the questions to ask, the main solution paths and, where we list one, a suitable option.
Hosting a company website
Keeping a company, service-business or lead-generating site online, safe and easy to recover.
Hosting an online store
Keeping checkout reliable, fast and secure when orders depend on it.
Managing multiple websites
Looking after several websites, your own or your clients’.
Running applications, internal tools or automation
Giving software you run a computing environment of its own.
Find the solution that fits
Work through the context that matches yours. For the full decision, read the Hosting & Website Infrastructure guide.
Hosting a company website
A company, service-business or lead-generation website has to stay online, load reliably and be easy to restore when something breaks. The real decision is how much of the maintenance the business wants to carry itself: updates, security, backups and recovery. The right route depends on the platform the site is built on, how much traffic it gets and how much technical capacity the team has.
More about this context
Your website informs visitors, brings in enquiries or bookings and builds credibility. It may be a brochure site, a service business site or a lead-generation site, built on WordPress or another platform, and it does not change much from day to day. The decision is about dependable running and easy recovery rather than maximum capacity.
For many companies the website is the shop window: it has to be there when a customer looks, and recoverable quickly if something goes wrong. It may run on WordPress or another platform; the platform shapes who has to keep it up to date, but the hosting decision is the same one: how much of the running do you want to carry yourself?
How the paths differ
The approaches differ mainly in how much the provider does for you. Shared hosting is the entry point: many sites on one server, with the provider running the server. Managed hosting adds server maintenance, patching and often backups and monitoring. If the site runs on WordPress, managed WordPress hosting adds platform-specific help such as caching, updates and a staging copy, and a managed VPS or cloud plan suits sites that outgrow standard plans.
Supporting detail
Questions to ask yourself. 5 questions to settle first
- Who will look after updates, security and backups?
- Is the site built on WordPress or another platform, and who keeps that platform up to date?
- How much traffic do you expect, and how steady is it?
- Can you restore a backup yourself, and how quickly?
- What will the plan cost at renewal, not only in the first term?
Why this decision matters. What is at stake
A website that is slow, offline or hard to recover costs enquiries and credibility. Matching the hosting approach to who will maintain the site, and to the platform it runs on, avoids paying for capacity you do not need or carrying work nobody on the team wants.
Before choosing. A short checklist
- Check how backups work and whether you can restore them yourself
- Compare the renewal price, not only the introductory rate
- The scope of “managed” varies, so check what is actually included
- On WordPress, plugin updates often remain your responsibility: ask who updates plugins and who restores after a failed update
Want the full background? Choosing a hosting model: a two-step framework
Choose the path that fits
Select a path to see why it fits and what to watch for.
Shared hosting
Many sites share one server, and the provider looks after it.
Best fit
- Modest, steady traffic
- Informational sites
Main thing to check
Fair-use limits and renewal price
Managed hosting
The provider also handles maintenance, patching and often backups.
Best fit
- Teams without server skills
- Backups handled for you
Main thing to check
What “managed” actually covers
Managed WordPress hosting
Hosting tuned for WordPress, with updates, caching and restores handled.
Best fit
- WordPress sites
- Sites that earn leads
Main thing to check
Who updates plugins
Managed VPS / cloud
A managed server or cloud plan with more control and room to grow.
Best fit
- Plugin-heavy sites
- Higher-traffic sites
Main thing to check
Who handles updates and backups
Managed hosting
Why choose it
- The provider takes on maintenance and patching
- Often backups and monitoring too
- Fewer decisions about the server
Best when
- Nobody on your team wants to run a server
- You want backups and monitoring to be the provider’s job
Watch for
- The scope of “managed” varies: check what is included
- Check how backups work and whether you can restore them yourself
Full decision detail
Why it helps
- The provider takes on maintenance, patching and often backups
- Fewer decisions to make about the server
Fits when
- Nobody on your team wants to run a server
- You want backups and monitoring to be the provider’s job
Watch for
- The scope of “managed” varies, so check what is actually included
- Check how backups work and whether you can restore them yourself
The provider also handles server maintenance and security patching, and often backups and monitoring.
Managed WordPress hosting
Why choose it
- Core updates, caching and restores are handled
- A staging copy to test updates first
- Support that understands WordPress
Best when
- There is no in-house capacity for updates and restores
- An hour of downtime would cost more than the price difference
Watch for
- Plugin updates often remain your responsibility
- Plans can restrict plugins and configuration
Full decision detail
Why it helps
- Core updates, caching and restores are taken off your plate
- A staging copy lets you test updates before visitors see them
- Support understands WordPress, not just the server
Fits when
- The site publishes regularly or earns leads
- There is no in-house capacity for updates, security and restores
- An hour of downtime would cost more than the price difference
- Maintenance is taking time better spent elsewhere
Watch for
- Plugin updates often remain your responsibility: ask who updates plugins and who restores after a failed update
- Managed WordPress plans can restrict plugins and configuration
- Pricing is often tied to visits or the number of sites
- Plugin-heavy sites on minimal plans can struggle
For a company website that runs on WordPress: managed hosting tuned for WordPress, typically with caching built into the platform, automatic core updates, a staging copy for testing and support that knows WordPress.
WordPress is flexible, and that flexibility brings continuous maintenance: core, theme and plugin updates, backups, speed and security. Managed WordPress hosting takes much of that on, with caching built in, automatic core updates, a staging copy for testing changes and support that knows WordPress. Plugin updates often remain your responsibility, so ask who updates plugins and who restores after a failed update.
When you may need more. If the site is plugin-heavy or high-traffic, a well-supported managed VPS or cloud plan gives more room.
Managed VPS / cloud
Why choose it
- More control over resources and configuration
- Room to grow for heavier sites
Best when
- The site is plugin-heavy or higher-traffic
- You want more control than a standard managed plan gives
Watch for
- Plugin-heavy sites on minimal plans can struggle
- Be clear who is responsible for updates and backups
Full decision detail
Why it helps
- More control over resources and configuration
- Room to grow for heavier sites
Fits when
- The site is plugin-heavy or higher-traffic
- You want more control than a standard managed plan gives
Watch for
- Plugin-heavy sites on minimal plans can struggle
- Be clear who is responsible for updates and backups
A managed server or cloud plan, run with support that understands your platform, for company sites that outgrow standard plans, including plugin-heavy WordPress sites.
Compare the main paths
Show the comparison. The paths side by side
| What to look at | Shared hosting | Managed hosting | Managed WordPress hosting | Managed VPS / cloud |
|---|---|---|---|---|
| Who manages the server | The provider | The provider | The provider, tuned for WordPress | The provider, with more control for you |
| Maintenance burden | Provider runs the server | Provider patches; often backups too | Core updates, caching and restores handled | Provider-run; agree who updates and backs up |
| Best suited to | Modest, steady traffic | Teams without server skills | WordPress sites that earn leads | Plugin-heavy or busier sites |
| Control / flexibility | Limited by the plan and fair-use limits | Depends on what the plan includes | Tuned for WordPress; plugins may be restricted | More control over resources |
| Main thing to check | Fair-use limits and renewal price | What “managed” covers | Who updates plugins | Who handles updates and backups |
See full comparison
| What to look at | Shared hosting | Managed hosting | Managed WordPress hosting | Managed VPS / cloud |
|---|---|---|---|---|
| What it gives you | You pay for what you need, not spare capacity | Fewer decisions about the server | A staging copy to test updates, and WordPress-aware support | Room to grow for heavier sites |
| Before you commit | Compare the renewal price, not only the first term | Check how backups work and whether you can restore them | Ask who restores after a failed update | Be clear who is responsible for updates and backups |
No option listed yet
We’re currently reviewing suitable options for this area.
Hosting an online store
An online store turns hosting problems into lost sales. Cart, checkout and payment steps are dynamic and cannot simply be served from a page cache, and campaigns or seasonal peaks can multiply traffic. Shops can run on dedicated platforms or on WordPress with WooCommerce. Whichever you use, the hosting question is the same: can the site keep taking orders when traffic spikes, and who responds when it does not?
More about this context
An online store turns hosting problems into lost sales. Cart, checkout and payment steps are dynamic and cannot simply be served from a page cache, and campaigns or seasonal peaks can multiply traffic.
Shops can run on dedicated platforms or on WordPress with WooCommerce, among others. Whichever you use, the hosting question is the same: can the site keep taking orders when traffic spikes, and who responds when it does not?
How the paths differ
Managed hosting for online stores is tuned for shops and takes server maintenance and patching off your hands. Cloud hosting draws on a pool of infrastructure that can scale as demand changes. An actively managed VPS gives you resources of your own with the upkeep done for you. The more your revenue depends on peaks, the more capacity planning and support response matter.
Supporting detail
Questions to ask yourself. 5 questions to settle first
- What does an hour offline cost the business?
- Which platform is the store built on, such as WooCommerce on WordPress or a dedicated shop platform, and does the host support it?
- How sharp are your traffic peaks during campaigns or seasons?
- Does checkout stay accurate under caching and load?
- Who responds quickly when the site fails?
Why this decision matters. What is at stake
An online store turns hosting problems into lost sales. Reliability, capacity for peaks and fast support protect revenue, and caching has to be set up so cart, checkout and account pages stay accurate.
Before choosing. A short checklist
- Ask how checkout behaves under load, and consider a load test before a major launch
- Caching rules must exclude cart, checkout and account pages, and need testing after each change
- Read the fair-use terms behind “unlimited” plans
- Card-payment responsibilities remain partly yours: confirm them with your payment provider (this page is not compliance advice)
Want the full background? Online shops raise the stakes
Choose the path that fits
Select a path to see why it fits and what to watch for.
Managed hosting for online stores
Hosting tuned for shops, with server maintenance and security patching handled.
Best fit
- Orders and payments through the site
- Sharp traffic spikes
Main thing to check
Fair-use terms behind “unlimited”
Cloud hosting
Resources drawn from a pool that can scale as demand changes.
Best fit
- Campaign or seasonal peaks
- A known cost of downtime
Main thing to check
How scaling is billed
An actively managed VPS
A virtual private server the provider actively manages, with resources of your own.
Best fit
- No in-house monitoring
- A busy shop
Main thing to check
What “managed” covers
Managed hosting for online stores
Why choose it
- Reliability and fast support response protect revenue
- Capacity can be raised before a campaign or seasonal peak
Best when
- Orders and payments run through the site
- Campaigns or seasons bring sharp traffic spikes
Watch for
- Read the fair-use terms behind “unlimited” plans
- Caching rules must exclude cart, checkout and account pages, and need testing after each change
Full decision detail
Why it helps
- Reliability and fast support response protect revenue
- Capacity can be raised before a campaign or seasonal peak
Fits when
- Orders and payments run through the site
- Campaigns or seasons bring sharp traffic spikes
Watch for
- Read the fair-use terms behind “unlimited” plans
- Caching rules must exclude cart, checkout and account pages, and need testing after each change
Hosting tuned for shops, including WooCommerce or other shops on WordPress, where the provider handles server maintenance and security patching.
Cloud hosting
Why choose it
- Capacity can be raised before a campaign or seasonal peak
Best when
- Campaigns or seasons bring sharp traffic spikes
- You can estimate what an hour offline costs the business
Watch for
- Scaling that is possible is not always automatic; check how it works
- Cost can rise under load, so ask how capacity is billed
Full decision detail
Why it helps
- Capacity can be raised before a campaign or seasonal peak
Fits when
- Campaigns or seasons bring sharp traffic spikes
- You can estimate what an hour offline costs the business
Watch for
- Scaling that is possible is not always automatic; check how it works
- Cost can rise under load, so ask how capacity is billed
Resources drawn from a pool of infrastructure that can scale as demand changes.
An actively managed VPS
Why choose it
- Resources of your own with the upkeep done for you
Best when
- You have no in-house team to monitor the site
- You want predictable resources for a busy shop
Watch for
- Check what “managed” covers, including security patching and monitoring
Full decision detail
Why it helps
- Resources of your own with the upkeep done for you
Fits when
- You have no in-house team to monitor the site
- You want predictable resources for a busy shop
Watch for
- Check what “managed” covers, including security patching and monitoring
A virtual private server that the provider actively manages, giving dedicated resources without running the server yourself.
Compare the main paths
Show the comparison. The paths side by side
| What to look at | Managed hosting for stores | Cloud hosting | Managed VPS |
|---|---|---|---|
| What it is | Hosting tuned for shops, with maintenance and patching handled | Resources drawn from a pool that can scale | Dedicated resources, actively managed by the provider |
| Best suited to | Orders and payments through the site; sharp traffic spikes | Campaign or seasonal peaks, where you can cost an hour offline | No in-house team to monitor; predictable resources for a busy shop |
| What it gives you | Reliability and fast support response protect revenue | Capacity can be raised before a peak | Resources of your own with the upkeep done for you |
| Main thing to check | Fair-use terms behind “unlimited”; caching must exclude cart and checkout | Scaling is not always automatic; cost can rise under load | What “managed” covers, including patching and monitoring |
No option listed yet
We’re currently reviewing suitable options for this area.
Affiliate links may earn Kybervega a commission. Disclosure
Managing multiple websites
Managing several websites, your own or your clients’, adds updates, backups, access and billing to keep track of, and a problem on one site should not spread to the others. The decision is how much of the server work you want to carry: a hosting plan built for many sites, or a control panel you run on a server of your own.
More about this context
Managing several websites is different from managing one. Your own sites might sit alongside a shop, a campaign site or a client’s site, and an agency or freelancer may look after many. Each site brings its own updates, backups, access, domain and billing, and a routine that worked for one site soon becomes a spreadsheet of exceptions.
The decision is how much of that you want to carry yourself and where the sites should live. Some people want a hosting plan built for many sites. Others run their own servers and want one panel to manage them. This section is for anyone weighing those routes, and for anyone who simply wants to know what a control panel does.
How the paths differ
There are two broad routes. Managed multi-site hosting is a hosting plan designed for many sites, where the provider takes on the server work and gives you tools to manage the sites together. The control-panel route puts a management layer on a server or hosting account you already have or choose, so you manage sites, email, DNS and databases from one place, while the server itself is still yours, or your host’s, to run.
Supporting detail
Questions to ask yourself. 4 questions to settle first
- How are sites kept separate from one another?
- Can a site be handed to a client cleanly, with a full copy?
- Can you restore a single site yourself?
- How many sites will you run in a year?
Why this decision matters. What is at stake
With one site, a problem is a problem. With several, one compromised or misconfigured site can affect the others if they share an account or a server, and a routine that depends on remembering which site needs what is easy to get wrong. Handing a site to a client adds ownership questions: whose account is it, and can you export a complete copy?
Doing it by hand, site by site, is fine for two or three. Beyond that it becomes a steady cost in time and risk. Choosing early how sites are separated, backed up and handed over avoids rework later.
Before choosing. A short checklist
- Ask how sites are isolated from one another
- Check the terms for handing a site to a client, including who owns the account and how a full copy is exported
- Limits on the number of sites often trigger upgrades, so price the plan for the number of sites you expect
- Check whether you can restore a single site yourself
Want the full background? Choosing a hosting model: a two-step framework
Choose the path that fits
Select a path to see why it fits and what to watch for.
Managed multi-site hosting
Hosting plans built for many sites, with isolation between them.
Best fit
- Agencies and freelancers
- Owners of several sites
Main thing to check
Hand-over terms and site limits
Hosting control panel
One dashboard for sites, WordPress, email, DNS and databases on a server.
Best fit
- Agencies and IT administrators
- Teams that run their own servers
Main thing to check
It still needs a server to run on
Managed multi-site hosting
Why choose it
- Isolation limits the damage if one site is compromised
- One routine for updates, backups and access
Best when
- You host client sites or run several of your own
- You take on or hand over sites from time to time
Watch for
- Check how a site is handed to a client, including a full export
- Site-count limits often trigger upgrades
Full decision detail
Why it helps
- Separation between sites limits the damage if one is compromised
- Updates, backups and access can follow the same repeatable routine for every site
Fits when
- You host sites for clients, or run several sites of your own
- You take on or hand over sites from time to time
Watch for
- Check the terms for handing a site to a client, including who owns the account and how a full copy is exported
- Limits on the number of sites often trigger upgrades, so price the plan for the number of sites you expect
Hosting plans designed for many sites, with isolation between them and tooling to look after them together.
This is the simpler route: the provider runs the server, keeps sites separated and gives you a dashboard for each. It suits agencies and businesses that want isolation, backups and handover without administering servers. You give up some control over the server and work within the plan’s limits on the number of sites.
When you may need more. If you need to install your own software, control the operating system or run many sites on one server, a control panel on a VPS or cloud server gives more control, with more responsibility.
Hosting control panel
Why choose it
- One dashboard for sites, WordPress, email, DNS and databases
- Updates and backups follow one routine for every site
Best when
- You host client sites, or several of your own, on a VPS or cloud server
- You, or someone on your team, administers servers
Watch for
- It is management software: you still need a server or hosting plan
- Editions and licences differ: check what covers your needs
Full decision detail
Why it helps
- One dashboard for sites, WordPress, email, DNS and databases
- Updates and backups can follow the same routine for every site
Fits when
- You host sites for clients, or run several sites of your own on a VPS or cloud server
- You want one consistent way to update, back up and manage every site
- You, or someone on your team, administers servers
Watch for
- A control panel is management software: you still need a server or a hosting plan to run it on
- Editions and licences differ, so check which one covers what you need
- Ask how sites are isolated from one another and how a site can be handed to a client
A control panel that manages websites, WordPress, email, DNS and databases from one dashboard, running on a server or hosting plan that you or a host provide.
A hosting control panel is management software, not hosting. It runs on a server or hosting plan and gives you one place to manage websites, WordPress installs, email, DNS, databases and security settings. It suits people who run their own servers or look after many client sites, and who want routine tasks such as updates and backups to follow the same pattern everywhere.
It does not make a weak server fast or secure by itself, and it adds a licence cost on top of the server.
When you may need more. If you do not want to administer servers at all, managed multi-site hosting is usually the simpler route.
Running applications, internal tools or automation
Some business software is not a website: an internal tool the team uses every day, a customer portal, a database, a scheduled job, or an automation that has to keep running when nobody is watching. Each workload needs somewhere to run, with the right operating system, enough memory and storage, and a way to be backed up and updated. The decision is less about brand than about control: who chooses the software, who patches it, and what happens when it fails.
More about this context
Some business software is not a website: an internal tool the team uses every day, a customer portal, a database, a scheduled job, an integration that moves data between systems, or an automation that has to keep running when nobody is watching. Each workload needs somewhere to run, with the right operating system, enough memory and storage, and a way to be backed up and updated.
Many businesses reach this point when the software they need to run no longer fits a standard plan, and they choose between a server they run themselves and a platform that runs the server for them. The decision is less about brand than about control: who chooses the software, who patches it, and what happens when it fails.
How the paths differ
The options sit on a spectrum of how much you manage yourself. A cloud server, often called a VPS, gives you your own slice of a machine and full control, and you run it. Storage-oriented and Windows servers are variations on the same idea for particular workloads. At the other end, managed application hosting runs the servers and the runtime for you and you deploy the application. Self-hosted automation is a specific workload that many businesses run on a cloud server.
Supporting detail
Questions to ask yourself. 5 questions to settle first
- Who will keep the server updated, secured and backed up?
- Which operating system does the software need?
- How much storage will the data need, and how fast must it be?
- Does the work have to run continuously?
- Do you want to manage a server at all, or have a provider run it?
Why this decision matters. What is at stake
Running your own software means deciding who looks after it. A server gives you the freedom to install what you need and puts the work on you: security updates, backups, monitoring, and recovery if something breaks. A platform that runs the servers takes that work back, but limits what you can deploy. The wrong level either leaves you stuck behind a platform’s limits or leaves a critical tool running on a machine nobody is looking after.
Operating system and storage are the other early decisions. Some business software only runs on Windows. Some workloads need large amounts of disk rather than speed. Some need neither and just a small, steady server. Settling these first keeps the shortlist short.
Before choosing. A short checklist
- Decide who is responsible for updates, security settings and backups, and write it down
- Check which operating system your software needs, and any licence cost on top of the server
- Estimate storage and memory for the first year, not only the first month
- Ask what happens if the server fails: snapshots, backups and how quickly you can restore
- If the application is business-critical, decide who is alerted when it stops
Want the full background? How the common hosting models compare
Choose the path that fits
Select a path to see why it fits and what to watch for.
Self-managed cloud server
A cloud server (VPS) you configure and run yourself, with resources of its own.
Best fit
- Internal tools and databases
- Comfortable managing a server
Main thing to check
Updates, security and backups are yours
Storage-oriented server
A cloud server where disk capacity is the main feature.
Best fit
- Backups and archives
- File-sync services
Main thing to check
Not for very fast disk workloads
Windows server with remote access
A cloud server with Windows Server installed, reached by remote desktop.
Best fit
- Windows-only applications
- A remote Windows desktop
Main thing to check
Licence cost on top of the server
Managed application hosting
A platform where you deploy the application and the provider runs the servers and runtime.
Best fit
- Teams that deploy code
- No server administration
Main thing to check
Platform limits, and moving away
Self-hosted automation
Workflow automation you install and run on your own server.
Best fit
- Automations on infrastructure you control
Main thing to check
You handle updates, security and backups
Self-managed cloud server
Why choose it
- You choose the software, runtime and settings, instead of working within the limits of a shared hosting plan
- Applications, databases and automations get resources of their own
- It gives staging, development and automation work a place of its own
Best when
- You run an application, internal tool or service and need to choose its software and runtime
- You need a database, background jobs or an automation to run continuously on resources of its own
Watch for
- You manage the server: software updates, security settings and backups are your responsibility
Full decision detail
Why it helps
- You choose the software, runtime and settings, instead of working within the limits of a shared hosting plan
- Applications, databases and automations get resources of their own
- It gives staging, development and automation work a place of its own
Fits when
- You run an application, internal tool or service and need to choose its software and runtime
- You need a database, background jobs or an automation to run continuously on resources of its own
- You, or someone on your team, is comfortable managing a server
Watch for
- You manage the server: software updates, security settings and backups are your responsibility
A cloud server, often called a VPS (virtual private server), gives you your own dedicated slice of a larger machine. You choose and configure the software, and you are responsible for keeping it updated and secure.
A cloud server is the general-purpose answer when you need to choose the software, the operating system and how it is configured. It suits internal tools, small databases, staging environments, scheduled jobs and automations, and it can host several things side by side. It does not come with someone looking after it: updates, security settings and backups are yours unless you add a management service.
When you may need more. If you would rather not administer a server at all, managed application hosting or a managed hosting plan removes that work, at the cost of some control. If the workload needs very fast disk or heavy computing, compare plans designed for that rather than a general-purpose size.
Storage-oriented server
Why choose it
- Large backups, archives and datasets get their own capacity instead of crowding a website's hosting plan
- It suits storage-heavy services such as file sync, where disk capacity matters more than raw speed
Best when
- You need to keep backups, archives or large datasets
- You run a file-sync or other storage-heavy service of your own
Watch for
- It is not the right choice for workloads that need very high disk performance
- As with any self-managed server, you look after the software and its security
Full decision detail
Why it helps
- Large backups, archives and datasets get their own capacity instead of crowding a website's hosting plan
- It suits storage-heavy services such as file sync, where disk capacity matters more than raw speed
Fits when
- You need to keep backups, archives or large datasets
- You run a file-sync or other storage-heavy service of your own
- Your workload does not depend on very fast disk performance
Watch for
- It is not the right choice for workloads that need very high disk performance
- As with any self-managed server, you look after the software and its security
A cloud server where disk capacity is the main feature. It suits workloads that read and write a lot of data but do not depend on very fast disk performance.
A storage-oriented server puts disk capacity first. It makes sense for backups, archives, large file collections and file-sync services, where how much you can keep matters more than how fast it responds.
When you may need more. If the application reads and writes data constantly and needs fast disk, a storage-oriented plan is the wrong shape; look at a general-purpose server instead.
Windows server with remote access
Why choose it
- Windows-only applications stay available without tying up a desk machine
- A remote or mixed-device team can reach the same Windows environment from anywhere
- It gives .NET and ASP.NET workloads a Windows home
Best when
- You depend on Windows-only business applications
- Your team needs a remote Windows desktop
Watch for
- Windows servers carry a licence cost on top of the server itself
- Unless you add management, you look after the server yourself
Full decision detail
Why it helps
- Windows-only applications stay available without tying up a desk machine
- A remote or mixed-device team can reach the same Windows environment from anywhere
- It gives .NET and ASP.NET workloads a Windows home
Fits when
- You depend on Windows-only business applications
- Your team needs a remote Windows desktop
- You host .NET or ASP.NET applications
Watch for
- Windows servers carry a licence cost on top of the server itself
- Unless you add management, you look after the server yourself
A cloud server with Windows Server installed. You connect to it remotely and use it like a Windows computer that is always on.
Some business software only runs on Windows. A Windows server gives you that environment in the cloud, reached by remote desktop, so a remote or mixed-device team can use the same application without a dedicated office machine. A Windows licence usually adds to the cost, and the server is still yours to maintain unless you add management.
When you may need more. If the software also exists for Linux or as a hosted service, those can avoid the licence cost and some of the administration.
Managed application hosting
Why choose it
- You ship the application without administering servers
Best when
- Your team is comfortable deploying code but not running servers
- You want the provider to handle scaling and upkeep of the runtime
Watch for
- You work within the platform’s supported languages, limits and pricing model
- Moving away can mean reworking how the application is deployed
Full decision detail
Why it helps
- You ship the application without administering servers
Fits when
- Your team is comfortable deploying code but not running servers
- You want the provider to handle scaling and upkeep of the runtime
Watch for
- You work within the platform’s supported languages, limits and pricing model
- Moving away can mean reworking how the application is deployed
A platform where you deploy your application and the provider runs the servers and the runtime.
Managed application hosting is for teams that can deploy their own code but would rather not administer the servers underneath. The provider runs the infrastructure and the runtime; you push the application. It reduces the maintenance load and usually scales more easily, in exchange for working within what the platform supports.
When you may need more. If you need a particular operating system, unusual software or full control of the environment, a cloud server is the more flexible route.
Self-hosted automation
Best when
- You want automations to run on infrastructure you control
Watch for
- You are responsible for updates, security and backups
Full decision detail
Fits when
- You want automations to run on infrastructure you control
Watch for
- You are responsible for updates, security and backups
Workflow automation that you install and run on your own server.
Compare the main paths
Show the comparison. The paths side by side
| What to look at | Cloud server (VPS) | Storage server | Windows server | Managed application hosting |
|---|---|---|---|---|
| Who runs it | You manage the server | You look after the software and its security | You, unless you add management | The provider runs servers and runtime |
| Best suited to | Custom applications, databases, jobs and staging | Backups, archives and large file collections | Windows-only business applications | Teams that deploy code but not servers |
| Main thing to check | Updates, security settings and backups are yours | Not for workloads that need very high disk performance | A Windows licence adds to the cost | Supported languages, limits and pricing; moving away |
See full comparison
| What to look at | Cloud server (VPS) | Storage server | Windows server | Managed application hosting |
|---|---|---|---|---|
| What it gives you | Software, runtime and settings of your choice | Disk capacity for backups, archives and datasets | Windows-only applications stay available | Ship the application without administering servers |
Want to know what sits behind each option? See how we evaluate hosting