Effortless Social Login Integration for Node.js
What do you like best about the product?
Basically i used into taking the implementation into nodejs for taking for signup using other social login easily not requiring the setup for each flow just key add in their platform with connectivity in it and key addition in it as well as you can do the google login as well as signup in nodejs in it easily and moreover it will be best for who wants to works to add authentication flows of different social media
What do you dislike about the product?
Design-wise option is less for authentication flow otherwise everything is fine
What problems is the product solving and how is that benefiting you?
It helps me to do the faster process of social media logins as well as easy to setup in code and it gives me the benefits for not wasting my time on setup for all key and nodejs modules just one configuration and it start working for it
Effortless Authentication with Room for Growth
What do you like best about the product?
I like Auth0 for its easy authentication, especially for Multi-Factor Authentication use. I find the setup very easy, which is a huge plus. It offers a great dashboard for user analytics, which is really beneficial.
What do you dislike about the product?
There's some pricing concerns since pricing increases with users and content. The console interface can seem overwhelming at first with lots of options and can require deeper learning.
What problems is the product solving and how is that benefiting you?
I use Auth0 for easy authentication, supporting Multi-Factor Authentication, simplifying sign-ons for interactive displays, and detecting anomalies. It offers an easy setup and a great dashboard for user analytics.
Effortless Setup and Seamless Integration with Auth0
What do you like best about the product?
I use Auth0 for an authentication system to verify user identities, making it extremely easy to set up and integrate with custom systems. I will be using it again because it solves the problem of displaying certain codes for specific users in a cost-effective way compared to other providers. I like its ease of access and the ability to integrate very easily with custom-built systems and build databases. Auth0 works especially well with a React frontend and Node backend. Using it with Python, specifically the Django backend system, also works well. Switching to Auth0 from Firebase made things much easier and better for us. The initial setup was very smooth with no errors, and the documentation suited our requirements perfectly. I recommend Auth0 a 10 out of 10.
What do you dislike about the product?
I feel its lack of customization on the login page could be improved. I think adding the ability to use CSS, like Tailwind, to have the freedom of customizability.
What problems is the product solving and how is that benefiting you?
Auth0 makes it easy to verify users and integrate with custom systems, solving my need to display specific codes for users more affordably than other providers.
Powerful Authentication with Room for Better Usability
What do you like best about the product?
I use Auth0 to add authentication to my website, and I appreciate how it helps with security and user data. I like adding Google auth, GitHub auth, and other integrations, making the authentication process diverse and flexible. Once you get the hang of it, setting it up turns into a piece of cake.
What do you dislike about the product?
It's not very easy to use for beginners, and I wish it was more beginner-friendly with some error resolving from the developers. The initial setup was tricky at first.
What problems is the product solving and how is that benefiting you?
I use Auth0 to add authentication to my website, solving issues with security and user data. It's easier once set up, with useful Google and GitHub auth options.
Effortless Secure Logins with AuthO
What do you like best about the product?
AuthO is very easy to deploy and set to facilitate secure login with OTP where does not require technical guides for one to use since you can embed the verification link into the login auth flow
What do you dislike about the product?
The cost can be expensive after your startup benefit expiring and not more scalable since it becomes too much expensive the more you use it and grow clientele base
What problems is the product solving and how is that benefiting you?
The solution is providing us with good login flow which is more secure with token based OTP and this protects our ecosystem from being compromised
Intuitive, Secure, and Developer-Friendly, But Pricey
What do you like best about the product?
I love the developer experience with Auth0 and how quickly I can get user authentication running. The good documentation and SDKs make complex tasks like JWT Token management for my websocket chat interface straightforward. The developer experience helps me tremendously because the clear documentation for code examples with Python/FastAPI means I can integrate authentication into my backend API endpoints easily. Also, the initial setup was quite easy, and the helpful guide made the process smooth.
What do you dislike about the product?
The main problem I face is the price structure can get quite steep as my user base increases. Especially with features like MFA and advanced security that should arguably be standard for an app handling voice recordings.
What problems is the product solving and how is that benefiting you?
I use Auth0 for secure user authorization, which eliminates the complexity and security risks of building an authentication system from scratch. The developer experience with clear documentation and SDKs helps me integrate authentication into my backend API endpoints easily.
Auth0 takes the complexity out of authentication so I can focus on building rail software
What do you like best about the product?
In my day-to-day work as a backend developer at Sternico, I really appreciate how Auth0 removes a whole category of problems from my plate. I work a lot with C#, ASP.NET Core, REST APIs, and Onion Architecture, and integrating Auth0 into that stack has been surprisingly smooth. Their SDKs and documentation fit naturally into the .NET ecosystem, and features like MFA, passwordless options, and role-based access are basically ready to go. I no longer have to write or maintain piles of custom authentication code, which is a huge relief, especially in a domain like railway operations where security and reliability matter a lot. It lets me stay focused on building solid business logic instead of messing around with token lifecycles every week.
What do you dislike about the product?
Pricing model isn’t always easy to predict. Some important features only pop up in higher tiers, which can be a challenge when planning long-term usage across multiple applications.
What problems is the product solving and how is that benefiting you?
At Sternico, a lot of what we build, whether for RAILBASE, COMAP, or custom integrations, depends on secure, reliable access control. Auth0 helps us deliver that without reinventing the wheel. For me personally, it shortens development cycles since I can plug secure authentication into our .NET Core services and APIs quickly. It also supports our broader architecture: cleaner separation of concerns, better maintainability, and fewer custom security components to maintain over time. Since we work in the railway sector where safety, compliance, and traceability are crucial, having a stable identity layer gives us confidence and helps us release features faster without compromising on security. Overall, Auth0 fits well into our software ecosystem and supports the way our agile teams work.
Secure API access for enterprises has improved and provides dynamic authentication for users
What is our primary use case?
My main use case for Auth0 is for authentication purposes for my APIs. I rely on it mainly to give specific access to a specific enterprise or user depending on their eligibility.
I use Auth0 to authenticate our enterprise customers before giving them access to a set of APIs where we show them the data or billing information, anything that they want and we can offer. Everything goes through Auth0.
What is most valuable?
The best features Auth0 offers are its scalability and it is a better way of authenticating a user compared to just a tokenized version of authentication where the token is static and does not offer dynamic authentication compared to how Auth0 offers it.
While working in a dynamic environment where there are many enterprises involved in the service, you need a tool that can authenticate them on the go, which is why I like it.
Auth0 has positively impacted my organization. Previously we used the tokenized version of authentication. The work was simple, but when you push this code to deployment and enterprises are involved, it makes much more sense to authenticate them through Auth0 so that you can just get a login for yourself when you are authenticated, which helps to dynamically scale depending on the product and its viability.
The specific outcomes since I started using Auth0 include time-saving, more security, and scalability, which are the three things I would emphasize.
What needs improvement?
I do not think there are any improvements needed for Auth0, other than maybe making it more visible to beginners. Auth0 could be made more accessible to beginners.
For how long have I used the solution?
I have been using Auth0 for almost three years.
What other advice do I have?
The features of Auth0 have been thoroughly covered. I would rate Auth0 an eight out of ten. I chose eight out of ten because there is always something to improve in a product, and giving eight actually keeps that room for improvement compared to giving it a ten.
Auth0 is deployed in my organization as a hybrid cloud. We use Amazon Web Services as our cloud provider for the hybrid deployment of Auth0. We purchased Auth0 through the AWS Marketplace.
I would say to others looking into using Auth0 that if you are building any product which needs an authentication flow for your API-based approach, using Auth0 from day one might be very helpful because you can scale over it as quickly as possible. My overall rating for Auth0 is eight out of ten.
A dependable authentication platform that helps us move faster at LiveEasy
What do you like best about the product?
Working at LiveEasy, I’m constantly bouncing between backend tasks, fixing odd edge cases, and trying to keep the homeowner and partner experience smooth. Auth0 has been one of those tools that slips into the background in a good way. I plug it into a Django service, write a few lines, and suddenly I’m not worrying about password resets or a shaky login flow anymore.
What do you dislike about the product?
Once you go beyond the basics, Auth0 does start to feel a bit heavier. Some of the advanced configurations require extra time to understand, and the documentation sometimes skips the parts you actually need when customizing things at a deeper level .
What problems is the product solving and how is that benefiting you?
Auth0 has helped us at LiveEasy by letting us focus more on building the moving and home-management experience rather than getting stuck maintaining authentication logic. With multiple partners and various user-facing touchpoints, having a stable identity system really matters.
Instead of writing custom auth code for every service, we plug into Auth0 and get a consistent flow across our platform. This saves development time, reduces potential security risks, and lets us ship updates faster. For a team that wants to keep improving the product experience, offloading identity management to a platform we can trust has been a big win.
Outstanding User Management and Configuration Features
What do you like best about the product?
I like the user management module, also the application configuration and the logs of the requests made to the application
What do you dislike about the product?
Some times, the integration with custom applications isn't that easy for beginners
What problems is the product solving and how is that benefiting you?
The management of passwords and user registration in my application, this benefits me because it's safer than handling the keys directly in my database.
