Auth0 Platform Reviews

I use Auth0 Platform for Identity and Access Management. Additionally, I use it for several different cases for end-users to log in and for internal users to log in. I have used Azure Business to Consumer as well as Entra ID. However, when a project comes up and I have the choice to work with Auth0 Platform, I really prefer to use Auth0 Platform for logins and for user management.

When comparing Auth0 Platform with Azure, you have to do a lot of things yourself if you want it to work and look and feel in a certain way. With Auth0 Platform, that comes more out of the box. You can see that it is focused on giving this experience to the user but also to the developers. There is a lot possible and there are a lot of features within Auth0 Platform. It is an all-in-one solution for this. The ease of use as a developer is what I appreciate the most.

Regarding how Auth0 Platform secures applications, I have configured Auth0 Platform for logging into apps and also to a mobile app, so several things. I use Auth0 Platform by using OAuth and OpenID Connect. What I especially appreciate is that for single sign-on, it has a lot of options. Everything seems to be there and everything seems to be working. I have not encountered a single sign-on with a third party that did not work or was not compatible. When looking at the applications, most are headless. I have an API and a frontend, a backend and a frontend, and some backends are microservices.

When we started in Europe, there was no European data center. That is there now, which solves a lot of problems that we had then. However, to be more compliant and easier to recommend for customers that are government organizations and do not want anything to do with American companies, that is difficult. The same applies to Azure. Having European data centers helped, but it might not be enough for some. Data and data protection are important things. Even now, it is a pain to back up to an offline location or it is hard to back up everything to your own data center or your own location. That is still a hard thing. I have to build that all myself and I have to use the APIs, and for backing up, I need all the data, so that is a pain. It would be nice to have that out of the box so that I could have an offsite backup that is not in Auth0 Platform Cloud.

Regarding the backup I mentioned before, I was puzzled that there was not something already in place to do this. I found out through their support that I indeed had to build this myself.

I have been using Auth0 Platform for about five or six years. It was a couple of years before Okta bought Auth0 Platform.

Auth0 Platform is perfect. I have had no problems there.

The project with the most customers had maybe 5,000 end-users, and that was never an issue. I am not sure how many were concurrent. For my cases, it is all fine. It is very good overall, but I am not Netflix, so for Netflix, I am not sure.

This was more consultancy support rather than support because there was an issue. It was more helping me understand how I should solve my case. I have not had support because there was an issue. For this consultancy, I had a call with Auth0 Platform here in the Netherlands, or Okta here in the Netherlands. I had a call with two people, and that was very pleasant and clear and good.

I have used Azure B2C, as I mentioned before. Before that, I used the old world approach of doing it myself with OAuth and OpenID Connect, and also on-premise Active Directory. I also used Keycloak.

In my opinion, Auth0 Platform is right in the middle of those options, and that makes it, I am a little biased, but that makes it for me the best solution. With Azure, you have it maybe more out of the box with other products that you are using in Azure, but it has limitations that Auth0 Platform does not. Keycloak is the most not out-of-the-box option, where you have to do a lot of things yourself and configure yourself and host yourself. That is also nice in some cases and can be nicer if you have a case that requires that. However, if not, I would go with Auth0 Platform because it is both managed and it does a lot of things out of the box.

To fully deploy it and have it all working and use infrastructure as code, I think a week would be fair. Now, it would easily be done in a day because I already have all this knowledge.

I was working with a rather large team, so to have the knowledge spread across my team, three people worked on that. However, if you have a small team, it could easily be done by one.

Auth0 Platform does provide return on investment.

I want to back up to an offsite location, so that is something I built. I prefer to do everything with infrastructure as code. When there are new features or new things, I like to go on top of that and update my infrastructure as code with the new features. Things are also changing, so some things might phase out and get replaced by newer features. I then have to do some maintenance, but it is not a lot. With Keycloak, it would be more.

I am not the right person to speak about this in detail. So far, I did not have a case where the pricing was an issue, so I think it is all right. I know that it is cheaper to do in Azure, and I have had discussions in the company with some customers where I thought maybe I should go Azure there. However, in the end, it did not work out that way and I still went with Auth0 Platform. However, I do not have the details.

I give Auth0 Platform a review rating of 8.

We use Auth0 Platform for our clients, and we started in 2019, which means we have been using it for around four years.

