Stytch is a full stack authentication and authorization platform, whose APIs make it simple to seamlessly onboard, authenticate and engage users. Improve security and user experience by going passwordless.
@bogomep hi there, our api docs are the best place to start to understand how the different products work, depending on which you choose and how you integrate them, the threat model might vary https://stytch.com/docs/api
We're happy to chat more in depth if it's of interest.
This sounds as an awesome tool! *_* Big congrats! ^_^ Getting rid of passwords is such a relieve! ':D May I ask you please, is there some explanation/tutorial for usage/implementation maybe? :) This would be very helpful! ^_^
Congrats on the launch! We use Firebase for email, passwordless login link, Google, and Twitter login today. When should we consider Stytch vs our current solution?
@parthi_logan hi Parthi, we support all of those products today except sign in with Twitter, that one is on our roadmap for early next year. We'd love to chat more about our solution and how it can help improve user conversion, one thing to check out would be our google one tap integration: https://stytch.com/blog/improvin...
We've been using Stytch at Quaestor to power auth through magic links for several months now and it has been the easiest integration I've built. Stytch absolutely nails the developer experience better than any API product I've used (even small things like automatically adding API keys to the documentation if you're logged in). The company also has React and JS components if you don't want to build out the UI yourself, but customizing and using your own UI along with Stytch's client libraries are also super simple to get up and running- we initially were using Stytch's React component to power our logins but later switched to building our own UI.
Hey there! Super thrilled to launch on the same day as you guys :D
I took a look at your product and our users could actually use it together with our front-end builder. (We have a native Auth0 integration, could do the same with Stytch).
Feel free to reach out if you want to discuss it :)
Good luck with the launch 🦾
Best,
Raphaël
Congrats on the launch @jelamb ! Stych looks amazing and from our experience building passwordless-auth at Kapwing I definitely understand the pain point!
Stytch is the best authentication API out there, hands down. What I love about the product is that it is super flexible for any company's needs. For example, if you are a building a completely brand new application and you want to outsource both authentication and session management to Stytch, you can do that. However, if you are a large company and you can't migrate all your systems at once, Stytch still fits in great for important parts of the workflow!
Even more importantly, the Stytch team is amazing. The moment I need have a question or an issue about the API, they will do whatever it takes to help me out. They are super responsive and are extremely customer focused. Regardless of whether or not you need a new auth/session management system right now, you should keep on eye on this team :).
Hi @jelamb -- love seeing all the progress and updates! Any thoughts on supporting web3/crypto wallets as a form of identity at some point in the future?
Hi Product Hunt 👋
We’re really excited to share Stytch with you!
My co-founder, Reed, and I met at Plaid back in 2017 -- during our time there, we both worked on the user authentication features that millions of people use to connect their bank accounts to apps like Venmo, Coinbase, and Robinhood. While working on these projects, we experienced first-hand how frustrating it is to build authentication flows. In addition to being complicated, resource-intensive, and error-prone to build in-house, we saw a fundamental issue with how most authentication is architected around passwords. Passwords pose significant security and user experience issues.
On the security side, passwords make companies a target for hackers and expose them to account takeover risk (especially given how often users re-use passwords across different online accounts). Passwords also present a significant conversion cost for companies, introducing drop-off during onboarding and retention issues when users forget their passwords. Today, there are a myriad of authentication factors that provide both strong security and a great user experience, yet many people still rely on archaic password-based flows.
As we were painfully building new authentication flows, we wished there was simple developer tooling that made it easy to embed passwordless authentication features into any app. This led us to build Stytch, a developer platform that enables teams to easily and securely weave authentication into their products.
See what Stytch’s solution has to offer:
✅ Support for multiple passwordless methods, including OAuth connections (Google Apple, etc.), WebAuthn (w/ biometric and YubiKey support), email magic links, SMS passcodes and more
⚡APIs for one-click user invitations that don’t require password creation or confirmation steps
🏋️♀️ Customizable front-end components that handle the heavy lifting for you
👩💻 A direct API for maximum composability
🤥 Fraud prevention and anomaly detection
🔄 Built-in redundancy across multiple SMS + email vendors
We’ve also recently expanded our platform to support fine-grained and flexible session management with our latest beta product, Stytch Sessions. Our sessions product allows you to easily support just-in-time authentication in order to place the right amount of friction in front of users at the right time. We’re excited to hear your feedback on this product as we’re working on new features and functionality to bring it out of beta.
👉 You can sign up today and get up and running with Stytch for free!
You’ll also receive an extra $5k in credits (which makes your first 50k active users completely free) if you sign up today. All you have to do is complete the signup process and send us an email at ph@stytch.com and we’ll apply the credits.
If you want to learn more, check out documentation here: https://stytch.com/docs
Reed, myself and the rest of the team would love to hear your feedback!
@charleyma Hey Charley, happy to share more on how we think about those different surface areas:
-On mobile, one of the unique authentication options is that if you support SMS one-time passcodes, you can integrate it so that the passcode sent to the user's text inbox auto-fills on both iOS and Android. This effectively makes it a one tap sign-up or login experience.
For mobile, you typically still want to give the user an option if they'd prefer another method (e.g. email magic link or sign in with Google/Apple), but SMS is really powerful on mobile and should typically be included in that option set. Square Cash has a good flow where they give the user the option of SMS or Email passwordless login so that they can choose what's more convenient for them based on whether they're on mobile or desktop
-On desktop, you can't guarantee a user will have their phone within arm's reach. Typically, we find most do have immediate access to their phone but it's not uncommon for some to have their phone somewhere else in their home. As a result, you'll always want to offer another high converting option like an OAuth option (Google/Apple/Microsoft/Facebook, etc. -- which you offer typically depends on if you're B2B or B2C) and the neutral email magic link or passcode option.
On desktop, the biggest thing I'd recommend is supporting Google One Tap (https://stytch.com/blog/improvin...). Most companies that integrate it see large double-digit conversion increases in both user sign-ups and returning user logins
We've also written a blog post that goes into more specific recommendations around passwordless options by vertical and mobile vs. desktop: https://stytch.com/blog/stytch-g...
Let me know if I can answer any other questions!
An incredibly useful product that addresses multiple pain points (security, developer experience, etc). Improving efficiency within a login flow without sacrificing security and quality is an extremely difficult, yet crucial and necessary task. Stytch's various SDK's help developers do exactly this.
@b_faje Hey Brandon,
Clerk and Auth0 still support passwords as a method of authentication and this is meaningful for a number of reasons (more detail below). Magic is passwordless but they are SDK-first meaning you don’t have full control over the UI/UX.
We find that many companies want to slowly replace their password-based authentication flows (peeling the bandaid off can be hard) and can’t do that with front-end component providers. We make it totally possible with Stytch. We’ve had customers use us for password resets via email magic link and other customers just use us just for OAuth alongside traditional passwords. The beauty is that their end users have no idea Stytch is powering those experiences!
Additionally, I’d call out:
Technical Flexibility: Because Auth0 and Clerk still support passwords they take a widget-based approach to the user flow for security purposes. Stytch offers a direct API integration for maximum customization and composability. Auth0, Magic and Clerk offer front-end components but do not allow for full customization. Stytch also offer highly customizable frontend components, which can be seamlessly integrated into your brand (unlike Auth0/Okta, these can be integrated into your user interface rather than requiring a hosted redirect page)
Reliability and deliverability: With Stytch you don’t need to worry about warming up IPs for email sending or managing your SMS provider. Also, Stytch has invested significantly in making sure that they have the right architecture to prevent outages, and have taken a dynamic failover approach to the products they support so that third-party downtime doesn’t impact you (e.g. programmatic SMS + email). The others mentioned above take a different approach -- it’s more of a “bring your own provider”.
Integration Experience: Most Stytch developers report finishing the integration within a day whereas Auth0 can take weeks.
Embedded Authentication: This is something unique to Stytch that none of the other providers mentioned have. Once again, because of our API-first approach, we can expose the primitives to developers allowing for authentication to happen within communication experiences.
Google One Tap: Out of those companies you listed, we’re the only provider to offer support for Google One Tap, which can have amazing conversion results.
For both Embedded Auth and One Tap, we have more information in our docs but happy to hop on a call to demo these as well if it's helpful!
We are launching our product soon and have integrated with Stytch.
It definitely has to be one of the easier and more ergonomic integrations I've coded up in a while.
Will absolutely recommend to anyone building a product focused on great UX and security.
@ikechi_obiajunwa Thanks, Ikechi! And if you have any feature requests from your integration, let us know! We're in the midst of 2022 planning right now
Authentication via password hasn't made sense for years, and it's nice to see Stytch solving some of the internet's most pressing UX and security gaps as well as they are. The team is smart and ambitious, and I'm excited to see what else they tackle in the coming years!
Congrats to the whole team on the launch, and please give their docs a look and send feedback—I know they're eager to hear it 😊.
Threat Modeling e-book