The SSO part is a bit confusing since it sounds like the product is letting you download account and permissions data based on your own api key. It might be helpful if you clarify how you can help with the SSO portion of things.
In a similar vein, I’m confused by the messaging: “SSO is expensive” problem, the “access user data” problem, “centrally manage permissions” problem, and “automatic account provisioning/deprovisioning” problem.
The marketing seems to jumble those 4 problems into 1 problem when (at least to me) they’re 4 very distinct problems to solve.
That leaves me wondering which of those problems are you truly solving? All 4 or just a subset?
Fantastic feedback. Indeed these are distinctive problems. For instance, "SSO is expensive" seems to be the root cause for the "centrally manage permissions" and "automatic account provisioning/deprovisioning" problems. At least when we're not talking about enterprises.
OpenOwl tries to give transparency over the user permission data in your SaaS tools - independent whether you have SCIM APIs or not. It's read-only though. No automatic account provisioning here.
However, as some of these problems are very close to each other, it could make sense to solve them together. But that's not the intent for OpenOwl.
That's a good point. Indeed there is a technical focus on login flows at the moment as this seems like the hardest problem to solve. Adding API key flows makes definitely sense though!