Auth0 Platform is used for user authentication. We use it for our clients who are using Google authentication. We have integrated with Azure Connect for another client from outside. Basically, we use Auth0 Platform for authentication.

Regarding the flexibility of customizable authentication, we do not have a specific need because we only authenticate, and the endpoint sends the verification, which is really easy. We have even tried SAML connection because another client suggested that there should be more clients with SAML connection.

The impact of Auth0 Platform's centralized, customizable universal login on the user experience is significant because we have to adapt to the client's email since most clients are from Google with a Google IDP. In that case, we use the universal login to separate them and cooperate with that.

We do not utilize the Fine Grained Authorization feature as we only use it for authentication. For authorizations, we use our internal system.

The best features of Auth0 Platform are that it is easy to integrate and is cross-platform. We use it with the Angular front end and the UWP application, and it also works with the iOS application, so it is really easy to integrate within the dashboard without any complications.

Regarding the flexibility of customizable authentication, we do not have a specific need because we only authenticate, and the endpoint sends the verification, which is really easy. We have even tried SAML connection because another client suggested that there should be more clients with SAML connection.

Auth0 Platform could improve by allowing more than three enterprise connections, as I remember it being three. We are stuck with that because I am not sure how the plan works, but it should be at least five.

The areas for improvement in Auth0 Platform include the UWP functionality, which works fine with the SDK. The support is also good as we read the documents available. In comparison to Keycloak, Auth0 Platform is my ultimate choice due to the ease of integration and strong support when we raise a ticket.

The amount of enterprise accounts could be improved, as that is my concern.

We use Auth0 Platform for our clients, and we started in 2019, which means we have been using it for around four years.

The reason I rate scalability a seven is not due to downtime, bugs, or glitches, as we have not experienced any. My concern is more about scaling connection-wise. For the last four years, we have not experienced any bugs from Auth0 Platform.

When assessing scalability, I would rate it around a seven, but the plans raise some concerns for me.

Auth0 Platform is scalable, and I would rate it around ten for being able to downsize or upsize based on our requirements.

Auth0 Platform requires maintenance as we have done some updates, and recently we have not done anything. However, we are in touch with Auth0 Platform team for any required security updates.

Maintenance is easy because we can handle everything using their Auth0 Platform configuration site.

I would rate the technical support of Auth0 Platform around nine, as it is one of the perfect supports I have had.

Positive

I have been using Keycloak for around two years, and we worked with it for around one year for that project. Now we are not working at the moment, but for the support, we are working on that.

Regarding the use case, we do not use Okta platform; we use Keycloak instead. Okta and Keycloak are two different things.

When comparing Auth0 Platform to other solutions and vendors on the market, it stands out for being easy in terms of integration, which is the main thing as a developer. It supports all the libraries, and when going to Angular, there are NPM packages and the SDK available. In comparison to Keycloak being a free open-source option, I prefer Auth0 Platform.

The pricing of Auth0 Platform is a consideration when choosing the technology. While comparing Auth0 Platform and Keycloak, I note that they are two different things—one is free and the other is paid. Therefore, we cannot directly compare a free option to a paid one, but I prefer Auth0 Platform's pricing.

For others looking to implement Auth0 Platform, I recommend that it is very easy to integrate, and they offer free plans to support everything. While pricing might be slightly higher than other options, the support and documentation provided are perfect. The only concern remains the plans, as small organizations like us just need around four to five connections.

I would estimate that the return on investment with Auth0 Platform saves around thirty to forty percent of my time in comparison to integrating with Keycloak.

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.

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.

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.

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.

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.

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.

I am using Auth0 Platform to implement security in the applications that I build. I build applications for myself or for customers, so Auth0 Platform usually provides security authentication to the users of those applications.

Whatever application in whichever language I have built, I can use Auth0 Platform's security for that application because it is easy to implement since they have already built the SDKs and related tools for particular languages. In whichever language my application is, I can use that SDK because they were already pre-built. Using that means that my application development time and the time to implement security for my application will be less. I scheduled a call to provide a review on Auth0 Platform.

Auth0 Platform is very easy to use and very intuitive in nature. For developers, it is mainly a great platform to implement the security framework in their applications because they have already built some previously. It is easy to use that instead of building from scratch in my application. The customizations for the end user, such as the domain or the interface which the user is directly facing, can be customized with Auth0 Platform. The hooks, all these actions, and all triggers are parts which I liked more in Auth0 Platform.

