[sofixa]

Hard disagree. Scalability and reliability, and SSO[0] are basic features any piece of software should have. Even a one-person startup shouldn't have to accept a tool being down for a month or all of their data lost due to a fire in a datacenter. Charging extra for any of these is a very shitty business model.

0 - sso.tax

[donmcronald]

How much scalability does one person need? And no HA doesn’t mean “down for a month”. It means I have no issue with enduring a few hours of downtime here and there. And HA and backups aren’t even related, so...

[sofixa]

One person could still require significant capacity - imagine an API with flight info, and your one person SaaS that does some magic with it by getting the data real time for all flights around the world.

> And no HA doesn’t mean “down for a month”. It means I have no issue with enduring a few hours of downtime here and there

No HA means downtime is expected and frequent ( baring crazy luck, but let's not base business on hope). If your invoicing, or project management, or note taking or whatever SaaS is down and you need it now to do something for a client of yours, how many hours of downtime can you accept?

> And HA and backups aren’t even related, so...

You said scalability and reliability, good backups are a part of reliability. If a SaaS cheaps on backups and HA for small time clients like one-person companies or small startups, and then a fire burns it all ( but not entreprise customers, because their backups are replicated to another DC), is it OK because they were small?