Hey everyone,
I ran some Facebook ads and received some feedback from Reddit /r/startups. I decided it was enough validation to build it.
If you're like me, you've probably used Basecamp, GitHub, Heroku, HipChat, and many other apps on a daily basis. One of the things I found annoying was sending out invitations to all of these different apps. Onboarder solves this. When you need to invite someone new, type in their email (and GitHub username) and you're done. Onboarder handles the rest.
Better yet, when you need to remove access, you can do so with just one click.
I'm exploring opportunities to make this process even simpler. I definitely think it would be better with deeper integration. For a first version, I think it's pretty cool.
Thanks a lot for listening and I welcome any and all feedback.
I really don't mean to be a jerk, but this sounds like a terrible idea. Four places to send invites from? That's a first world problem, not a startup business opportunity.
Since when were first world problems not startup opportunities? It certainly doesn't sound like the next Google, but it could be a good side project that pays for his next vacation.
I've been involved at a few startups that over a year later my accounts still are not disabled. At one I logged in six months later and disabled myself.
Identity, access/SSO, provisioning and management are all massive problems that need to be dealt with. For an MVP you are hitting on the important stuff.
Security and being trustworthy are going to be extremely important and I would stress that if I were you. You don't want to be a weak link.
Onboarding is a pain to solve (yay), but offboarding is even worse. If this really does deactivate everyone's account across all services, it's a huge win.
Thanks! Yes, I definitely agree. For the first version, I picked the ones I felt could generate the most interest. I've had people mention Google Apps, the Atlassian suite, Campfire, and many more.
I'm still trying to learn more about Active Directory everyday. Companies like Okta and OneLogin offer user provisioning (what Onboarder is doing) and they integrate with Active Directory.
Onboarder is definitely not that complex yet, but I'm still learning about this space. My goal was to make it simple. Connect with OAuth or give us an API key, and we're good to go.
Yep, looks like it. Thanks for posting this. I was focused on the big players in the space, and I missed this one. It's interesting that it never came up while I was talking about it with others.
You're welcome. I'm not sure how well-known Meldium is -- I think the only reason I'm aware of it is that they're a YC company and I work for a YC company.
Your use of "then" rather than "than" makes it read like you do two steps in a specific order rather than the, I assume, intent of using a better alternative for a time consuming process.
We have 100s of developers using Github, HipChat. This service would be quite useful. Especially the offboarding.
Another thing that would be awesome if your could get even finer grained control of some of the services. Like having the ability to maintain some additional Github permissions. A big pain point for us right now is you need to have admin to manage teams, webhooks, etc. Have some levels between admin and write would be great (and I don't blame GH for having these. It's a more enterprise need.)
Derek, The design and control flow looks very smooth for first version of the site. I have registered and will look to use it, here is a small suggestion, you can probably add something on dashboard to show as initially it shows nothing.
27 comments
[ 2.9 ms ] story [ 58.5 ms ] threadIf you're like me, you've probably used Basecamp, GitHub, Heroku, HipChat, and many other apps on a daily basis. One of the things I found annoying was sending out invitations to all of these different apps. Onboarder solves this. When you need to invite someone new, type in their email (and GitHub username) and you're done. Onboarder handles the rest.
Better yet, when you need to remove access, you can do so with just one click.
I'm exploring opportunities to make this process even simpler. I definitely think it would be better with deeper integration. For a first version, I think it's pretty cool.
Thanks a lot for listening and I welcome any and all feedback.
This seems very valuable to large teams, and like a small convenience to large teams.
Identity, access/SSO, provisioning and management are all massive problems that need to be dealt with. For an MVP you are hitting on the important stuff.
Security and being trustworthy are going to be extremely important and I would stress that if I were you. You don't want to be a weak link.
Onboarder is definitely not that complex yet, but I'm still learning about this space. My goal was to make it simple. Connect with OAuth or give us an API key, and we're good to go.
The onboarding/offboarding process is generally initiated from there, and internal apps and services tend to use that as the canonical user store.
Good luck with your project, I hope it works out well for you!
Another thing that would be awesome if your could get even finer grained control of some of the services. Like having the ability to maintain some additional Github permissions. A big pain point for us right now is you need to have admin to manage teams, webhooks, etc. Have some levels between admin and write would be great (and I don't blame GH for having these. It's a more enterprise need.)