What SaaS is: software as a service by NIST's definition, real business examples, SaaS vs in-house software, and when a subscription pays off.

SaaS is short for software as a service. Instead of buying a licence, installing a program on every computer and keeping it patched yourself, a business pays a subscription and uses a ready-made application through a browser or a mobile app. The servers, the updates, the infrastructure backups and the ongoing development of the software sit with the provider.
The most precise description comes from the US standards body NIST, which has been the industry's reference point for over a decade. By its definition, SaaS is "the capability provided to the consumer is to use the provider's applications running on a cloud infrastructure" (NIST SP 800-145). The customer doesn't manage the servers, the operating system or the application itself — at most, the settings the application exposes to users.
This hub answers the four questions that come up once a business starts using SaaS deliberately, or starts thinking about building its own product in that model.
SaaS — four questions, four articles
Digital Vantage SaaS section map, September 2026
Map of the SaaS section: four questions and four articles. First: what the cloud is and where SaaS sits within it — IaaS, PaaS, SaaS, public and private cloud — the cloud computing article. Second: who's responsible for what — the processor contract, the Swiss reporting duty — the cloud data security article. Third: how to sell a product on subscription — freemium or trial, churn, MRR, LTV:CAC — the freemium article. Fourth: what product to build yourself — niche, MVP, pricing, first customers — micro-SaaS ideas.
Most businesses use SaaS before they ever stop to think about it. Webmail in a browser, an online office suite, shared drives for documents, invoicing and accounting software, a CRM system, a booking tool for appointments — all of that is SaaS.
Which categories do businesses adopt first? The pattern holds everywhere: generic SaaS tools — e-mail, office software, file storage — come first, because they replace a use case that's already standard across almost any organisation. Database hosting and computing power for a business's own applications come much later, only once there's a genuine technical reason to move them out. In 2025, according to Eurostat, 52.7% of EU enterprises with at least 10 employees bought paid cloud services: 44.9% for e-mail, 37.8% for office software and 37.7% for file storage, against just 24.0% for database hosting and 14.9% for computing power for a business's own applications (Eurostat, isoc_cicce_use) — EU figures, useful as an illustration of the pattern rather than a measure of the Swiss market: no comparable official Swiss statistic exists for paid cloud services bought by businesses.
The difference isn't only where the program runs. It changes who does the work, and how you pay for it:
SaaS is one of three cloud service models — alongside IaaS, where you rent servers, and PaaS, where you rent a platform to run your own applications on. How they differ, and which layers stay on your side of the line, is what we cover in the cloud computing article. When it still makes sense to keep your own server in-house — and how to run the numbers over five years — we cover in the on-premise article.
SaaS wins where a business's process looks like the process at thousands of other businesses: e-mail, documents, invoices, calendars, a basic CRM. You're paying for a tool someone else has already built and refined across many customers, instead of building it from scratch.
It stops winning when the process is what makes the business different, when several SaaS tools have to be glued together by copying data by hand, or when the team's subscriptions, added up over several years, exceed the cost of a system of your own. How to make that call is what we cover in the custom software article.
A SaaS provider is responsible for its own infrastructure and application, but the data, the user accounts and who has access to what stay on the business's side. If personal data lives in the service, you also need a data processing agreement with the provider under Switzerland's Data Protection Act (nFADP) — and, in addition, under the GDPR if you offer services to people in the EU. What to check before you sign — from where the data is stored to how you get it back if you switch service — is covered in the cloud data security article. What a provider actually guarantees when it promises 99.9% availability, and how many minutes of downtime a month that really is, is what we break down in the SLA article.
We know the SaaS model from the other side too. DVN Links is our own product — a European link management platform with click analytics and QR codes. It works exactly as the NIST definition describes: a customer opens an account in a browser, creates links and watches the statistics, while the servers, updates and further development of the service sit with us. Data is stored on servers in the EU.