I can serve almost every category because whichever application I have built can use Auth0 Platform since it supports all web applications, mobile applications, API services, back-end services, and all of this. I can use Auth0 Platform for any sector that has been built with web applications or mobile applications.

One of the positive impacts I have seen since starting to use Auth0 Platform is time saving, and the SDKs are the main thing. They are already built, so it is easy to use. They documented it very well, so whenever I send it to some other developer to develop this application or to change anything in this configuration, it is easy to understand. When passing it to someone, it is straightforward.

The recently launched AI agents for Auth0 Platform is also a positive one, which is a growing feature in this technology. I appreciate that aspect as well.

Auth0 Platform is very easy to use and very intuitive in nature. For developers, it is mainly a great platform to implement the security framework in their applications because they have already built some previously. It is easy to use that instead of building from scratch in my application. The customizations for the end user, such as the domain or the interface which the user is directly facing, can be customized with Auth0 Platform. The hooks, all these actions, and all triggers are parts which I appreciated more in Auth0 Platform.

Auth0 Platform has an extension in the marketplace to see whatever applications I have assigned to the user. It would be easier if, as developed in Okta, they had an end-user dashboard integrated directly with Auth0 Platform's dashboard itself. That is one thing I can say could be improved. Other than that, I did not find any big impact areas for improvement because they have almost given all the features for a customer-facing platform.

I have been working with Auth0 Platform for four to five months.

I would rate the stability of Auth0 Platform as a nine.

I would rate the scalability of Auth0 Platform an eight. The features I have explained before indicate that it is easy to implement Auth0 Platform, and I found its scalability to be an eight out of ten.

I did not need to communicate with technical support during the initial setup because, while working with my test applications, I did not encounter any disturbance or ambiguity in implementing Auth0 Platform with my application, so I did not contact technical support yet.

Positive

I have started the CIAM with Auth0 Platform itself. Previously, I used similar platforms for workforce identity, not for customer identity. Customer identity and workforce identity provide almost similar features, but workforce requires more security. I did not check previously about the competitors of Auth0 Platform, but I can say I have worked on similar workforce identity solutions, making this my first experience with customer identity.

The installation was easy because they have a lot of documentation mentioning how to start and where to start. It is easy to deploy Auth0 Platform to my applications because their documentation is very well organized, making it user-friendly.

I participate in the implementation process with Auth0 Platform, so I have worked with that.

I have just explored the pricing and licensing of Auth0 Platform, but I cannot recollect the exact figure. I know that pricing is mentioned in the documentation, such as how much they will charge for a certain number of users, but I did not collect the exact amount.

I think Auth0 Platform is not expensive compared to other platforms. It is affordable, and as the number of users grows, the pricing fluctuates. Considering the amount of features I use, such as multi-factor authentication, it is affordable and comparatively less for the features it is giving compared to other existing platforms.

I did not evaluate other options or vendors before choosing Auth0 Platform. As I mentioned, I worked on workforce identity and did not check the alternatives, so I have used this only.

The cross-app connection Auth0 Platform has built allows access to other applications also with the AI agent without asking for consent from the user, which is a very good feature.

What attracted me to Auth0 Platform is how simple and easy it is to implement with my applications. Other platforms might provide similar APIs and features, but Auth0 Platform has a vast variety of language-specific SDKs. Whatever language I want, I can take that SDK and implement it right away in my applications, which is an easy aspect that attracted me most. I am using Auth0 Platform to secure AI-powered applications, as I previously mentioned. The AI agents is the feature that is introduced new to Auth0 Platform. I can secure my AI agents while interacting with them.

I use Auth0 Platform as our authentication platform to allow our customers into the app that we provide, so it's essentially our authentication piece.

The ability to manage multiple customers and assign roles within Auth0 Platform is the most valuable feature I have found. It allows certain users access only to specific pages or data sets in our application. We can have all our customers in different buckets. I also maintain separate production and staging environments with distinct setups, making it central for authentication management across different environments and customers.

The flexibility of Auth0 Platform's customizable authentication flows in adapting to our organization's specific needs is commendable. Being able to execute custom code snippets within Auth0 Platform to set different access levels or provide messages to users who lack access to requested pages, along with tracking and notifications, is very beneficial.

The impact of Auth0 Platform's centralized, customizable universal login on our organization's user experience is significant, as it is essential for hosting our application effectively.

