6 ms·
This pops up on HN about once a year, and it's worth calling out that the SSO tax has mostly nothing to do with technology or with support costs and mostly ever
by tptacek 1y ago
This pops up on HN about once a year, and it's worth calling out that the SSO tax has mostly nothing to do with technology or with support costs and mostly everything to do with market segmentation. One of the clearest segmentation signals you get is that bigger, less price-sensitive customers all require SSO (because their SOC2 attestations require it).
You can get irritated about pricing systems that soak price-insensitive customers, but remember that the big price-insensitive customers pay for the price-sensitive customers, which is why this kind of segmentation is practically universal.
Previously, on this, from me:
https://news.ycombinator.com/item?id=29892664 https://news.ycombinator.com/item?id=29892664
- cubefox 1y agoSimilar reason why there is a big price difference between DVDs and Blu-rays, and why DVDs still exist in the first place.
- RedShift1 1y agoThey still make new DVD's?
- TylerE 1y agoAnd they still outsell Blu-ray. It’s mostly lots and lots of kids tv. Kids don’t know what 480p means and parents just want discs that are cheaper and more resistant to damage.
- bombcar 1y agoExactly this - and sometimes they don't even bother with two SKUs and give you both in the same container for the DVD price. A surprising percentage of the population cannot tell a DVD from a Blu-ray in motion at home, especially if their TV does upscaling.
- TylerE 1y agoOf course physical media as a whole is still way down. Streaming outearns physical by a lot. All physical media is less than half what just blu ray was 10 years ago.
- cubefox 1y agoYes, so they can cover the price sensitive customers, and charge a higher price for Blu-rays for the quality sensitive customers.
- ghostpepper 1y agoshouldn't every new company be using SSO for everything in 2025 and beyond? how long before this no longer becomes a good signal?
- mathattack 1y agoYes - it's an enterprise versus SMB distinction that doesn't require asking questions like "What's your revenue?" in the qualification. Enterprises need it. SMBs don't.
- ryanisnan 1y agoCan you clarify, are you suggesting that the bills footed by large orgs that require SSO are paying the bills for these features?
- 0cf8612b2e1e 1y agoI think the implication is that without a few whale customers, the minimum price would be significantly higher for everyone. The SSO whales subsidize everyone else.
- bryanrasmussen 1y agoI sort of feel that the way most software pricing works is that it is the big customers who pay for features in everything and the small customers get brought along for the ride, in short I think it's the same as SSO for basically all functionality.
- trollied 1y agoYes, your 2 seat small business isn't paying the bills.
- jaggederest 1y agoIt's true both in the micro sense ("We wouldn't have developed the headache that is SSO without a cornerstone customer demanding it and paying $XXXk"), and in the macro sense ("Our business would not be a going concern without the significant revenue provided by enterprise customers")
- ryanisnan 1y agoInteresting. I wouldn't have thought that running an SSO integration is that painful. I've done it before, albeit for a single enterprise client, and while annoying at first, after delivery was just like another feature.
- jaggederest 1y ago
- Aurornis 1y ago> but remember that the big price-insensitive customers pay for the price-sensitive customers The fallacy is thinking that the alternative is for everyone to pay the lower price and get the enterprise features. In reality, without market segmentation a singular price for everyone would fall much closer to the enterprise price than the non-enterprise price. You can call it an SSO tax, but it would be equally correct to refer to the lower price as the non-corporate discount.
- cj 1y agoAre you saying companies should provide a discount for not using SSO? Or charge everyone the enterprise price to remove segmentation altogether? Edit: I think I see what you’re saying. Although you’d likely welcome the same criticism if you refer to it as the non-corporate discount.
- TylerE 1y agoWhy not? Just like some companies offer discount plans that come with no/very limited tech support, and others charge 10 or 20x for the same product bundled with a high level of support.
- wkat4242 1y agoMost of the big players like Microsoft charge enterprise customers for support on top of everything else. And this "premium support" still sucks. Microsoft outsources to Accenture who then outsource again to some random dopey small companies in the middle East so you get calls in the middle of the night from Qatar by someone who has no more knowledge than what the docs say. Which you've already read yourself otherwise you wouldn't have gone through the hassle of logging a ticket. Because outsourcing causes barriers between the people who built the thing and the people who support it. In most of these cases we either give up because the support is so useless, or someone high up calls Microsoft and gets the case escalated away from Accenture to someone in Microsoft who actually knows something. Personally if I were a CIO I would really be pissed at having to pay for this kind of "support". But yeah these guys rub shoulders with Microsoft all the time who tell them it's all amazing.
- zoeysmithe 1y agoI think this is overly complimentary to big business and what's essentially predatory pricing. The reality is you can't just carve out on feature and say "we pay for this." I mean that's true of a lot of things. The big revenue generators pay for a lot of things, but how things are billed is important. Remember, not to long ago people paid for Netscape, but now its laughable to pay for a browser. Its arbitrary to have this 'buffet' mentality and seems purposely shaming towards people who rightfully complain about ridiculous pricing structures like this. I'm also skeptical that SSO costs vendors money. Maintaining and supporting an authentication database is a huge expense. For every SSO client, its one less Adobe or whatever account that needs to be hosted. Less helpdesk tickets about password resets, etc. SSO tends to be once and done. Hosting millions of accounts and being the sign-on provider for them is not 'once and done.' Lastly, a lot of orgs don't do this. A lot arent SOC2. That means they'll just use whatever account the vendor supplies, and most likely without MFA, but their SSO would have provided that, thus making everyone more vulnerable. This is a great example of how exec salaries and stock buybacks and other things have priority over security because security is seen as a cost-center and without litigation or law, stuff like this becomes the norm. Oh and now there's one more source of passwords out there and another potential hack. This is just greed and predatory. Its not the wonderful largess of big companies. It fact, its quite the opposite.
- viraptor 1y ago> Less helpdesk tickets about password resets, etc. Pretty much everyone knows the password reset flow these days. Even if they do manage to lose access to everything somehow, the process to restore is mostly standard. On the other hand, SSO issues are long, annoying, and involve engineers rather than first level support. Source: my weeks long support tickets with Okta.
- Analemma_ 1y ago> I'm also skeptical that SSO costs vendors money Sane SSO from clients with clean setups doesn’t cost vendors much money. But take it from someone who has done this work: that’s rarely the case for the megacorps who want SSO integration. They tend to have horrifying AD/Oauth monstrosities, with back-compat requirements that will break your mind and sysadmins of questionable competence. These require lots of bespoke code and lots of meetings— meaning, lots of man-hours that senior ICs are not spending on product— to get right. That’s where a lot of the money for SSO is going, and you can’t exactly say “the price depends on how shit your backend is”, so it has to be enough to prepare for the worst.
- hackitup7 1y agoThank you for adding some sanity to this discussion – this is ultimately a matter of economics, and the R&D effort to add and maintain these features is not trivial.
- sparrish 1y agoI think you missed the point. The costs isn't insomuch R&D, it's in support. Users struggle with SSO and so we get tickets; techs answering tickets costs money.
- raxxorraxor 1y agoOn the other hand you have dev time that needs to save user passwords in a secure way. And this is the part of software that requirements maintenance and updates. Sure, other software needs that too. Some enterprises use their own identity provider and I would prefer that as well. Usually that is probably some windows ldap database that can easily be integrated, but there are a lot of other solutions as well.
- medlazik 1y agoSmall orgs don't need to be SOC2 to have client contracts that require SSO. This is absolute fucking evil behavior and this page shouldn't exist anymore in 2025.
- maxrmk 1y agoEvil feels strong? Small companies benefit from having the basic feature set subsidized by big cos. It's kind of hard for me to imagine a scenario where pricing of a saas product could be _evil_. you can just choose not to do business with them!
- akavi 1y agoIt's evil to sell a product for a price higher than you, personally, want to pay?
- mooreds 1y agoI like Patio11's characterization[0]: > The right way to think of the "SSO tax" (where companies charge extra for security features) is "You are being offered a dual use product backed by a strong engineering team for far less than it would otherwise cost, with sophisticated enterprises picking up the slack." That said, TLS/SSL used to be the preserve of the enterprise too (or at least the ecommerce site). There are lots of free options, including 3rd party servers and libraries. I'm hoping eventually SSO will be, if not in free versions, at least not isolated to enterprise plans. 0: https://x.com/patio11/status/1481293027331440640 https://x.com/patio11/status/1481293027331440640
- maxwellg 1y agoMany "softer" forms of SSO have trickled down too. Google + Microsoft OAuth are ubiquitous today without any upchage. OAuth from a Google Workspace account managed by an IT admin has many of the same security guarantees as SAML or OIDC from a Google Workspace account, at least for a small player. There are some sketches like https://easie.dev/ https://easie.dev/ that explore this further.
- jedberg 1y ago> and it's worth calling out that the SSO tax has mostly nothing to do with technology or with support costs I'm surprised this is at the top. My experience, and the experience of nearly all the commenters below, is that SSO is by far the biggest support burden they have. SSO costs extra because it costs extra to support them. Market segmentation is a nice side effect though.
- erazor42 1y agoAgree, I have implemented a few provider and every time they implemented their own interpretation of the spec. In the end you end up checking each provider to make sure everything works as expected.
- akanet 1y agoI ran a company that did price segmentation on SSO, and it's the other way around. The burden of supporting the buggy piece of crap that is SAML SSO is the cost of the privilege of being able to perform such sharp segmentation.
- jedberg 1y agoExcept the segmentation isn't all that sharp. With Google domains et al almost everyone wants SSO now, even the smallest of companies.
- tptacek 1y agoIt's not that small companies don't want it, it's that they're capable of not getting it. Larger companies aren't: one thing their SOC2 auditors will actually be able to evaluate is whether all their vendors do SSO.
- behringer 1y agoIt's segmented even in OSS software to the point where it's the first thing I have to check when deciding what software is going to run on my home server.
- 1y ago
- sunshowers 1y agoWhat are your normative views on this topic?
- tptacek 1y agoThat there's nothing magic about security to exempt it from economics.
- sunshowers 1y agoThat's not a normative view (the hint is the "there's" which is a contraction of "there is"). A normative view would use the word should or ought.
- tptacek 1y agoPretty sure I meant what I said. https://hn.algolia.com/?dateRange=all&page=0&prefix=false&query=normative%20by%3Atptacek&sort=byDate&type=comment https://hn.algolia.com/?dateRange=all&page=0&prefix=false&qu...
- drdeca 1y agoDo you mean that you don't have a normative view on it, or that the thing you said was a normative view, or something else?
- tptacek 1y agoIf you want to fit the word "should" in there somewhere, you can. I think SSO is important, and it would be one of the first 3 things I would stand up at any new shop I went to, but I can think of more important security things that nobody really thinks should be equally distributed across companies.
- sunshowers 1y agoOkay: "That there should be nothing magic about security to exempt it from economics." I disagree quite strongly with this! I think a reasonable premium for SSO support costs is fine but severe price discrimination/bundling based on security features is unethical. That is because security issues have large externalities on uninvolved parties.
- vosper 1y ago> mostly nothing to do with technology or with support costs Support costs aren't zero though. I work for a company with a lot of corporate customers and we get loads of SSO support tickets. People are always misreading the docs, (mis)configuring things against our recommendations, migrating systems, merging systems (due to acquisition etc)...
- agoodusername63 1y agoThis is how I've come to accept it too And honestly when I really really want SSO anyways, I can bolt on vouch proxy for free
- benmccann 1y agoWouldn't vouch proxy only work with self hosted apps? How would you use it with a SaaS app?
- limagnolia 1y agoI run a very small business, SSO is still very high up on my feature priority list, and I have passed on software/services I would have otherwise used for competitors that offered SSO at a lower entry-point.
- magicalhippo 1y agoWe have Github Enterprise licenses for all our developers. All 7 of them. Similar with other services. Just because of SSO, as we don't have the manpower to handle the compliance stuff our customers demands otherwise.
- Spooky23 1y agoI’d take it a step further and say it helps the customer filter vendors too small to be worth the trouble. At work, I can’t afford free.
- andy99 1y agoAlso, enterprise customers are way more work, the sales cycle is longer, the compliance and onboarding stuff takes more time. There's a very legitimate case for building that into one's pricing, and it's really the same reason these companies appear price insensitive. If they had people lining up to give them a better price, they'd presumably take it.
- 3acctforcom 1y agoSecurity is an optional feature? You must be a sales executive...
- mixmastamyk 1y agoSSO doesn't add security, it enables bulk management of accounts. Which only affects security in an indirect way.
- raxxorraxor 1y agoTechnically it doesn't add security, but I think the recommendation for SSO stems from the reality that peoples behavior gets worse if they have to maintain more accounts. And if they use the same password, the least secure system affects the others in a classical setup.
- basch 1y agothe human side of security, the one thats more often breached.
- themafia 1y ago> but remember that the big price-insensitive customers pay for the price-sensitive customers You mean they more than make up for the loss of those customers? What is the underlying cost on the service? Isn't the profit margin here absolutely absurd since the underlying cost to the vendor is basically zero once their implementation is written?
- croes 1y agoSo the price insensitive get the security the price sensitive can’t afford. That’s the same logic some use to explain why university fees have to exist opposed to being tax funded, because otherwise the poorer would finance the education of the wealthy totally ignoring that higher costs are the barrier that makes less likely that the poorer can study in the first place.
- tptacek 1y agoYou can moralize it all you want. All I'm saying is: the alternative to the SSO tax isn't that everyone gets the features they want at the price they want: it's that the price of the low-end product goes up and the price of the high-end product goes down. If you care about distributional effects, that seems like a step backwards.
- croes 1y agoThat's not necessarily true. You make it sound like there are only two group. Big Enterprise with SSO and small without but there are also those small who need SSO and can't afford. So the overall revenue and profit could be higher if they offer the SSO at the same price as without
- raxxorraxor 1y agoI don't think SOC2 specifically demands SSO and just encourages it. Probably good, since such security mandates often age badly, even such a broad concept like SSO could fall victim. And there is always that one tool that isn't integrated, ironically inhouse software often neglects it. But otherwise I believe you are very on point. Although from a developer perspective perhaps it should be segmented the other way around. If I can outsource to identity providers, I have delegated a lot of risk and work. And while the initial implementation might be a bit more cumbersome, in the long run it certainly is less development intensive than providing a complete user management interface. And maintenance for a few keys is easier than user management, even if you still have to do some of that. Perhaps not using SSO should be marketed as some privacy focused benefit, which is more expensive.
- tptacek 1y agoIt doesn't specifically demand it, but (1) SSO is the simplest way to knock out a huge swath of control objectives, and (2) once you attest to a control like SSO, it's extremely annoying to pull that back. If you hire security/compliance/engineering management to take you through SOC2 and they don't set up and attest to SSO, they're bad at their job.
- basch 1y agoI hate this argument. The local PTA or kids sports league or boutique needs sso as much or more than an enterprise. These may be organizations without an IT department at all, handed down from family to family, where they are transferring a database of gmail passwords. I know gsuite and office365 have free tiers for charity, but the amount of small businesses with a gmail address is staggering. SSO should be a feature for the family as well. A parent should be able to pull up a dashboard and see where all their family gmail accounts are authorized to use as a login from one screen without scrolling. The overall sentiment that SSO creates a support burden is true, but a separate problem that should also be fixed. it _shouldnt_ be complicated for a small team with ten accounts to control group login information, revoke access, lock accounts.
- tptacek 1y agoAs someone who does a lot of local organizing, I really don't think getting SSO set up in this level of organization is a thing that happens enough to impact pricing decisions at Atlassian. Even if SSO was completely free everywhere, most of these kinds of places would still just be using a single shared account with a shared password. Stuff costs money! That's really all there is to the analysis. You can demand that companies not price-segregate customers, but then all you're really saying is that there's no account that the local PTA can afford, because you're demanding that vendors raise prices on the low end and and drop them for customers like Apple and Ford.