Hey PH 👋, It’s been a really great year since we last launched, and I’m excited to share some big updates! For some background, one of my first side projects was a dev tools product around alerting. As I started building it, I realized there were so many edge cases and annoying decisions around the authentication because I was building a B2B product. My users weren’t individuals, they were teams. Should users be allowed in multiple organizations? Can a user be in no organizations, but still use the product? What happens if the only remaining admin leaves the org? I don’t want users to sign up yet, but invitations from existing users should be allowed, right? And that’s before I needed to build all the org management UIs for invitations, roles, revocations, etc. After that, I tended to stick with B2C side projects, primarily to make the auth story easier. When we first launched PropelAuth, we had a simple B2B offering. I pitched the company as “We make auth easier to use. Oh! Btw we have some B2B features.” As we started getting initial traction, we realized that the features our customers were most excited about were the B2B ones. I wasn’t alone in finding B2B auth tedious and time consuming! We've spent the last year focusing on those use cases. The most important thing we do is help you (and your team) not think about authentication any more. To achieve that, we provide: 📄Hosted UIs to launch as quickly as possible: These UIs are fully customizable and include not just signup/login/account pages, but also **organization management** pages. We also just launched our component library if you want to take more control over these UIs. 🏢Orgs + Configurable Roles (RBAC): You can set roles that make sense for your product. And, when you want to change them, we automatically update all existing users/pending invitations for you. 🎊No extra work to support enterprise customers: Larger customers don’t like invite flows. They prefer a solution that ties into their IDP (like Okta, Azure AD, etc). PropelAuth’s UIs enable your customers to set up these connections on their own. You can decide which customers set it up (e.g. the ones that pay for it), and your code doesn’t need to change at all. 🔒All the usual auth fixins: You do still need to sign users up. To that end, we have password login, passwordless/magic links, and social logins. You can collect additional info on signup, like your users name. And your users can enroll in 2FA out of the box. 🏃‍♂️And some unusual ones: As founders ourselves, we wanted to automate a lot of the things we saw people repeatedly building. You can, for example, click a button and disable new users from signing up - which is really handy for manually onboarding customers. You can also set up a Slack bot to notify you of new signups, or require users to change their password the next time they login. One of the best parts of building PropelAuth is getting to see all the cool things that people build. If you build something with us, please let us know! We’re always around for any and all feedback or just chatting about products/startups.

I have been using it for a project, and really like the Org setup out of the box!

We're super happy PropelAuth customers Main reason I love it: Orgs are a first class concept. Example: new users are automatically taken through a workflow to create or join an org (based on email domain) when they first sign in. The other day we changed our email domain and our logins continued to work properly, which I definitely wouldn't have accounted for if I wrote the org mapping logic myself. All the enterprise auth products out there (besides being obscenely expensive) leave basic things like that - anything besides authentication - as an exercise to the user. Really glad to be building on top of a product that continues to extend the features there so I never have to build those kind of IT facing features myself.

Congrats on the launch - really exciting to see all of the changes you've made over the past year.

Congratulations on launching! I've had PropelAuth on my list for quite a while. We're now getting serious about an external CIAM solution, and PropelAuth still looks like it fits all the tech requirements well! However it isn't easy for a European company to move all their user data to a US company, especially when the privacy page has no details on what subprocessors you are using for example. Are you only focussing on US-based customers at the moment, or is this just an oversight and do you have enough in place to help us out?

PropelAuth is nothing short of an amazing team solving a huge problem. Congrats on the launch team!

Congrats on the launch, Andrew!

A slick flow for adding users to an organization & a team that ships and ships and ships. An alternative to Auth0 that gets auth added to an app fast, so you can move on and build. A customer-obsessed team -- I mean, they even offer a Rust SDK.

As a power user of PropelAuth, I can say that their product is amazing! It is easy to use, easy to set up, and the team is one of the best in the game. Super helpful and responsive to any questions you need. Excited to see how the product evolves over the next year! Congrats on the launch Andrew and team!

This could be suuuper useful. When I was a PM at PlayHaven I worked with the team on multi-user access and permission system. It's an iceberg challenge when retroactively applying to an existing account structure.

Congrats on all the progress! I was a happy internal customer of your auth products at Palantir, and excited you are now building for all developers. Keep up the great work.