Live data from Hacker News

Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning

news.ycombinator.com

31–40 of 45 posts

Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning

#31
post #3

That's very good and any ISO 270001 certified small-medium company would need that. But it would be better to have stand alone web interface and not only relay on Slack.

Organisations that don’t use Slack aside, driving this from Slack is a real benefit in my experience.

A system like this lives and dies on the team actually using it, and by allowing them to drive it from where they already are (Slack), we’ve found the team are actually using it and don’t have many complaints about the workflows either.

Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning

#35
post #23

Do you plan to integrate with SSO providers or become one? This is cool, but seems like kind of a limited market because why would I want to maintain this information in two places (AccessOwl and my SSO provider).

Currently AccessOwl works well with "Sign in with Google". More to come. We don't plan to be come an own SSO provider as we believe authentication is solved good enough. But setting the right permissions for a user account is not. So you SSO provider does not have information which permission somebody has only that somebody has access to an app. That's we do differently basically.

When do you plan on implementing Office365 / Azure SSO?

I would ditch Okta tomorrow and throw money at you. One of the reasons I stay with Okta is their ability to automatically provision accounts with SaaS providers. It's not 100%, but it's more than 80% of the apps we use have integration with them and seem to provision/de-provision well.

Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning

#36
post #35

Earlier quoted context omitted.

Currently AccessOwl works well with "Sign in with Google". More to come. We don't plan to be come an own SSO provider as we believe authentication is solved good enough. But setting the right permissions for a user account is not. So you SSO provider does not have information which permission somebody has only that somebody has access to an app. That's we do differently basically.

When do you plan on implementing Office365 / Azure SSO? I would ditch Okta tomorrow and throw money at you. One of the reasons I stay with Okta is their ability to automatically provision accounts with SaaS providers. It's not 100%, but it's more than 80% of the apps we use have integration with them and seem to provision/de-provision well.

In regards to de-provisioning we are not relying on a SSO provider. The SSO provider plays a bigger role for us when onboarding an organization to read out what applications have been used by whom.

Would love to understand your case better. Are you using Azure SSO and Okta SSO in parallel? Without knowing the specifics of your tool landscape I believe we can help you there. Here is my calendly in case you want to share more details: https://calendly.com/accessowl/30-minutes-pdt

Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning

#37
Congratulations on the launch. This is great - I had started to feel the pinch of provisioning de-provisioning 2-3 years ago and wrote scripts for ~10 SaaS applications. Worked great until we started to get more and more SaaS apps and there was a day when I spent more time writing script for the tool rather than for the actual product of our company. Ditched the tool the next day.

Was planning to open source the tool but didn't really get the time then - great to see you guys solving it well! Congratulations!!

Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning

#39

Congratulations on the launch. This is great - I had started to feel the pinch of provisioning de-provisioning 2-3 years ago and wrote scripts for ~10 SaaS applications. Worked great until we started to get more and more SaaS apps and there was a day when I spent more time writing script for the tool rather than for the actual product of our company. Ditched the tool the next day. Was planning to open source the tool…

Thanks! We can really relate to that. Would love to hear more about what tools you did that for and what your experience were. Hit us up if you are open to chat!

Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning

#40

Funny coincidence, the logo is very similar to a convenience store we have in Australia: https://nightowl.com.au/

Haha true. We realized after designing it ourselves that there are lots of owl logos out there!
Post reply on HN