The reporting in Auth0 Platform could use improvement. Currently, most of the reporting is contained within Auth0 Platform, but it would be useful to have notification streams sent to email or Teams. Enhancing notification features and their ease of use would be beneficial.

I do not have any specific recommendations for improvements as I utilize features I need, such as actions and triggers, as needed. Much in Auth0 Platform remains unutilized by us due to lack of needs, highlighting scalability.

I am not using Bot Detection and Attack Protection enhancements actively; it might be part of Auth0 Platform that I am not familiar with. Additionally, I lack enhanced B2B features implementation, focusing instead on applications and user management.

I have been working with Auth0 Platform for approximately seven or eight years.

I have not often communicated with the technical support specialists at Auth0 Platform. I remember maybe once or twice experiencing outages that seemed global. During those instances, I waited for service restoration without contacting support.

Auth0 Platform scales exceptionally well with us. I find the built-in Zanzibar and Spide authorization engine robust. As I continuously add users, customers, and refactor for other applications in Auth0 Platform, it supports my application growth efficiently.

I would rate the scalability level of Auth0 Platform as a 10. Scalability is crucial for us, with business directives requiring flexible and manageable platforms such as Auth0 Platform. Its intuitive interface supports seamless build-outs as needed without problems.

I have not often communicated with the technical support specialists of Auth0 Platform, except possibly during rare outages. Otherwise, I have not needed to engage with tech support.

Negative

I used a different solution for similar use cases before Auth0 Platform, through Microsoft. It was contained in Microsoft Azure's federation service, though the exact name escapes me as it has been a long time.

I switched to Auth0 Platform as part of migrating from Azure to Google Cloud seven years ago, driven by dissatisfaction with Microsoft Azure due to billing issues. My move to the Google stack included incorporating Auth0 Platform.

I considered options such as Okta at one point, but Auth0 Platform was a better fit.

From what I remember, the initial setup process with Auth0 Platform was straightforward. I had guides and consultants familiar with Auth0 Platform who provided a white-glove service, aiding my team in establishing connections and setting up my application. The scalability since then has been admirable.

I participated in the initial setup and deployment of Auth0 Platform.

I feel it has been a very prudent investment. I get everything I want and more from it for what I invest.

Currently, I feel that Auth0 Platform is very affordable.

In my Confluence environment, I have instructions for setting up new applications, adding, and managing users, so I maintain my custom documentation for Auth0 Platform.

I think it is somewhat difficult to suggest enhancements for Auth0 Platform as I choose features based on necessity and have always found needful accommodations when required.

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.

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.

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.

I have been using Auth0 for almost three years.

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.

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.

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.

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.

I have been using Auth0 Platform for almost three years.

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.

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.

My main use case for Auth0 Platform is as an authentication service for apps that I build.

I have an app that has retail users who require a log in. My app provisions them both in my local database and creates an identity in Auth0 as well. They create their password and use that subsequently every time they want to log in.

Auth0 Platform's best features include automating the entire login stream in a secure way, providing storage for user credentials, offering a robust password reset facility that users can use by themselves without involving any of my support personnel, and providing a log of all user interactions in terms of logins, logouts, and password resets.

Auth0 Platform positively impacts my organization because, in terms of development work I do, I don't have to spend really any time at all on authentication features or password reset features or anything that Auth0 Platform automates for me.

Auth0 Platform's documentation is excellent, their support organization is excellent, their code is robust, and it's certified as secure.

I have been using Auth0 Platform off and on for about ten years.

Auth0 Platform is stable.

I have had no problems whatsoever with Auth0 Platform's scalability, but I don't really have a large number of users yet.

Auth0 Platform's customer support is excellent.

I rate the customer support a nine on a scale of one to ten.

I did not previously use a different solution.

Auth0 Platform is deployed in my organization by embedding the client SDK in my application, which is deployed to the cloud, allowing users to access my application by connecting to the cloud service and logging in.

Auth0 Platform's pricing, setup cost, and licensing are excellent, and they provide a large free tier that is beneficial to companies with applications just starting to scale their user base.

I evaluated whatever were the range of similar services available at the time before choosing Auth0 Platform, but Auth0 Platform was the best and continues to remain one of the best.

My advice for others looking into using Auth0 Platform is to familiarize themselves with the underlying protocol standards, in this case OAuth. I rate this review ten out of ten.