It's not a big deal, but I find it annoying when people call something an OS when it's not an operating system. Like how xfinity has their "Entertainment Operating System" or whatever it is.
i can't count the number of products i've worked on or adjacent to that have gained some traction, started to scale... and hit a brick wall when wanting to access the enterprise market. far too often, these projects end up stopping most core feature work to add hacky versions of whatever's required to close that enterprise sales gap. they slow velocity while incurring tech debt.<p>a SaaS product that offers some developer-friendly ways to drop these capabilities into your system could be a huge win for companies at that inflection point.
I love the idea, and can definitely see the need.<p><i>But</i> I always come to the same question with services that provide auth and user management: You pay a lot of money for someone _else_ to own critical information about your customers. What happens if you want to move away and use a different/your own/your customers own service?<p>Your customer data (at least login) lives in WorkOS' database.
How do you get it out? How much does that cost? Are there contractual guarantees around that?<p>The same goes for your customers integration points. If the customer has to do any setup to integrate WorkOs for your app then moving away would involve them making changes. Not necessarily an easy thing to manage.<p>Not to be negative: I'd be happy to hear that WorkOS have great processes and guarantees around this.
Apologies if not the right place for this feedback, but the careers page does not work properly on Firefox 100/Linux - clicking any opening does nothing.<p>I work heavily with enterprise products. In my experience, when you're selling an enterprise-ready product it's a good idea to QA all public-facing code, even sections of a public website.<p>This is because I have found many enterprise customers are more interested in maintenance (which can be pre-assessed by looking at support and QA experiences) than they are the actual product.
Anyone know how this compares to Auth0? I like Auth0 because it's free for up to 7K active users. WorkOS seems much more expensive out of the gate ($49 per "connection"?).
I applaud WorkOS for the idea (even if I also hate the name). The sheer amount of externally developed apps that don't manage to authenticate to our IdP is staggering. I've had a dozen calls with developer teams, walking them step by step through the OIDC flow and they still can't manage to implement it.<p>I fail to understand why this is so hard for so many companies. It's really not rocket science.
The signup page mentions using Slack for OAuth, but I don't see that option when I'm trying to set up an SSO integration. I wonder if that's coming or no long available?