Funny coincidence, the logo is very similar to a convenience store we have in Australia: https://nightowl.com.au/
We see owls everywhere since that, kinda cool :-)
Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning
41–45 of 45 posts
Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning
#42Hello, this solves a real problem for me as a growing startup CTO (~70 people) still handling most account creation / removal manually. I couldn't find a list of your integrations on your website? Seems like it should be a top level menu entry!
Great to hear that this would solve a problem for you! Do you have somebody else helping you with account creation/removal or are you still doing it on your own? I agree that we need to put more work into our website and list all integrations there. But I guess most of the applications you use, we're covering already.
> But I guess most of the applications you use, we're covering already.
That seems like an unnecessarily bold statement when your landing page mentions +100 integrations
Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning
#43Earlier quoted context omitted.
Great to hear that this would solve a problem for you! Do you have somebody else helping you with account creation/removal or are you still doing it on your own? I agree that we need to put more work into our website and list all integrations there. But I guess most of the applications you use, we're covering already.
> But I guess most of the applications you use, we're covering already. That seems like an unnecessarily bold statement when your landing page mentions +100 integrations
You have a point here, indeed. What I mean is that we cover the "typical" apps many tech companies use. But yes, not everything is integrated yet.
Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning
#44Earlier quoted context omitted.
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 sha…
Scheduled for next week - thanks!
Re: Launch HN: AccessOwl (YC S22) – Automating SaaS Provisioning and Permissioning
#45Earlier quoted context omitted.
Great to hear that this would solve a problem for you! Do you have somebody else helping you with account creation/removal or are you still doing it on your own? I agree that we need to put more work into our website and list all integrations there. But I guess most of the applications you use, we're covering already.
> But I guess most of the applications you use, we're covering already. That seems like an unnecessarily bold statement when your landing page mentions +100 integrations
I think the statement was meant to be softer
“But I’m guessing we cover most of the applications you’d use”
I’ve read a couple other comments from them, and am pretty sure it’s a minor fluency thing. I’d give them the benefit of doubt :)