Hacker News new | ask | show | jobs
by rad_gruchalski 479 days ago
Running my own keycloak or another ory hydra is a boring task. Locking SSO behind some arbitrary scale and raked up price takes sales away from you. It’s a matter of perspective.
1 comments

> Running my own keycloak or another ory hydra is a boring task.

Simply running keycloak is not sufficient for SSO.

An SSO implementation may take months of dev time (i.e. $50k, minimum, considering cost of dev hours spent on it, and opportunity cost of not having those devs putting those hours into features).

And after you have done that, it remains an expensive feature - it's a high-touch feature that will eat product support time like you wouldn't believe.

Outsourcing this is still the cheapest option, and it still costs more than the product itself in many cases.

I don’t understand your point. My question is: if the service provider offers SSO as an additional feature, why limit it to certain size of a client? Their service supports it. Why cannot my two persons company enable this feature? My two persons company can run my own keycloak and use it as an OAuth provider in your product all right. If you need months of dev time to enable SSO on my account then say that upfront because I will certainly find a different service provider because you clearly don’t know what you’re doing.
> If you need months of dev time to enable SSO on my account then say that upfront because I will certainly find a different service provider because you clearly don’t know what you’re doing.

If you could do that, you would. The point is that SSO is high-touch and high-maintenance, and the price reflects that.

If it is as cheap you appear to think so, you'll make a killing offering SSO for businesses and undercutting the current providers by (maybe) 50%.

I don't think you are doing that. Maybe I am wrong, but if you are right you're leaving easy money on the table.