SaaS
Software as a Service
Software you rent instead of own: the vendor hosts it, runs it, and charges a subscription, while customers just log in through a browser.
SaaS is a delivery and business model, not a technology. Instead of selling you a copy of the software to install and run yourself, the vendor hosts it, operates it, and gives you access over the web for a recurring fee. You log in, you use it, you never touch the servers. Salesforce, Slack, and Notion are SaaS. The customer rents capability rather than buying and maintaining software.
The defining technical trait is multi-tenancy: one running system serves many customers at once, with their data isolated from each other. That single choice shapes everything. You design for isolation and security between tenants, for deploying updates to everyone at once without breaking anyone, and for scaling as customers are added rather than shipping a new version once a year. It also changes operations, because the vendor now carries uptime, backups, and security as an ongoing responsibility, not the customer.
The business model is the other half. Revenue is a subscription, usually monthly or annual, which means the relationship does not end at the sale, it starts there. The metrics that matter become recurring revenue, churn, and the cost to serve each customer. Pricing usually ties to value or usage: per seat, per tier, or per volume. Get the pricing model wrong and a technically excellent product still loses money on every customer, so pricing is an architecture decision as much as a sales one.
We build SaaS products end to end, from the multi-tenant architecture to the web app customers log into. Polity is a SaaS product. The honest part founders underprice: the recurring model means you are signing up for permanent responsibility for uptime, security, and support, which is a real operating cost, not a one-time build.