What Is SaaS? Software as a Service Explained

In a SaaS arrangement, the vendor operates one application and many customers use it, usually through a browser or an API. The customer does not own a copy of the software, does not manage servers, and does not apply patches. Payment repeats month by month or year by year for continued access, which is why the model is inseparable from an ongoing subscription. A definition is easy; the consequences are what matter. Recurring payment turns a product into an ongoing relationship, and the vendor's revenue depends on customers staying rather than on a single sale.

The clearest way to explain SaaS is to compare it with the model it replaced. A perpetual license sells the right to use a specific version indefinitely, typically for a large upfront fee plus optional maintenance. SaaS charges for access to a service the vendor hosts and continuously updates. The differences follow from that:

• Payment: recurring subscription versus a one-time license purchase.
• Delivery: reached over the network versus installed on customer hardware.
• Ownership: the vendor retains the software; the customer buys access.
• Updates: continuous and vendor-controlled versus periodic purchased upgrades.
• Data: usually held by the vendor, which creates data-protection and portability obligations.

The full comparison is covered in SaaS vs Licensed Software. Buyers weighing the two are really choosing between control and operational burden, which is the same trade-off that separates cloud from On-Premise vs Cloud Software.

SaaS sits at the top of a stack that is usually described in three layers, covered together in Cloud Service Models (IaaS, PaaS, SaaS). Infrastructure as a Service delivers raw compute, storage, and networking. Platform as a Service adds a managed runtime so developers deploy code without patching servers. SaaS delivers a finished application the customer simply uses. The layers are complements, not competitors: most SaaS vendors run on IaaS and PaaS underneath, buying infrastructure and platform services so they can focus on the application, their pricing, and their customer relationship.

Because payment repeats, the SaaS Business Model behaves differently from a one-time-sale business. Revenue recurs and compounds when retention is strong, and erodes when it is not. Operators track Monthly Recurring Revenue (MRR) as the core number, watch Churn Rate (SaaS) as the main threat, and measure customer lifetime value against acquisition cost to judge whether growth creates or consumes cash. The model's central identity is simple: recurring revenue equals paying customers multiplied by average price, and net growth is new plus expansion minus churn. A definition of SaaS that stops at "software in the cloud" misses the part that shapes every decision inside the company.

SaaS serves two broad customer types. Business-to-business products sell to organizations, where deals are fewer and larger and support expectations are higher; the split is examined in B2B SaaS vs B2C SaaS. Business-to-consumer products sell to individuals, rely on self-serve signup, and live on volume. A second axis describes market scope: horizontal products serve a function used across many industries, such as customer relationship management, while vertical products encode the workflows and compliance rules of one industry. Horizontal vs Vertical SaaS covers how those two positions compete. Most software categories today have both a horizontal incumbent and several vertical challengers.

The recurring fee is structured in a handful of familiar ways. A flat rate charges one price for full access. Per-seat pricing scales with the number of users. Tiered pricing packages features and limits into good, better, and best plans. Usage-based pricing charges for measured consumption such as API calls, tokens, or storage. Freemium offers a permanent free tier with paid upgrades above it. Many mature vendors land on a hybrid, pairing a base subscription with a usage or seat component. Each choice trades predictability against alignment with the value the customer receives, and the comparison is set out in SaaS Pricing Models.

The economics are driven by retention more than by any single sale. A customer who stays for years can justify a higher acquisition spend than a one-time buyer, so acquisition cost must be read against Customer Lifetime Value (LTV) through the LTV to CAC Ratio. The time required to earn acquisition cost back is the CAC Payback Period, and rising churn lengthens it. Expansion revenue from upgrades, added seats, and growing usage can lift Net Revenue Retention (NRR) above 100%, meaning the existing base grows even with no new customers. These ratios, not raw signup counts, tell an operator whether the business is healthy.

Most SaaS products are built on Multi-Tenant Architecture: one running instance of the application and its database serves many customers, called tenants, while keeping each tenant's data logically separate. The vendor maintains one codebase and deploys once, so the cost of serving each additional customer falls as the customer count grows. The trade-off is shared risk — a filtering bug or a noisy neighbor affects everyone — which is managed with isolation, quotas, and per-tenant resource accounting. Single-tenant deployments exist for large buyers who need maximum isolation or strict data residency, but they cost more to run.

On-premise software is installed on hardware the customer owns and runs inside its own data center. It allows deep customization and direct control over data locality, at the cost of operating, patching, and scaling the software itself. SaaS shifts that work to the vendor, which means adopting the vendor's release cadence and accepting that data sits on someone else's infrastructure. Neither is automatically cheaper or safer; the deciding factor is who can operate the controls consistently. Steady, high workloads can favor on-premise, while variable demand and small teams usually favor SaaS.

SaaS became the default delivery model for software because it aligns cost with use. The buyer avoids a large upfront purchase and converts capital spending into an operating expense that scales with the team. The vendor gains predictable revenue, a direct customer relationship, and the ability to ship improvements continuously instead of bundling them into paid upgrades. Those incentives pulled both sides in the same direction. The shift is visible across the wider value chain, where infrastructure and platform providers sell to application vendors, and application vendors own the customer.

A few beliefs about SaaS cause avoidable confusion:

• "SaaS just means cloud software." Cloud describes where software runs; SaaS describes how it is delivered and paid for. The two usually travel together but they are not synonyms.
• "SaaS is always cheaper." It usually lowers upfront cost, but total cost depends on utilization and how long the subscription runs.
• "The customer owns the data in the same way." With SaaS the vendor stores the data, so portability, export, and deletion terms matter and should be checked before committing.
• "Growth is just acquisition." In a subscription business, retention and expansion decide whether growth compounds or leaks away.

If you want the operational side next, continue with the benefits of SaaS, the types of SaaS software, the SaaS business model, and the deeper revenue models. Marketers building demand for these products should read SEO for SaaS.

What does SaaS stand for?

SaaS stands for Software as a Service, a model where a vendor hosts software and customers pay a recurring fee for access over the internet.

Is SaaS the same as cloud computing?

Not quite. Cloud computing is the broader idea of using someone else's infrastructure on demand; SaaS is the top layer of that stack, where the customer receives a finished application rather than raw servers or a platform.

What is the difference between SaaS and a perpetual license?

A perpetual license is a one-time purchase of the right to use a specific version. SaaS is a recurring subscription for continued access to a service the vendor hosts and keeps updated.

Do you own the software in a SaaS model?

No. The vendor retains ownership and the customer buys access. That is why data export, portability, and exit terms belong in every SaaS evaluation.

Why do SaaS companies care so much about churn?

Because recurring revenue only compounds if customers stay. Churn reduces lifetime value, extends the payback period, and caps growth, so it drives more of the business than any single sale.

This page is one node in the XKnow knowledge base, a linked set of notes on SEO and SaaS in Markdown and Obsidian. The vault connects the concepts above — the delivery model, the metrics, the pricing choices — so you can follow the system rather than read one page in isolation.

• How to Pronounce SaaS