Home › SaaS Resources

SaaS Software or Installed Software? A Decision Aid

SaaS software is one of three common ways to get a business application. This page compares it with the other two and offers a short decision aid. It does not argue that one is better in general, because the right answer depends on your situation.

The three options

• SaaS. The vendor hosts and operates the software. You subscribe and use it in a browser.
• Installed software. You buy or license a program and run it on your own equipment. You apply updates yourself.
• Self-hosted software. You run an application on servers you rent or own, often open-source, and you operate it.

Who does the work

With SaaS, the vendor patches, backs up and monitors. With installed software, you do, or your IT provider does. With self-hosted software, you do the same plus you decide how to host it. Each choice moves work between you and someone else. If your time is scarce, SaaS usually saves it. If you have the skills and want control, the others offer more.

Where your data sits

SaaS stores your data on the vendor's systems, in places the vendor chooses within its terms. Installed and self-hosted options keep data under your control, which may matter when rules or contracts limit where information can go. Control also brings responsibility for security and backups.

What it costs

SaaS spreads cost over time and includes upkeep in the fee. Installed software may involve a larger upfront license and separate costs for support and upgrades. Self-hosted software may have no license fee but needs hosting and skilled time. Count the whole cost for a few years, including staff hours, rather than only the visible price.

Customization and control

Installed and self-hosted software can often be modified deeply. SaaS usually offers configuration and connections, but not changes to the underlying code. If your process is unusual, check how far configuration can go.

Working without a connection

Installed software can run offline. SaaS generally needs a connection. If staff work in places with poor service, that matters.

A decision aid

1. If you want minimal upkeep and a quick start, lean SaaS.
2. If rules require data to stay on your own equipment, lean installed or self-hosted.
3. If you need deep modification and have technical staff, consider self-hosted.
4. If your work must continue without a network, favor installed.
5. If you are unsure, trial a SaaS product while keeping your data exportable.

A website example

A website can be built with a hosted builder, a self-hosted content system, or custom code. The hosted builder asks the least of you. The self-hosted system gives control and asks for maintenance, security updates and backups. See the comparison pages on WordPress and website builders for how one vendor frames this choice.

When SaaS is not the right choice

When regulation, location, offline use or heavy customization rule it out, choose another model. When none of those apply, SaaS is often the simpler route.

Example: an accounting practice uses both

A small accounting practice has used an installed program for years. Updates are bought every year, installed on each computer, and sometimes break a customized report. The practice considers a hosted alternative. It lists what matters: keeping client files on its own systems because of an engagement agreement, working at client offices without a connection, and avoiding technical maintenance.

The list produces a mixed answer. The engagement agreement and offline work point to installed software for client files. The wish to avoid maintenance points to hosted tools for everything else, such as time tracking and invoicing. The practice ends up with both, and the decision aid helped because it separated the reasons.

Questions to settle before choosing

• Does any rule or contract limit where the data may sit?
• Who in the organization can patch and back up a system, and do they have time?
• How many people need access from outside the office?
• What happens to the work if the internet connection fails?
• Over a few years, which option costs less in total, including staff time?

Mixed arrangements and how to manage them

Many organizations end up with a mix of hosted, installed and self-hosted software. That is normal, but it needs care. Keep a list showing for each system where it runs, who maintains it, and how it is backed up. Make sure connections between systems are documented. And decide who is responsible when a problem crosses a boundary, such as an installed program that depends on a hosted service. A short, current diagram is worth more than a long document nobody reads.

Signals that your current setup is due for review

• Updates to an installed program are being skipped because they are a nuisance.
• Staff often work away from the office and struggle to reach the system.
• Backups depend on one person remembering them.
• A hosted tool is costing more each year than the problem it solves.
• A rule or contract has changed about where information may be kept.

Any of these is a good reason to look at the three options again, using the decision aid above.

Next steps

Read the definition of software as a service, the guide to what remains your job with hosted software, and the comparison with doing it yourself.

Updated October 2026