Unified identity platform has simplified brand logins and strengthened customer authentication
What is our primary use case?
Auth0 Platform is the main identity provider at my company for different brands, serving as a gateway to downstream systems.
Each brand uses Auth0 Platform for authentication and authorization purposes, with different services and functionalities downstream where each system is secured by a JWT token signed by the Auth0 tenant, making Auth0 Platform serve as the identity protection layer and authentication and authorization protocol.
Auth0 serves as an attack protection layer, security and access control, automation and onboarding layer.
What is most valuable?
Auth0 Platform offers excellent features including social logins, Single Sign-On options, Multi-Factor Authentication, customizable login UI, and security features such as breached password detection, bot detection, suspicious IP throttling, and anomaly detection.
The most valuable feature in my day-to-day work is the customizable login UI because brands want to customize their universal login, including both the login and registration forms, tailoring the universal login features to their brand's theme. The ease of customization in our Auth0 Platform tenants has been very useful for the brands, helping them stay up to date with current industry standards while maintaining the security of the identity provider.
Enterprise SSO is also one of the most sought features among our brands, allowing a user signing in to a single application to log in without traditional friction in multiple applications at the same tenant, which reduces user friction while maintaining strong security.
Auth0 Platform offers excellent integration with modern web and mobile applications, allowing our brands to deliver new products easily and conveniently. This integration helps them stay up-to-date with industry standard authentication platforms and facilitates the delivery of new features through straightforward integration with continuous integration and continuous delivery processes.
What needs improvement?
One of the sought features in our company that we would like Auth0 Platform to improve is the adoption of new features and how quickly they are integrated. I would appreciate more extensibility features, as although extensions and plugins exist for ease of extensibility, they still are insufficient. For example, social login account linking remains unavailable in Auth0 Platform, which is one of the most requested features from our brands. Additionally, multiple custom domains are also a sought feature, especially for tenants where multiple brands share the same database in the same tenant.
For how long have I used the solution?
I have been using Auth0 Platform for almost three years.
What was our ROI?
I do not have specific metrics available at this time, but various brands have reported significant increases in consumer engagement since adopting Auth0 Platform. Comparatively to the previous identity provider, their releases are faster now. However, I cannot provide specific metrics, but we have observed substantial feedback from our brands and consumers.
What other advice do I have?
Auth0 Platform offers excellent integration with modern web and mobile applications, allowing our brands to deliver new products easily and conveniently. This integration helps them stay up-to-date with industry standard authentication platforms and facilitates the delivery of new features through straightforward integration with continuous integration and continuous delivery processes. I would rate this review an 8 out of 10.
Easy, Reliable Authentication That Saves Time and ensures the necessary protection standards
What do you like best about the product?
An easy, reliable and scalable authentication system. It's an extremely useful and secure tool for integrating a pre-packaged login system into an app, without having to write code myself, saving time and ensuring the right level of protection. It supports virtually all major login systems such as Google, Facebook, Apple login, etc.
What do you dislike about the product?
Usage needs must be correctly calibrated based on potential accesses to the app to define the correct profile. Costs can increase significantly if the user base or feature usage grows.
What problems is the product solving and how is that benefiting you?
This tool allowed me to connect a secure and expandable login system to my app without the complications of programming and following continuous regulatory updates. Without this precious help, I would have had to program the login area myself or rely on third-party plugins that are not always efficient.
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.