DVN Links — an example of a SaaS product
dvnlinks.pl/en, screenshot of 30 September 2026
It's also an example of SaaS as part of a bigger system. The site you're reading right now uses DVN Links through its API: when we publish an article, the content management system requests a short link for it automatically, and updates that link whenever the address changes. Nobody copies addresses by hand. That's what a typical SaaS integration with a company's own software looks like — a ready-made service does one thing well, and connects to the rest of the system through an API.
The SaaS model also works the other way round — as a business of your own. Five articles in this section deal with exactly that:
SaaS (software as a service) is software you use over the internet on a subscription, instead of buying it and installing it yourself. The servers, updates and ongoing development sit with the provider; you log in and work. Examples include webmail in a browser, an online office suite, invoicing software or a CRM system.
Usually, yes — it needs no server purchase and no administrator, and the starting cost is low. In the EU, according to Eurostat, in 2025 almost half of small businesses (49.3% of firms with 10–49 employees) bought paid cloud services — a European figure; no comparable official Swiss statistic exists. It's still worth adding up the subscription cost over several years, and checking how you'd get your data back if you switched provider.
In how many layers the provider maintains. With SaaS you get a ready-made application. With PaaS the provider maintains the platform, and you deploy your own application onto it. With IaaS you rent servers and maintain everything on them yourself. Details are in our cloud computing article.
The provider is responsible for the security of its own infrastructure and application, but the data, accounts and permissions stay with the business. If personal data is involved, you need a data processing agreement under Switzerland's nFADP — and, in addition, under Article 28 GDPR if you offer services to people in the EU. Before choosing a service, it's worth checking where the data is stored, the provider's certifications and how you export your data.
We'll help you compare ready-made services against custom-built software and work out what's cheaper over the long run.
What SaaS is: software as a service by NIST's definition, real business examples, SaaS vs in-house software, and when a subscription pays off.
Multi-tenant SaaS: single tenant vs multi-tenant, the silo/pool/bridge models, Row Level Security, Swiss data protection and choosing a model for an MVP.
On premise, your own server: the full cost beyond hardware, the end of Windows Server 2016 support, and when the cloud or VPS wins instead.
ARR, MRR, churn, NRR, LTV:CAC and Rule of 40: formulas from ChartMogul and Stripe, benchmarks with their sample size, and the traps that make SaaS metrics lie.
SLA meaning: how much downtime fits in 99.9%, how AWS, Microsoft and Google SLAs compare, SLO, RPO, RTO and 10 things to check before signing.
A SaaS application from MVP to subscription: the five building blocks, recurring payments in Switzerland, the legal minimum, costs and the DVN Links example.
Cloud computing by the NIST definition: five traits, IaaS, PaaS and SaaS, public, private and hybrid cloud, and how businesses actually use the cloud.
35 micro-SaaS examples grouped by industry, a niche-scoring framework, a 30-day MVP plan, and Swiss VAT for selling abroad.
Cloud security explained: shared responsibility, the processor contract, US data transfers, Switzerland's Information Security Act and your cloud exit strategy.
Freemium, trial without a card, or trial with a card: ChartMogul conversion data, time-to-value, churn, MRR, LTV:CAC and European cloud adoption from Eurostat.
Your Partner in Business, Digital Vantage Team
Digital Vantage team is a group of experienced professionals combining expertise in web development, software engineering, DevOps, UX/UI design and digital marketing. Together we carry out projects from concept to implementation - websites, e-commerce stores, dedicated applications and digital strategies. Our team combines years of experience from technology corporations with the flexibility and immediacy of working in a smaller, close-knit structure. We work in agile methodologies, focus on transparent communication and treat each project as if it were our own business. The strength of the team is the diversity of perspectives - from systems architecture and infrastructure, frontend and design, to SEO and content marketing strategy. As a result, the client receives a cohesive solution where technology, aesthetics and business goals go hand in hand.
Table of Contents · 6 sections · 5 minutes read
Rate this article

Multi-tenant SaaS: single tenant vs multi-tenant, the silo/pool/bridge models, Row Level Security, Swiss data protection and choosing a model for an MVP.

On premise, your own server: the full cost beyond hardware, the end of Windows Server 2016 support, and when the cloud or VPS wins instead.

ARR, MRR, churn, NRR, LTV:CAC and Rule of 40: formulas from ChartMogul and Stripe, benchmarks with their sample size, and the traps that make SaaS metrics lie.

SLA meaning: how much downtime fits in 99.9%, how AWS, Microsoft and Google SLAs compare, SLO, RPO, RTO and 10 things to check before signing.

A SaaS application from MVP to subscription: the five building blocks, recurring payments in Switzerland, the legal minimum, costs and the DVN Links example.

Cloud computing by the NIST definition: five traits, IaaS, PaaS and SaaS, public, private and hybrid cloud, and how businesses actually use the cloud.

35 micro-SaaS examples grouped by industry, a niche-scoring framework, a 30-day MVP plan, and Swiss VAT for selling abroad.

Cloud security explained: shared responsibility, the processor contract, US data transfers, Switzerland's Information Security Act and your cloud exit strategy.

Freemium, trial without a card, or trial with a card: ChartMogul conversion data, time-to-value, churn, MRR, LTV:CAC and European cloud adoption from Eurostat.