Identity platform has simplified social sign-in and has accelerated secure user onboarding
What is our primary use case?
My main use case for Auth0 Platform is sign up and storing users' information. On our platforms, if we need users to sign up or log in, we use Auth0 Platform implementation with Next.js. It makes the user flow easy to use. If a user wants to use their social sign-in, password, or username and password, we can use the multiple platforms, making the whole process seamless. It is easier than implementing it ourselves. We outsource it to Auth0 Platform, and Auth0 Platform makes the process easier to use.
On the platform, because we tailor certain services to certain users, we implement Auth0 Platform with our database. When the users come on the platform, their details are saved. That also eases the stress of having to manually write users' data. All their sessions and their login processes, everything is saved to the database straightforwardly with the use of Auth0 Platform. That also helps us to implement an easy user flow, so we can manipulate the database easily instead of writing from scratch. It helps us with our database work and makes that process easy and seamless.
I can give a quick, specific example of how Auth0 Platform has helped me in a real scenario. On our platform, we need users to sign in to use our services. If we wanted to create a social sign-in from scratch, we would have to set up our Google Cloud console, our GitHub console, and we would have to set up Facebook, Google, and other providers. We would have to get each different token and set it up. With Auth0 Platform, it eases that process. If I want to implement multiple sign-in processes with Auth0 Platform, I just need to set up my Auth0 Platform account, and it makes the process easy. If I wasn't using Auth0 Platform, I would have to create it from scratch and set up five different sign-up processes, which would take a lot of time. Auth0 Platform saves us that time so fast and so quick.
What is most valuable?
The best features Auth0 Platform offers in my experience include Universal Login, which is one of the main features for us because it makes the whole process easier. Auth0 Platform hosts the login UI, then they redirect the user to it. Also, the SDKs for Next.js, Python, and other languages make the whole OAuth 2 and OIDC flow easier. Additionally, the JWT token and the Rules and Actions, which are serverless functions that run during the auth pipeline, are beneficial. The dashboard is super useful because it helps us to manage users.
Auth0 Platform has positively impacted my organization mainly by improving our developer velocity, which is basically the biggest one. Auth0 Platform eliminates most of the work, such as session management, password hashing, and token fetch logic. Dropping in the SDK and having the core thing as a knowledge base is a pretty significant benefit for a small team. Our security is better by default. Auth0 Platform also bakes in best practices you might otherwise miss, such as brute-force protection, anomaly detection, token expiry, and secure cookies. We are confident in our security and identity solutions. We have social login without the headaches. Integrating Google, GitHub, or Facebook login and handling callbacks and managing tokens yourself is complex. Auth0 Platform turns that into a dashboard toggle. For products where social login improves conversion, this is a huge win.
What needs improvement?
Auth0 Platform works pretty well, but ways it can be improved include the universally cited complaint that the free tier is generous, but the jump to paid can be steep for a growing startup.
Auth0 Platform and Okta said that they are reducing the price for users that are just starting and want to use a paid version.
For how long have I used the solution?
I have been using Auth0 Platform for about two to four years.
What do I think about the stability of the solution?
Auth0 Platform is stable.
What do I think about the scalability of the solution?
Auth0 Platform's scalability is great due to the foundational architecture where Auth0 Platform is built, which is a multi-tenant SaaS platform built on AWS. Scaling is not a problem.
How are customer service and support?
The customer support for Auth0 Platform is fast. The customer service is fast, and they are always there to help.
Which solution did I use previously and why did I switch?
Before choosing Auth0 Platform, I evaluated other options, including Clerk. I decided on Auth0 Platform, but then I switched from using Clerk.
What was our ROI?
The specific outcomes or metrics I have noticed since implementing Auth0 Platform include the measurable metric of the time saved on implementation and building the auth from scratch.
The measurable improvements I have seen in scalability, security, or developer velocity within my cloud environment since implementing Auth0 Platform include a huge gain in API response time. Some session-based flows require a database call on every request to validate the session, which adds tens to hundreds of milliseconds per request. With Auth0 Platform JWTs, validation is local and cryptographic, so there is no network call needed.
What other advice do I have?
Auth0 Platform secures APIs, microservices, serverless applications, or containerized workloads in my cloud environment by issuing a signed JWT access token when a user or a service authenticates. Our API never trusts the caller blindly. It validates the token on every request by checking the signature, the expiry, the audience, and the issuer. If any check fails, the request is rejected before it touches the business logic. I would rate this review an eight out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Auth0 Keeps Our Business, Employees, and Customers Secure
What do you like best about the product?
Using Auth0 helps keep our business, employees, and consumers secure.
What do you dislike about the product?
Sometimes it can be time-consuming to sign in and access my accounts.
What problems is the product solving and how is that benefiting you?
It provides security and protection from hackers. Not only me, but anyone in cyberspace needs this kind of protection.
Auth0 Simplifies Secure Authentication with Powerful, Customizable Features
What do you like best about the product?
What I like the most about Auth0 is that it enables simplifying authentication and authorization without necessarily developing everything on your own. The platform provides a rich set of capabilities such as social logins, multi-factor authentication, and single sign-on, and thus can be highly customizable to various applications. It is also developer friendly, has good documentation and SDKs that facilitate easier integration. Generally, it conserves much time and maintains high levels of security.
What do you dislike about the product?
One downside of Auth0 is that it can feel a bit complex when you first start using it, especially for beginners. The pricing structure can also become expensive as you scale, which might not be ideal for smaller businesses. Additionally, customizing certain workflows or debugging issues sometimes requires deeper technical knowledge, which can slow things down if you’re not very familiar with the platform.
What problems is the product solving and how is that benefiting you?
Auth0 helps solve the challenge of securely managing user authentication and access control. Instead of building and maintaining login systems internally, it provides a reliable and scalable solution. This reduces development effort, improves security, and allows teams to focus more on core business functionalities. It also enhances user experience with seamless login options, ultimately saving time and reducing operational risks.
Seamless Integration, Fast Performance, and Great Support
What do you like best about the product?
Integration is seamless and straightforward, and the UI/UX is great. Performance is fast and supports a large scale of transactions. Pricing is good and it supports all kinds of business models. The ROI is solid, onboarding is trivial, and the support team is great.
What do you dislike about the product?
I would appreciate having more pricing programs with greater flexibility.
What problems is the product solving and how is that benefiting you?
Seamless authentication service. The API integration is easy and adds additional security layers on top of SSO.
Identity platform has secured our cloud APIs and now protects AI and microservices reliably
What is our primary use case?
We are an enterprise IT services provider delivering cloud solutions to our clients. We implement Auth0 (Okta) to secure API integrations, enable SSO for client websites, and support passwordless authentication, MFA, and RBAC. It helps us standardize identity and access management across applications.
What is most valuable?
Auth0 makes it easy to secure APIs, microservices, and modern applications with a consistent identity layer. Features like SSO, MFA, and RBAC are straightforward to configure and work reliably across environments.
For how long have I used the solution?
We have been using Auth0 for about 5–6 years. We initially deployed it in test environments and integrated it for user authentication and SSO access to client applications.
How was the initial setup?
The setup was straightforward. Documentation is clear, and integration with both Azure and AWS architectures was smooth.
Which other solutions did I evaluate?
We evaluated Microsoft Entra ID and some custom-built authentication solutions. Auth0 was easier to integrate and more flexible for our use cases.
What other advice do I have?
Auth0 works well for securing APIs, microservices, serverless, and container-based workloads. We also use it for AI and agent-based applications. It integrates well with AWS services like Lambda, API Gateway, ECS, and EKS.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Critical Issues Overshadow User-Friendly Interface
What do you like best about the product?
I find Auth0's UI very easy to navigate and use, which made onboarding and configuration very easy. Their user management for my customers via a SaaS model is very powerful and extremely useful for triaging authentication issues with our applications. The initial setup of Auth0 was very easy.
What do you dislike about the product?
Their support is the worst of any software vendor I've ever had the displeasure of having to engage with. They don't have any support route if you are locked out of your account, forcing you to create a new account to even create a support ticket to try and get access to your official tenant account. Their own authentication service is also broken very badly as if you use a federated login option without ever setting a password, then no longer have access to those federated service(s), you are permanently locked out of your account. There is no way to do a password reset if you simply never had a password set on your account. Their official support response was to simply re-create everything with our new account we used to open the support ticket originally. We abandoned them for this.
What problems is the product solving and how is that benefiting you?
Auth0 saves us from building and maintaining our own auth solution. Its user management is powerful for handling auth issues, and the UI makes onboarding and configuration easy.
Identity management we built once and never had to rebuild
What do you like best about the product?
The speed at which we got secure authentication running across our applications was genuinely surprising for a team that had previously attempted to build auth in house. Social login enterprise SSO and MFA were all live within days rather than the weeks we had budgeted for. The documentation is thorough enough that our developers rarely needed to go beyond it which kept the integration work moving without constant blockers.
What do you dislike about the product?
Pricing scales up faster than expected once user volumes start growing and the jump between tiers is noticeable.
What problems is the product solving and how is that benefiting you?
Building and maintaining authentication infrastructure internally was pulling engineering time away from product development on a consistent basis. Every time a security requirement changed or a new integration was needed it landed on our core engineering team as unplanned work. Auth0 absorbed all of that complexity and gave us a stable identity layer that our team does not have to think about anymore which has had a compounding effect on how much product work actually gets shipped each quarter.
Centralized authentication has improved security, streamlined roles, and accelerated testing
What is our primary use case?
I have been using Auth0 Platform for more than a year for authorizations, login, and sign-up functionality in my application for my current project.
My main use case for Auth0 Platform involves registering all existing users to Auth0 and onboarding new companies and users, which all feed into Auth0. When I need to update any organizational units, such as the name or trading name, I use Auth0. If I need to change the MFA for any existing user or to check roles and permissions granted to a particular user, I use Auth0.
As a software engineer, I do not use Auth0 that often; I work with the basic, generic flow which I have already mentioned. The developers in my company would use Auth0 on a day-to-day basis. I have used it to handle login, signups, and user identities, so it is a nice tool to work with.
What is most valuable?
Auth0 Platform offers good security features, such as MFA, and the role-based access that can be granted to users is easy to manage with a dropdown and simple access to different permissions and roles. There were times when there was an issue logging in a user, so I had to reset the MFA, and it was straightforward, taking less than a second to complete. These three features are particularly valuable.
The role-based access feature impacts my daily tasks the most because when we onboard a new company, that company needs to be approved by the company admin user. If the user does not have those rights, then the new company would not be able to perform any other task in the product. The role feature was a major breakthrough and was straightforward to use.
The measurable improvements I have seen since implementing Auth0 include faster feature deliveries for developers with fewer auth-related bugs. We have never been uncertain regarding user security, and the traffic has been great without downtime. Auth0 provides 100% centralized authentication, which reduces unauthorized access. The MFA adoption increased by 60 to 70%, and automation shifted from UI-based to token-based authentication using Auth0, reducing test execution time by 20 to 30% and eliminating most flaky tests related to login flows. After migrating to Auth0 from a custom authentication system, we noticed substantial improvements in developer productivity, auth-related implementations, and reduced login flow flaky tests.
What needs improvement?
I find the process of managing roles, permissions, or MFA changes in Auth0 to be straightforward; it has a very user-friendly UI. However, at times I find it difficult to understand the role. In my previous experience a couple of months ago, I checked and the permissions assigned to the user were not working, but then I had to update it by going to its company and then providing the particular permissions. That was one thing I found as a limitation of Auth0, but apart from that, Auth0's UI is very user-friendly and easy to navigate.
I think additional documentation would be beneficial for Auth0.
Now that I am switching into automation, token handling is needed from Auth0, as well as session handling and error handling with invalid and expired tokens. A better layout or a better way to handle those would be helpful. Additionally, improvements can be made around the authorization code flow, refresh tokens, and expired tokens.
What do I think about the stability of the solution?
Auth0 Platform has been highly stable and reliable in my experience; I have never faced downtime or technical issues. It handles increased loads and more users very well, and there may be occasional minor issues, but those are rare and do not significantly impact users. Overall, the platform has proven to be dependable and highly scalable, successfully managing increased traffic due to its stateless JWT-based authentication.
How are customer service and support?
I personally do not reach out to Auth0 Platform customer support because developers or the customer support team handle that for us. However, in minor cases, we did reach out, and they were proactive in replying and helping us. My experience was good.
What other advice do I have?
Security incidents related to the companies and users we onboarded were an issue, as they were not able to access the platform. Debugging that using Auth0 Platform was very effective, and we previously were not using one of the features of Auth0 Platform, but now we are using it and really enjoying it.
My advice for teams considering Auth0 Platform would be to clearly understand the authentication and authorization requirements before implementation. Auth0 Platform is a powerful tool, so it is essential to configure it correctly and use it wisely, especially around token usage, roles, and security policy. I would recommend investing time to understand Auth0 Platform 2.0 and JWT flows. From a testing and performance standpoint, using token-based authentication instead of UI can significantly improve automation speed and reliability. Overall, I believe Auth0 Platform is a great choice, but it should be implemented thoughtfully with proper planning in mind. I would rate this product a 9.
Identity platform has simplified social logins and has accelerated travel app development
What is our primary use case?
My use case is mostly identity management. I used Auth0 Platform to build my personal projects, and they have a very good free tier, so I just use Auth0 Platform to add identity, such as login boxes to my apps.
The industry that my applications serve is travel-related, so it is mostly for end users, not a B2B application. I am building a trip planning app, and it will be a travel industry application.
What is most valuable?
The best features in Auth0 Platform are the social login aspect because they have a lot of out-of-the-box integration and also they have something called Actions, which allows doing different file logins in itself. Actions is another feature I really appreciate.
The secure APIs, the microservices, the serverless applications, and the workloads impact my cloud environment because most of the hosting is done on Auth0 Platform itself, and the Actions I mentioned is where I can write microservices to connect to my other APIs or my backend system, providing quite an intuitive interface. They use JavaScript, which is the language I am also familiar with, so that makes it easy.
The measurable improvements I have seen in scalability, security, and velocity since implementing Auth0 are mostly that I don't have to worry about adding new features because a lot of features are available out of the box when it comes to identity-related features. Rather than me thinking about how to build it from scratch, I just have to search whether this is something supported by Auth0, and more often than not, the answer is affirmative, and then I just have to find out how to enable it and it is done.
What needs improvement?
In Auth0 Platform, one area that has room for improvement is on-premises deployment because one major thing that I see some other vendors do is give on-premises deployment, basically allowing me to have my own version of Auth0. Auth0 currently does not offer that; it is just a SaaS offering. That is something they could add, but other than that, they cover most of the boxes for my requirements.
For how long have I used the solution?
I have been using the solution for almost three years since 2023.
What do I think about the stability of the solution?
I rate the stability at ten. It is definitely stable; I have not had any issues at all.
What do I think about the scalability of the solution?
I find it scalable for my business. So far, so good, as I have not had any issues and I do not think there will be scalability issues because they offer a free tier for twenty-five thousand users. Until I reach that number, I think I am good.
How are customer service and support?
I would rate the technical support at nine or ten; I would say nine because most documentation is up-to-date and I can get answers in their forums. When I need to get support on something which is not there, then it takes some time, such as one to three days at times to get a response.
How was the initial setup?
The deployment is easy; since it is a SaaS offering, I do not need to push any updates or anything of that nature.
Auth0 Platform from my end does not require maintenance. I cannot worry about authentication and I just focus on building my own plans.
What was our ROI?
The return on investment I have seen is that it has saved me quite a lot of time which would have instead gone into implementation, as they have good documentation and quite a few quick starts and examples. I can just give tools such as Cursor or Claude the link to those documentations, and they help add Auth0 Platform to my project, so a lot of time has been saved on implementation.
I estimate it is at least twenty to thirty percent because that part would have involved me writing application code, but that I offloaded to Auth0 Platform. At least thirty percent I would estimate.
Which other solutions did I evaluate?
I would compare Auth0 Platform to other solutions, and I think on the UI side, they are definitely one of the better ones, and they have good documentation. The only downside to them is the pricing, which is a bit expensive.
Regarding the pricing, it is expensive, but I will say the value comes when you use most of its features. Then you can make value out of that price. If you are just using it for basic login and just MFA, then the pricing might be too much and there are other vendors out there who might be better suited.
What other advice do I have?
Approximately three hundred users use Auth0 Platform right now because it is in beta, so I am just testing with a closed group.
I would advise others looking to implement this product that if they do not have any on-premises regulatory requirements, they can definitely look at Auth0 Platform, as they have a really good developer ecosystem. Someone can just download their example projects and play around with it and if it fits the purpose, go ahead. I would highly recommend that. I give this product a review rating of nine.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Strong authentication has improved our enterprise trust and supported rapid ISO certification
What is our primary use case?
Auth0 Platform serves as our primary authentication platform for public-facing websites, and we use it primarily for two-factor authentication.
We only use Auth0 Platform for user authentication and do not use it for API-based authentication.
We currently use Auth0 Platform to secure three applications, and our next phase is introducing multi-tenancy.
What is most valuable?
We chose Auth0 Platform for two main reasons. First is their tenant and segregation capabilities, and the second is their reputation in the industry, which made it much easier to sell our product to enterprises since they had already heard about Auth0 Platform.
The multiple options for two-factor authentication with Auth0 Platform were really easy to set up and integrate into our system. The entire process, including migration of users, took about a week and a half.
Thanks to Auth0 Platform, we are ISO 27001 certified.
What needs improvement?
Managing federated identities for our customers to onboard their own users in Auth0 Platform would be a great enhancement.
For how long have I used the solution?
I have been working with Auth0 Platform for about eight months.
What do I think about the stability of the solution?
We have experienced some crashes, downtimes, and performance issues with Auth0 Platform, but it was not their fault.
What do I think about the scalability of the solution?
Currently with Auth0 Platform, we only have one tenant, and we are planning on implementing multi-tenant architecture.
We are not using multi-tenant architecture yet with Auth0 Platform, as we are planning to use it in our next phase.
How are customer service and support?
Our experience with customer service has been a mixed bag. We had a contact at Okta previously, but because we are on a subscription-based plan, we can only use the community support. Unfortunately, their hours are outside of our working hours, making it difficult to get support from them.
Which solution did I use previously and why did I switch?
Our biggest issue with Auth0 Platform was the cost. From a feature perspective, they had everything we needed compared to the other options. They have the reputation within enterprises. There was another competitor that had a better developer experience, but when it came time to actually using Auth0 Platform, their developer experience was great.
How was the initial setup?
Auth0 Platform was really easy to use, and I honestly do not have any complaints.
We used Auth0 Platform's own documentation and tooling for the deployment.
What other advice do I have?
Explore the documentation for Auth0 Platform, as it is better than you might think. I would rate this product a 9 out of 10.
