The reason a lot of companies charge extra for SSO is because it is a support nightmare. Most users can't tell the difference between "my SSO provider is broken" and "your service is broken" so they always blame the service, who now has to either tell the customer "talk to your SSO provider", which of course they don't like, or having to diagnose and fix SSO problems.
I agree that it should be a core feature, but I sympathize with companies that need to charge extra for it.
WorkOS makes adding SAML to your app incredibly easy and fast. We're powering Vercel, Planetscale, Webflow, Loom, and hundreds of others. Pricing is transparent and scales as you grow. And you don't need to talk to a sales rep. ;)
What? That's such absolute nonsense. Compared to managing your users passwords? Bah! No way is supporting saml that hard. It's. Library, and config. Users usually find out pretty quick when thier idp is down.
Plugging in my startup BoxyHQ here. This is the reason why we open sourced our SAML integration - https://github.com/boxyhq/jackson, it should be commodity.
Yes, but SSO is a very upfront integration that blocks all access to app. Most other integrations only break a piece of the app or are in the background. And lots of companies charge extra for those integrations too.
I find this hard to believe, setting up SSO was a piece of cake with Github. Sure you have some issues during the setup, but once it’s there it never changes.
Then again, Github also chargea you $20/month instead of $4/month if you want SSO in a small org, but it’s possible.
I agree that it should be a core feature, but I sympathize with companies that need to charge extra for it.