Auth0 Platform Reviews

Our main use case for Auth0 Platform is to work with our partners to take to the customers, with Auth0 Platform being an identity and access management platform that helps developers add authentication and authorization to apps. We are working with a lot of companies that have many developers, allowing us to help implement and service Auth0 Platform services. We can build a login system from scratch, handling user login, identity verification, and access controls for their applications.

I can give a quick, specific example of a project where we used Auth0 Platform for these purposes, keeping it anonymous. We did a large project for a customer that wanted admin versus regular user permissions. We provided access to certain APIs and implemented role-based access control, controlling what different users were allowed to do when logging in or after logging in. A big part of that was the authorization point, along with daily tasks such as providing single sign-on, allowing users to log in once and access multiple apps without repeated logins. We essentially created a whole login to a company portal that automatically accesses internal tools such as Salesforce, HiBob, and Outlook.

There are different elements to the best features Auth0 Platform offers, and I have touched on them, particularly the ability to help applications authenticate and authorize their users and manage their identities. A big point is identity federation, allowing connections across multiple identity providers, enabling users to log in using existing accounts due to databases and enterprise identity systems.

A strong security feature is provided, particularly with their MFA, multi-factor authentication, which includes bot detection and brute-force protection, along with breached password detection, which is really good as an added extra.

Auth0 Platform has positively impacted our organization, particularly in terms of usability. While we are not selling it directly, I find the platform easy to use for authenticating different users. Our own services team handles the implementation, so I cannot comment on the ease of that process. However, whenever we have had contracts and bids to roll out services, it has been really easy.

We have seen improved security due to the implementation of Auth0 Platform. User management, such as creating and deleting users, is all about enhancing the user experience, which is massive. We assist with password resets and account linking. The time to implement is shorter, and we maintain a consistent user experience with a secure login flow, benefiting from a faster implementation due to the universal login, providing a hosted login page customizable by developers.

I am not involved on the development side, so I cannot speak to the technical aspects that could be improved on the implementation. However, the core cloud-based identity and access management is solid, and the workflow could always improve. There are a few hitches, but customer feedback has generally been very good.

The only negative feedback I have heard is about the decision to go direct rather than through partners or distribution channels. However, this is not a product-related issue; it is more feedback from channel partners.

I've been working with Auth0 for about eighteen months now.

Auth0 Platform is completely stable, built on a strong security baseline covering the API gateways for user data. It is 100% reliable, especially with the support of our implementation services partner.

Scalability is quite vast, but it does lead to higher pricing as usage increases.

It is designed to be highly scalable, capable of managing millions of users and billions of authentication requests globally. This scalability comes from its cloud-native architecture and its token-based systems, operating effectively across AWS, which also helps reduce bottlenecks through JSON Web Tokens and is built on microservices architecture.

Customer support has been really good; we manage our own support for our channel partners through Okta, along with the support from our implementation services partner in Berlin.

On a scale of 1 to 10, I would rate customer support a 10, as they have always been very attentive and effective. It could be a nine if considering direct engagements, but overall, the product and customer service have been excellent.

I have not used a different solution because we distribute the products and have been working with Okta for eight or nine years. After Okta acquired Auth0 Platform in 2021, we have been using Auth0 Platform since.

Auth0 Platform has moved its infrastructure to a single cloud architecture on AWS to simplify operations and scale globally. The services run across multiple AWS regions to handle billions of login requests and ensure high availability, meaning the applications calling an Auth0 Platform API for logins or tokens are all managed by AWS infrastructure. Additionally, Azure is key for private deployments.

As for deployment, we utilize a services partner in Berlin for the implementation, and we use a cloud-based software approach.

While I do not have specific numerical metrics, there has been a noticeable reduction in the number of security team personnel needed due to the robust security provided by Auth0 Platform. The implementation and service time for deployment have been quick, with great feedback from Auth0 Platform and Okta's customer service.

Developers benefit from not having to expand their teams to handle manual user integrations. While I cannot definitively claim time savings, I suspect it is significant as fewer employees are needed for user management due to the efficiencies gained through Auth0 Platform.

Regarding pricing and licensing, it seems reasonable; however, I noted a bit of negativity at scale due to the vast user base and high costs associated with government clients. Some competitors were considered for their pricing models, but overall, the service has been well received.

A downside I remember mentioning is that pricing can be high at scale, though that is not a product issue; it relates more to the nature of large enterprise solutions.

We have not evaluated any other options since we have been exclusively with Okta for nearly a decade, especially since we will not typically engage with other competitors within the Microsoft stack.

My advice for others considering Auth0 Platform is to definitely look into it. Running a proof of value reveals how it leads to cost reduction, time savings, and improved scalability, demonstrating how easy it is to work with. Auth0 Platform is effective for businesses looking to simplify authentication and identity management, and I would strongly recommend it.

Auth0 Platform secures APIs and microservices by acting as a central identity provider. It uses modern token-based authentication standards by issuing JSON Web Tokens (JWTs) that provide identity and permissions for requesters. Tokens are normally signed and can be optionally encrypted, allowing APIs to verify authenticity without querying Auth0 Platform each time. Additionally, OAuth 2.0 and some role-based access controls enable APIs to check roles within the JWT, differentiating admin capabilities from those of regular users.

My overall review rating for Auth0 Platform is 9.

We have multi-tenant applications. We initially conducted POCs with other providers including Cognito and some open-source providers, as well as Auth0 Platform. We chose Auth0 Platform because it provides excellent multi-tenant tenancy support, such as creating multiple organizations and having separate users within each organization, which aligned with our application requirements.

Auth0 Platform offers good support and community resources, along with APIs and SDKs. We have Next.js in the frontend and FastAPI in the backend. We used Auth0 Platform SDKs to handle all communication with Auth0 Platform from the frontend. After we receive tokens, we use those tokens in the APIs. From the backend, we use Auth0 Platform public keys to authenticate the token and retrieve user information.

We implemented Auth0 Platform workflow with two-step verification using authorization code with PKCE. Auth0 Platform generates automatic verification codes whenever users log in. This verification code is sent again after receiving authorization codes to obtain the actual token, which is an encrypted token. When we pass this token to APIs, we retrieve published keys to obtain token information and signatures, which are verified before access to backend system APIs is granted. Everything is handled by Auth0 Platform. From a security and compliance perspective, we receive JWT tokens that we verify using the keys, which secures our backends. We have a central gateway where we route APIs, and on the gateway, we have added Auth0 Platform token verification. If verification passes, we allow access to the application layer; otherwise, we deny the request with appropriate codes like 401 or 403.

From a compliance perspective, we did not want to store user IDs and passwords. We used passwordless authentication through email OTP or phone OTP. We also implemented enterprise connections such as Google Workspace and Microsoft Azure AD. The organization support feature allows us to define users based on organizations. Passwordless authentication is a particularly good feature when compared with other platforms.

Auth0 Platform offers good support and community resources, along with APIs and SDKs. We used Auth0 Platform SDKs to handle all communication with Auth0 Platform from the frontend. After we receive tokens, we use those tokens in the APIs. From the backend, we use Auth0 Platform public keys to authenticate the token and retrieve user information. The community support was particularly helpful when we encountered obstacles during implementation. We received excellent support from the community when we were stuck. The SDKs provided a plug-and-play experience with minimal changes required to start working with Auth0 Platform from the frontend.

Auth0 Platform is a large company, which results in less flexibility in their applications. We encountered a few issues, and when we consulted the community, they did not have answers. We had to modify our workflow to adjust to their current system.

Pricing is a significant issue we faced. As a small company, we need SSO login and other login methods. However, accessing SSO logins requires subscribing to the enterprise plan. Auth0 Platform does not offer basic plans with a few SSO connections that we could try. We must subscribe to a major plan to access most of their features. While this works well for larger companies, for small companies or those conducting POCs, this affects our budget allocation for other initiatives.

Additionally, if we need to serve users in the US, Canada, Europe, and potentially India, we require the ability to keep data in specific countries. Creating multiple Auth0 Platform tenants for data residency requirements is only available in enterprise or higher plans, not in basic plans. Auth0 Platform does not currently have an Indian tenant to serve Indian users. We must use a US or other available tenant and keep Indian user data there. We had a requirement to create an Indian tenant, but since it is not available, we proceeded with a US tenant.

We have been using Auth0 Platform for approximately two years. We received startup credits for one year, and after that program expired, we transitioned to enterprise billing.

We have been using Auth0 Platform for approximately two years. We have not experienced any downtime during this period. Auth0 Platform is already compliant with security and other requirements. We have not encountered any reliability issues, and Auth0 Platform appears reliable for our use case.

Auth0 Platform handles all scaling on their own. We do not need to worry about scaling on their end. We set up our Auth0 Platform tenant, and they handle all logins and scaling. We receive tokens, and how we pass and verify those tokens is what we need to scale from our backend. We can scale our system horizontally. Auth0 Platform is already managed by their team, and we do not need to worry about it. It is a plug-and-play solution.

We spent approximately one or two days setting up the platform. Since then, we have not needed to worry much. Auth0 Platform has been working as expected, and we only need to scale our system. We do not touch Auth0 Platform for day-to-day operations. It is a one-time setup. There might be changes needed based on requirements, but we do not make changes to Auth0 Platform on a day-to-day basis. We do not have to worry about Auth0 Platform operations; we only need to scale our system.

The support team is very good. We faced some issues and raised tickets. Our support team responded immediately and was very responsive. In one instance, a support representative joined a call and explained and resolved the issue. The support team provides immediate support.

We initially conducted POCs with other providers including Cognito and some open-source providers before selecting Auth0 Platform. We chose Auth0 Platform because it provides excellent multi-tenant tenancy support, including creating multiple organizations and having separate users within each organization.

The setup process is straightforward. We used Auth0 Platform SDK and backend support from the community. It required only a few lines of changes to make it work.

We implemented Auth0 Platform workflow with two-step verification using authorization code with PKCE. Auth0 Platform generates automatic verification codes whenever users log in. The verification code is sent again after receiving authorization codes to obtain the actual token, which is an encrypted token. When we pass this token to APIs, we retrieve published keys to obtain token information and signatures, which are verified before we gain access to backend system APIs.

Auth0 Platform is a famous identity provider. When we onboard clients and they ask about our tech stack and security approach, and we mention that we use Auth0 Platform for their login flow, they are already familiar with it. We do not have to explain much about it. This is beneficial when we onboard clients and explain our architecture because they recognize that Auth0 Platform is a large platform with compliance and security measures in place. This represents a good investment.

We used AWS to host the backend system.

We evaluated one open-source tool and AWS Cognito before selecting Auth0 Platform.

If companies have a good budget, they should definitely use Auth0 Platform. However, for small companies with limited budgets, Auth0 Platform's basic plan has limited features, so budget considerations are important. If companies are comfortable with their budget, there are no other issues. For larger companies, Auth0 Platform is a good choice to move forward with.

We spent approximately one or two days setting up the platform. Since then, we have not needed to worry much. Auth0 Platform has been working as expected, and we only need to scale our system. We are satisfied with the solution and do not touch Auth0 Platform for day-to-day operations. It is a one-time setup. There might be changes needed based on requirements, but we do not make changes to Auth0 Platform on a day-to-day basis. We do not have to worry about Auth0 Platform operations; we only need to scale our system. Our overall rating for this solution is 8 out of 10.

A few use cases for Auth0 Platform include using it for authentications and authentication systems and security for good user experience in terms of logging in and logging out into the system and for security itself.

In terms of how I use Auth0 Platform for login flows, once I have the data using the OAuth systems, it is able to come in and come out without having to log in, type in the same passwords or username or having to start the entire process again, which makes it frustrating and does not provide a good user experience.

The main benefits that I have seen from using Auth0 Platform include the fact that above all, for instance, yesterday I was assigned to a UK company that I am supposed to plan the infrastructure for the system that they are coming to do. I was to plan the security compliance and all of that for it. One thing that I would say helped with the planning, with my knowledge of Auth0 Platform, is the fact that security-wise, I am able to configure user data with the limited information that a system is required to use. For instance, I usually use name and email or, for this instance, I want to be using the phone number. With the data that I want to use to validate the person, I have Auth0 Platform to help with the improvement of the security from the streams, how the person uses their data on my platform. I think that also gives the user a good experience. Usually, people get frustrated with consistently having to log in into the system, but with it, I have a more flexible user experience that makes it easier for people to visit my system. One other thing I would say is the SSO, the single sign-on, where you sign in once and that is a very good thing about Auth0 Platform. I would also say it is good for third-party integrations.

The way Auth0 Platform secures APIs, microservices, serverless applications, or containerized workloads in my cloud environment is through the security API integrations. OpenID and OIDC is what helps with the standardized way of validating users and authenticating them into my system. Integrating Auth0 Platform into my own API logic plus third-party integrations is where I serialize, and I have a serialization sequence that validates the user once, through the SSO system. I think it usually depends on the understanding of the engineer on the back end and how they integrate it with their API endpoints to make the experience seamless. Overall, it is easy to integrate with. My first time when I was integrating, I did not have much challenge. Where I had a challenge was where I had to do the cloud setup for the other third parties, but not with the code. Integration-wise, it is fine and easy to use.

The AWS services that I integrate with Auth0 Platform include S3, gateways, and Lambda. I use S3 for the cloud storage, then the rest for whatever they have to do.

The way Auth0 Platform supports my SaaS or multi-tenant architecture running on public cloud infrastructure is surprisingly seamless. All the systems I have been building recently are multi-tenant based, perhaps one or two systems. With multi-tenant integrations, I found it to be one of the seamless integrations I have ever done. Initially, having to manipulate JavaScript to do that requires a lot of code. However, I started with one tenant, an administrator and a customer, then I expanded it to business to business, then business branches, and then I invite members of each or add them back to the system. Configuring the multi-tenant systems on the back end is easy. I just follow the same sequence where I just have to use the business ID, user ID, and the tenant owner ID to just validate if it belongs to this business and if the user's access token is right, then I just give the user access the way I create the normal user in the system. The flow is seamless when I am using multi-tenant. I have used the multi-tenant in that regard for businesses, people, and branches. It was easy and I did not have any challenge on that branch of the workflow.

The industry or customer segment that my application serves is a vertical system. It is a vertical SaaS platform that is developing slowly into a classroom as a service. It serves all industries and is customized for Africa, because I am African. People are using fragmented systems to do their businesses and it does not really promote seamless business transactions and every data is elsewhere. I have a vertical SaaS that cuts across from finance to retail to manufacturing to wholesale to pharmaceuticals and then it continues from there.

The best features in Auth0 Platform include the authorization without sharing your password, the access tokens, and cookies, the way you use the cookies. Refresh tokens on the back end, for instance, when I am validating a user, I think when I use the normal custom approach, I always have to store the tokens in the local storage. Every time I go into the system, the new tokens are generated. With Auth0 Platform, for instance, I can use the cookies to set access tokens and refresh tokens where I give a lifespan based on how I set it. The person can constantly have access to the system without having to generate the tokens all the time over again when they log in. That puts a lot of latency and pressure on the back end and then the data flow within the CPU consumption.

These are what makes me appreciate Auth0 Platform. The refresh token, the access token, and the aspect with Google, signing in with Google for instance. I am a GitHub user, so I use GitHub constantly. When I use GitHub to sign in into Render, and I am going back into it for instance, it gives me access. I do not have to come and input all of those data again, but I am going in straightforward. The main benefits that I have seen from using Auth0 Platform include the fact that above all, when I was assigned to a UK company that I am supposed to plan the infrastructure for the system that they are coming to do, I was to plan the security compliance and all of that for it. One thing that I would say helped with the planning, with my knowledge of Auth0 Platform, is the fact that security-wise, I am able to configure user data with the limited information that a system is required to use. For instance, I usually use name and email or, for this instance, I want to be using the phone number. With the data that I want to use to validate the person, I have Auth0 Platform to help with the improvement of the security from the streams, how the person uses their data on my platform. I think that also gives the user a good experience. Usually, people get frustrated with consistently having to log in into the system, but with it, I have a more flexible user experience that makes it easier for people to visit my system. One other thing I would say is the SSO, the single sign-on, where you sign in once and that is a very good thing about Auth0 Platform. I would also say it is good for third-party integrations.

Regarding improvements or enhancements in Auth0 Platform, if there is anything I would say they should improve, AI has advanced and technology has taken a very big turn, but there is limited education on it. People make a lot of noise about it, but there is limited education on how to use this system. People make noise about AI and we do not know how to use it. Perhaps much more education on how people can actually go about using these systems would be helpful. Or, for instance, if I am a non-tech person or something, but then all of a sudden I find myself in that space with the way AI has advanced, how do I use it? Education, really, is what I would say is needed.

From the features perspective, functionality-wise, when it comes to missing features that I would like to see included or maybe enhanced in Auth0 Platform, I do not think I would add any. All the functionalities, for me as a technical person and how I would think about them, are already integrated. The fact that I can go back to my former login and I do not have to repeat the cycle again, but it is already taking me into it without me having to input the details. From the technical perspective, I am fine with it. Maybe I have not thought about any other improvements that would need to be added, but then currently, in my state, I am okay.

I have been using Auth0 Platform for two years.

When it comes to crashes, downtimes, or performance issues with Auth0 Platform, I would not say it caused them. I did have an issue with a system that crashed because of CPU consumption, but I would not attribute it to Auth0 Platform because it was bad tech configurations on our side. The endpoints were running much more than was needed. We had to adjust what we call tech debt. We had to come and adjust and then reduce the CPU consumption. I would not attribute it to Auth0 Platform that caused it, but it was our configurations that were consuming a lot of CPU. In terms of crashes, I have had my own experience with crashes. It taught us a lot to rectify the situation, but we learned from it. It was not the system, it was us who did the configurations wrong.

In terms of scalability with Auth0 Platform, it is very scalable because for multi-tenant systems, I am able to expand the scope of what I do from one tenant to, for instance, one-to-many, many-to-many, and all of that. I do not have a problem with scaling. Maybe I do not know because my systems have not gotten to that extent to maybe see the performance or how it works under pressure, but from a code perspective and working on it, there was not any challenge at all.

I have not escalated any questions to Auth0 Platform regarding customer service.

Regarding which other solutions I evaluated before choosing Auth0 Platform, I used Kloc, I think. I used it so that it helps with the state management, but then it was not as smooth. There was a lot of configurations I needed to do before I was able to do all of that. I used other state management solutions, a few of them before I finally landed on Auth0 Platform.

When it comes to the key differences, both pros and cons of Auth0 Platform in comparison to other identity management products that I have used, for me, advantage one, Auth0 Platform is seamless and the configuration is okay. I do not need to do a lot to use Auth0 Platform. The other identity management systems, even though they make a noise about it being good and it is actually good to work with, the configurations are quite heavy. I do not have much to say on that, but I feel Auth0 Platform is quite easy to use than the other ones. That is the best way I can put it.

The overall initial setup experience with Auth0 Platform is that my first time, I think to every integration with every new system, it is a try and error approach when it is my first time. Even though I read the documentations and get understanding on how it is implemented, my first time I definitely face a challenge. The more I keep using it and the more the system expands and the more I get familiar with it, integration becomes a normal thing I do every other day. Depending on the logic and how vast the system is and how I want it to be configured, I also have to adapt and then think in that regard. Integrating it for the first time is a try and error thing where every developer goes through that phase. It was not a new thing, so it was not a challenge. It was even easier than some other integrations I do. Once I do it, I get to grasp the concept on how it is done. I just have to adjust the concept to suit the skills of what I am coming to do. It was easy.

The measurable improvements I have seen in scalability, security, or developer velocity within my cloud environment since implementing Auth0 Platform include the fact that initially using the normal way of authenticating people into a system takes a bit longer. For instance, if you are using 500 milliseconds, one of the things I would say about Auth0 Platform is it reduces the time, the seconds by which the authentication processes go fast. I would attribute it to the fact that there is improvement because authenticating people into a system takes a few seconds, knowing that connecting to the databases and because everything is on the cloud and it is connected, it makes it easier for me to integrate and authenticate somebody into a system. The time, the latency periods have been reduced drastically. On that aspect, there is improvement.

The experience with the pricing aspect of Auth0 Platform is that when it comes to pricing, I would make reference to AWS, it is pay as you go. The number of things I use is what I pay for. On that regard, it is good. It is quite expensive but security-wise, I am secured. I know that my data and my information are well protected. I feel that it is better as a startup and to the experts also, it is better to invest into what will make you secure than to not invest into what causes you pain. When your data gets breached, you are coming to invest double the money you would have invested into what could have kept you safe. When it comes to pricing and systems, from my understanding, I feel that it is better to invest the right cost than to come and double the investment because of security breaches or something.

One piece of advice or recommendation that I would share with other organizations considering Auth0 Platform is that security is very important. In as much as in Ghana, for instance, the awareness is limited, security is very important to a system. When your security is not good and it has been breached, it costs you a lot to rectify it, more than you would spend to have a very good security system. Organizations should really be intentional about using systems like Auth0 Platform to be able to implement good security infrastructures to secure their systems, like the RBAC solutions and all of those things.

When it comes to using Auth0 Platform to secure AI-powered, GenAI, or agent-based applications, I have not done any of that yet.

My overall review rating for Auth0 Platform is 8.

We generally use Auth0 Platform to provide identity provider services to our customers who are not part of our domain, such as when we work for different clients. For one client, Auth0 Platform was already in place, so we used it to onboard users and applications. External users with domains such as gmail.com or facebook.com were onboarded to Auth0 Platform, and we provided access to them through that platform. We also onboarded a few applications there for those purposes.

Currently, we are not using Auth0 Platform to secure artificial intelligence-powered, generative AI, or agent-based applications. We have only used it for external applications and some internal applications.

Auth0 Platform serves an insurance industry client, specifically an insurance company, with an HR portal, a few portals that the security team uses, and several insurance portals. They use Auth0 Platform for security and as their identity provider.

Auth0 Platform's best features include a great graphical user interface. When any new user who has never used Auth0 Platform previously arrives and has any knowledge in identity and access management, they can easily navigate through the portal and use it without needing any prior training for beginner-level work.

The impact on our company has been positive. If we were to use Entra ID or any other identity provider that we evaluated, we would need to onboard users to our platform and create mail domains or invite them as guests. With Auth0 Platform, integration and providing access to external users, not just organization users, was much easier. Managing users was also easier, and this tool has a great graphical user interface, making it easier for us to check logs if users are facing any issues. Providing any access was also easier and quite smooth.

The biggest return on investment for me using Auth0 Platform is that, compared to Okta, which is an identity provider with a good reputation, Auth0 Platform was a new product. Compared to SailPoint or CyberArk, Auth0 Platform's graphical user interface is quite user-friendly, very easy to use and integrate, and also easier to learn.

Regarding improvements for Auth0 Platform, during the last time I used it, I observed that during log analysis or when using the search or filter options, I missed some features. If I went into Entra and tried to filter to find a log, those filtering features are missing in Auth0 Platform, which I felt could be improved. Additionally, providing users with access to applications was not that easy to navigate, and it was difficult to see which user has which application access. If that could be improved, Auth0 Platform will be more user-friendly.

I rate Auth0 Platform an eight, not a ten, because although it offers a great user experience, there are still some aspects to improve. During log analysis, it is not quite easy for us to see if a user has access to applications or which user is facing any issues, so those filtering features are missing. That is why I rated it eight; otherwise, I would have rated it ten out of ten.

I have been using Auth0 Platform for the last three years, from 2020 to 2025.

During my tenure working with Auth0 Platform, I never saw any kind of lag or Auth0 Platform portal going down. We never faced any challenges due to Auth0 Platform. Unlike Azure, where I have seen outages many times, with Auth0 Platform, I never experienced such issues in the last few years.

Regarding the scalability of Auth0 Platform, the number of users does not matter. As we continue to increase the user count, Auth0 Platform supports it and does not lag. It will support 2,000 users, and we can even onboard more than 2,000 users and work with them smoothly. Users can authenticate through the platform and get authorization to use authorized applications. There are no issues with scalability; Auth0 Platform is very good in this regard.

We never reached out to customer support, as our team did not handle that. Our client dealt with customer support, so I do not have much insight into that area.

I am not sure what solution was being used before Auth0 Platform because Auth0 Platform was already in place when I joined. In other clients, I observed they were using on-premises Active Directory and Entra ID for identity provider services, but in this case, I saw they are integrating Entra ID, Active Directory, and Auth0 Platform as one system. This allows internal users to get authenticated through Auth0 Platform, and external users are also authenticated through Auth0 Platform.

Auth0 Platform's initial setup was not very complex. It was easier compared to other products because it functions as software as a service. We registered it on Entra ID as an application and then started using it.

I am not sure about the help for setup from an integrator, reseller, or consultant, but I see many integrators available. However, I never used any.

The biggest return on investment for me using Auth0 Platform is that, compared to Okta, which is an identity provider with a good reputation, Auth0 Platform was a new product. Compared to SailPoint or CyberArk, Auth0 Platform's graphical user interface is quite user-friendly, very easy to use and integrate, and also easier to learn.

Before choosing Auth0 Platform, I mainly evaluated CyberArk, which is a great product but its graphical user interface is not quite user-friendly. For anything I need to check, I often have to search for where this option is or what I have to do, and it is integrated into one portal, which makes it difficult to remember where everything is. In contrast, with Auth0 Platform, I see everything clearly on the left-hand side menu, and I can navigate without confusion. This is a significant advantage.

Currently, in our environment, we are using mostly all the applications on on-premises servers, and they are getting migrated to cloud, which is Red Hat OpenShift, and they are in pods. I am not sure if all are migrated because when I was working, the migration was in progress.

We had four environments deployed: user acceptance testing, production, test, and development. We used to onboard applications for these environments to the different tenants of Auth0 Platform. The application team performed different testings per their environments, and then we deployed them to production. Auth0 Platform's multi-tenant option was available, which made it easier to deploy different environments of the application in different tenants. It was easier for us to segregate and manage because if any application team did not know their tenant ID or any other details they needed, we could easily provide that information due to the multi-tenant capability in Auth0 Platform.

After implementing Auth0 Platform, I have seen measurable improvements in scalability, security, and developer velocity with our cloud environments. It was easier for us to scale our applications to external users. Through Entra ID, we were required to onboard users through guest invites or inviting them to our tenant, which made it difficult to manage all external and internal users in one tenant due to architectural-level challenges. After integrating Auth0 Platform, everything was segregated. Internal users remained in Entra while external users were directly on Auth0 Platform. This made management straightforward. If we need to work on any external users, we can just log into Auth0 Platform and manage them without worrying about duplicating actions on internal user IDs. Those issues never occurred after implementing Auth0 Platform.

Overall, I rate Auth0 Platform an eight out of ten.

Auth0 Platform's main use case is to serve as an identity provider for all the applications that users want to access. This enables achieving single sign-on, multi-factor authentication, migrating users, and keeping them stored safely.

Auth0 Platform secures external API calls during the authentication flow through a feature called Action Secrets. When you write custom Node.js code to extend the login process via Auth0 Actions, you use Action Secrets to securely store and inject API tokens or sensitive credentials so they are not exposed to potential attackers.

The main benefit that Auth0 Platform brings to the table is security. Everyone knows they are investing a lot in their security, keeping the product up to date and improving it consistently. The other benefit would be the ease of use and the total amount of features offered.

The best features in Auth0 Platform are Forms for Actions. They are a standout feature that allows you to seamlessly collect additional information during the onboarding process and save that data directly inside the user profile. Advanced customization for Universal Login is another great feature that was recently launched, allowing businesses to fully customize and host the login pages themselves.

Auth0 Platform supports SaaS or multi-tenant architecture running on public cloud infrastructure through the Organizations feature. This is a really helpful feature that allows you to achieve multi-tenancy inside one tenant to support complex multi-organization structures.

Regarding areas for improvement, Auth0 Platform is a premium product, and its pricing reflects its enterprise-grade capabilities. While the cost can sometimes make smaller businesses hesitate, the return on investment usually outweighs the initial price tag when the platform is architected and implemented correctly. The comprehensive feature set, top-tier security, and reduced development time justify the investment for organizations prioritizing scalability.

On the technical side, I would like to see Auth0 introduce more no-code branding options for Universal Login. Currently, achieving a highly specific, bespoke login experience often requires utilizing Liquid page templates or the newly released Advanced Customizations for Universal Login. While these are incredibly powerful tools, they do require some technical expertise to execute flawlessly. Having more robust, out-of-the-box customization options would be a great enhancement in the future.

I have been working with Auth0 Platform for the past three years. However, this isn't just occasional use—it has been my primary, full-time focus. I have spent eight hours a day, every single working day, actively architecting, implementing, and navigating the platform for various enterprise use cases.

In my experience architecting and implementing identity solutions, Auth0 Platform's stability has been exceptional. I have not encountered any downtime, latency spikes, or reliability issues so far.

Because authentication is a mission-critical component of any application, high availability is entirely non-negotiable. Auth0 consistently delivers on that front, providing a highly robust and resilient infrastructure that ensures seamless, uninterrupted access for end users.

Scalability is undeniably one of Auth0 Platform's strongest points. It is built to scale effortlessly, capable of supporting anywhere from thousands to hundreds of millions of users without compromising performance, even when utilizing its more complex identity features.

While I don't share specific client telemetry, the positive impact on developer velocity, security posture, and system stability within cloud environments is immediately noticeable post-implementation. Because Auth0 handles the immense infrastructure load behind the scenes, organizations can confidently scale their user bases without worrying about authentication bottlenecks.

The technical support and customer success teams at Auth0 Platform are consistently exceptional. Over the past few years, I've found their approach to be highly proactive; they frequently offer to jump on a call to discuss support tickets in depth rather than relying solely on back-and-forth emails. As an architect, having the ability to screen-share complex tenant configurations directly with their team is invaluable for rapid troubleshooting.

Furthermore, Auth0 provides a highly effective escalation path. If a unique technical edge case arises, support can seamlessly loop in the core engineering team, ensuring you get assistance directly from the people building the product. Because of this high-touch, expert-level service, I give Auth0 Platform's technical support a solid nine out of ten.

Positive

In addition to Auth0 Platform, I have experience working with Keycloak, which is an open-source identity option, as well as Okta Workforce Identity Cloud (WIC). While I have evaluated and utilized these other solutions for different identity use cases, my current primary focus and technical expertise remain dedicated to Auth0 Platform.

The initial setup of Auth0 Platform is highly straightforward. For standard identity flows, anyone with baseline IAM (Identity and Access Management) knowledge can have a functional configuration up and running very quickly, greatly aided by Auth0's exceptional, well-structured documentation.

However, because Auth0 is an enterprise-grade solution with a vast array of extensibility features, there is naturally a steeper learning curve to master the entire platform. This complexity is entirely appropriate given the depth of functionality provided. While getting started is fast, fully optimizing the architecture and leveraging advanced capabilities—like custom Actions and multi-tenant Organizations—takes time and dedicated expertise.

The return on investment with Auth0 Platform is substantial and can be categorized into two main areas: user experience and risk mitigation. On the experience side, providing a frictionless and secure login journey directly translates to better user retention and fewer support tickets. Additionally, by offloading complex identity infrastructure to a fully managed service, development teams save countless hours that can be redirected toward building core business features.

However, the most critical ROI comes from security and risk avoidance. If a company suffers a data breach, any money saved by utilizing cheaper, less secure tools is instantly negated by reputational damage, potential compliance fines, and customer churn. Investing in an enterprise-grade platform like Auth0 is essentially investing in the long-term trust and safety of your user base, which provides the ultimate return on investment.

As an identity consultant, my primary focus is on the technical side of the platform—specifically architecture design, technical reviews, and hands-on implementation. Because of this role, I am not typically involved in the commercial negotiations or direct licensing agreements with Auth0.

However, from a setup perspective, the technical onboarding is very straightforward. The platform provides excellent documentation and a logical structure, which significantly reduces the developer hours required to get up and running. By minimizing the time spent on complex custom coding, the overall technical setup costs are kept highly efficient for the business.

Before fully focusing on Auth0 Platform, I evaluated a few other solutions, including OneLogin, Amazon Cognito, and Keycloak.

While each has its merits, they didn't quite fit the broader requirements. OneLogin leans heavily toward workforce identity, Amazon Cognito lacks flexibility in UI customization, and Keycloak—while a great free open-source option—requires significant operational overhead to host and maintain the infrastructure yourself.

Auth0 Platform ultimately stood out because it delivers a fully managed, highly extensible, and future-proof SaaS experience. It completely removes the maintenance burden while offering superior, developer-centric customization, which is why it remains my primary focus.

I rate Auth0 Platform a solid nine out of ten. For organizations considering the platform, my advice is to confidently move forward with it, especially if you are looking for an identity architecture that is built to last.

From an integration standpoint, it works seamlessly with enterprise identity providers like Azure AD, making it highly adaptable for various business environments. Ultimately, Auth0 is scalable, secure by design, and equipped with all the features a business might need as it grows, making it a truly future-proof solution.

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.

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.

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.

I have been using Auth0 Platform for about two to four years.

Auth0 Platform is stable.

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.

The customer support for Auth0 Platform is fast. The customer service is fast, and they are always there to help.

Before choosing Auth0 Platform, I evaluated other options, including Clerk. I decided on Auth0 Platform, but then I switched from using Clerk.

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.

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.

We adopted it at the enterprise level as a reliable authentication solution for our Java Spring Boot-based API, and it has been a meaningful part of our backend security stack for a considerable time.

Our main use case for Auth0 Platform has been API authentication and authorization. We use it to secure our backend API built on Java and Spring Boot, including issuing JWT tokens, validating them on incoming API requests, defining scopes and permissions for different services, and managing role-based access control across our microservice architecture.

In one of our enterprise projects, we have multiple Spring Boot microservices that needed to communicate securely with each other and also serve authentication requests from a frontend application. We integrated Auth0 Platform to act as the central authorization server. Whenever a user logged in, Auth0 Platform would issue a JWT access token. Each of our microservices would then validate that token on every incoming request, checking the signature, expiry, and the specific scopes attached to the token to decide whether to allow or deny access. This made a significant difference because before Auth0 Platform, each service was handling authentication independently, which was messy and inconsistent. Auth0 Platform gave us one centralized place to manage who has access to what, and rolling out new permissions or restricting access became a configuration change in the Auth0 Platform dashboard rather than a code change across multiple services.

We also used Auth0 Platform for machine-to-machine authentication, not just user-facing authentication, but also service-to-service communication within our microservices. Each service had its own client credentials and would request tokens from Auth0 Platform independently, which kept things secure even internally. We also leveraged custom claims in JWT tokens, embedding user roles and permissions directly into the token payload. This meant our downstream services did not need to make extra database calls to check permissions because they could read it straight from the token, which improved performance. While the setup for all this was well-documented initially, managing token expiry and refresh cycles across all these services in production is where we had to do a lot of custom handling, which is the one area where Auth0 Platform could improve its enterprise-level guidance.

From my experience, the dashboard and management UI is genuinely one of the best in this space. Managing users, checking logs, setting up APIs, defining roles and permissions—everything is accessible and intuitive. It saved our team a lot of time that we would have otherwise spent writing admin tooling ourselves.

Auth0 Platform handles token signing, automatic key rotation, HTTP enforcement, and brute force protection by default, providing security out of the box. As a developer, I do not have to think about whether my security fundamentals are correctly implemented. Auth0 Platform takes care of that, which is a big deal in an enterprise context.

For a tool this complex, the documentation is surprisingly good. The Spring Boot quickstart guides got us up and running fast, and the concept docs around JWTs, scopes, and grants are well-written.

In all my time using Auth0 Platform in production, we never had a significant outage that impacted our users for authentication, which is literally the front door of our applications. That reliability is non-negotiable, and Auth0 Platform delivered on it consistently.

Auth0 Platform had several meaningful positive impacts. The biggest one was speed of development. Before Auth0 Platform, every new service or application we built had to implement its own authentication logic, which is a significant amount of work and more importantly, is error-prone. With Auth0 Platform, we essentially removed that burden entirely. New services could be secured within hours rather than weeks.

Auth0 Platform gave everyone a single, consistent way to handle authentication and authorization across our organization. In a large enterprise with multiple development teams working on different services, that consistency reduced bugs, made code reviews easier, and made onboarding new developers much faster because they only had to learn one auth system.

In an enterprise environment, security audits are a reality. Having Auth0 Platform as our auth layer meant we could point auditors to an SOC 2 certified, industry-standard platform rather than trying to defend our own custom auth implementation.

We did not have to worry about rotating keys, patching auth vulnerabilities, or managing certificate renewals. Auth0 Platform handled all of that, which freed our team to focus on actual product features rather than infrastructure maintenance.

The number one area I want to see improved is token and session management documentation for complex enterprise environments. The quickstart guides are great for getting started, but once you move into a microservice architecture with multiple services, token expiry, refresh token rotation, and session handling across services, the documentation gets thin. We had to figure out a lot of edge cases on our own through trial and error, which cost a significant amount of time.

When a token validation fails in production, the error messages are often vague. Something such as 'invalid token' does not tell you much. Is it expired? Is the signature wrong? Is the audience claim mismatched? More descriptive error responses would save developers hours of debugging time.

As your user base grows, Auth0 Platform pricing can become a concern in an enterprise context. I would love to see clear pricing tiers and better cost predictability for large-scale deployments so organizations can plan budgets more confidently.

The machine-to-machine use case is very common in enterprise environments, but the documentation around it, especially for edge cases, could be significantly more detailed. More enterprise-focused guides around microservices and machine-to-machine authentication would be beneficial.

I have been using Auth0 Platform for around eight to nine years.

Customer support is really good. Every time I created an incident and reported issues, they were tackled properly, and the services are excellent.

From a pure engineering effort perspective, the setup cost was quite reasonable. Auth0 Platform offers a generous free tier that we used during our proof of concept and development phases.

Auth0 Platform pricing is primarily based on monthly active users, or MAUs. In the early stages, this worked well for us because our user base was manageable. However, Auth0 Platform can get expensive at scale. For large enterprise deployments with tens of thousands of monthly active users, the costs rise considerably. There were internal conversations within our organization about whether the cost was justified compared to alternatives or even building an in-house solution.

Before Auth0 Platform, setting up a secure authentication system for a new service from scratch would typically take one to two weeks when you factor in implementation and testing. With Auth0 Platform, we got this down to two to three days. We are talking about saving weeks of engineering time per service, and we had multiple services, so that adds up significantly.

I have always used Auth0 Platform. I chose Auth0 Platform directly because I heard it was good.

I advise organizations to go through the initial documentation, use the free tier plan, and start with a proof of concept before committing. Auth0 Platform's free tier is generous enough to build a meaningful POC. Organizations should do a realistic cost projection before signing an enterprise contract. My overall rating for Auth0 Platform is 9 out of 10.

I work with Okta, and I also work with SailPoint, Veza, and IBM tools because I am overseeing many sales engagements, and I must deal with many tools. We are a service company, and we offer different kinds of products to our clients.

For example, there is an enterprise customer XYZ Corporation using Microsoft Azure AD as an IDP, who logs into a multi-tenant HR application through an Auth0 tenant managing connections, RBAC, and tokens. The user visits the HR application and logs in with their email, Auth0 redirects them to Azure AD for authentication, which sends tokens back to Auth0, allowing the user to access the HR app with the roles assigned.

Working on Veza at this stage includes preparation for migrating systems; I will begin this process in the coming months after thorough research and planning.

Auth0 Platform from Okta, which is for access management and single sign-on, is basically for dividing modern IM into categories. The first is workforce identity, meaning SSO and access management solutions for users, partners, and temporary employees, which is catered by a traditional Okta Platform. Customer identity speaks about internet application customers, such as logging into an FMCG application through mobile or laptop applications like Flipkart, Amazon, and Alibaba.com. If security is needed for these applications, it is called customer identity and access management solution, CIAM, and requires a different tool because the user base will be in millions or billions. For instance, banking apps and airline applications fall under CIAM solutions, and Auth0 Platform will be implemented for these requirements.

Most integrations will not be done by traditional connectors but by exchanging metadata between the application and Auth0 Platform. Once metadata is exchanged, certificate information and cryptographic keys are also exchanged, making transactions secure. Different methodologies for onboarding users are available, including bulk onboarding and risk score features. If someone logs into a banking app normally from the UK, but they log in from Namibia after stealing a mobile phone, the application detects this change of location as a zero trust model. Policies such as restricting app access based on location can also be implemented using Auth0 Platform, along with self-service user registration features similar to opening a bank account.

Universal login, while I do not think it has a major impact, allows a seamless experience by authenticating multiple app logins from one entry point, which would be particularly useful in healthcare applications.

Auth0 Platform is quite affordable compared to IBM Security Access Verify, which is on the higher end. ForgeRock and Okta are in the same bucket for pricing.

Auth0 Platform is not as flexible compared to ForgeRock or IBM Security Access Manager.

Auth0 Platform will only play on the outer boundary of the application. Once the application team requests to handle their entire system and APIs, then only ForgeRock and IBM Security Access Manager can help; Auth0 Platform cannot assist.

The only area for improvement is that Auth0 Platform cannot handle requests for developing APIs for legacy systems, such as mainframe models, where ForgeRock and IBM Security Verify Access can be utilized.

I have been dealing with Auth0 Platform for more than one year.

I have not experienced any downtime with Okta; in the last one and a half years, including production environments with higher availability setups, the systems ensure uptime.

Auth0 Platform is very scalable, and Okta handles CI/CD deployments effectively to adjust to needs.

Using enhanced features improves multi-tenant management for B2B SaaS.

Customer support from Okta is quite good; I know people personally, and their learning portal is also effective. They need to hire more resources, though, especially as they expand products. Okta is capable of being competitive but is limited due to resource constraints.

I would rate their customer support a nine; I have not seen any complaints.

Positive

I have been working recently with Veza through a client looking to replace SailPoint. Veza, acquired by ServiceNow, offers an IM solution at a lower cost by bundling it with the ServiceNow license.

Auth0 Platform is SaaS based. They spin up a tenant for me upon deal closure, and I can access it immediately, establishing different roles for administrative and user purposes to start implementation without delay.

I can enable attack protection in Auth0 Platform, which protects applications from automated attacks such as brute force, credential stuffing, and password spraying by analyzing various detection signals including IP reputation and suspicious login velocity. If a risk is detected, Auth0 Platform can trigger mitigation actions such as blocking requests, initiating captcha challenges, throttling login attempts, and sending logs to SIEM systems.

Regarding ROI with Auth0 Platform, they offer various subscription plans including free basic options for a few hundred users, but comprehensive ROI reflects better with the full Okta platform, which is robust in providing a unified security solution. Okta is unique in offering comprehensive services including single sign-on, IGA, privileged access, and endpoint security, making it a worthwhile investment compared to deploying multiple vendors.

Auth0 Platform is quite affordable compared to IBM Security Access Verify, which is on the higher end. ForgeRock and Okta are in the same bucket for pricing.

Veza's entire SDK is built on Python, which enhances integration capabilities with AI tools and chatbots. As the market shifts toward cost-effective solutions, especially in expectation of an economic slump, Veza is positioned to gain traction.

Auth0 Platform will only play on the outer boundary of the application. Once the application team requests to handle their entire system and APIs, then only ForgeRock and IBM Security Access Manager can help. Auth0 Platform cannot assist, making Auth0 Platform slightly better in terms of user migration.

Detecting automated traffic is vital for security measures, as it provides end-to-end security. It protects login and signup endpoints and deals with attacks through various implementations, including breach detection.

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.

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.

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.

I have been using the solution for almost three years since 2023.

I rate the stability at ten. It is definitely stable; I have not had any issues at all.

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.

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.

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.

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.

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.

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.

I am using Auth0 Platform while developing our application for securing it. We are using Auth0 Platform for multi-tenancy work, creating users, and generating tokens. I am using it for authentication and authorization for my web application.

All microservices we are deploying on the cloud use GitHub to store all repositories and Azure to deploy. We create Docker containers and push our microservices code and images there. All of those things are connected with Auth0 Platform and work very well. There are no issues with Auth0 Platform, Docker, or microservices, and all integrations are working fine.

We are not doing agent-based applications yet, but it is in our application's next scope. In a couple of months, we will integrate and develop the feature to use Auth0 Platform with an AI agent.

Our application serves the retail segment with inventory management. We are selling different items on platforms such as Amazon, eBay, and other marketplaces at the enterprise level.

There are many features in Auth0 Platform. Sometimes when we consider other tools instead of Auth0 Platform, we cannot get everything in one place. In Auth0 Platform, if I want to do authentication and authorization using Google or single sign-on or Okta or different providers, I can do that there. I can customize my login page, and there are built-in features. I just need to use the default feature that is free, but for customization based on my needs, I need to pay. For default features, many platforms do not provide even the default feature, but Auth0 Platform has free features. I can maintain different connections to utilize multi-tenancy in my application, where different organizations are connected with different connections and all users are stored in that particular connection database only. Auth0 Platform even provides the opportunity to connect with my local database and store all user details there. Many features are available in Auth0 Platform, and I am utilizing all the features available.

Earlier, I was also doing authorization and authentication, but I had to write a lot of code such as writing classes, generating tokens, and saving details. I also needed to create APIs to manage these things. However, with Auth0 Platform, different management APIs are already available. I need to generate a token and call those APIs. All of those things are handled from Auth0 Platform's side. I am just calling a certain API, which saves a lot of time from the development perspective while providing many features. This allows me to secure my application more efficiently. These are the benefits I am getting from Auth0 Platform.

I previously used Google provider and Okta separately, but I find everything with Auth0 Platform in one place. Key differences include time-saving features, everything in one place, many features, support for multi-tenancy, and management APIs for easy integration. All of these are advantages, and I have not experienced any disadvantages.

There have been many improvements in our cloud technology since we are using Auth0 Platform. It is helping a lot. The main thing is that it reduces our development time while providing many features to integrate and utilize. We do not have to include dependencies from multiple providers. Everything is available in one place with Auth0 Platform. We are utilizing it to develop our application faster, which minimizes our time and maximizes utilization.

I noticed some enhancement challenges. Sometimes when I logged in, there was a thirty-day time period to log in again, but recently after restarting my system, that thirty-day period is not working. I need to provide the token after login again, which is for the security part. For development accounts used by others, every time we need to use those tokens to connect to that site. UI improvements can also be made, particularly on the homepage, where tiles could be displayed. It would help if there were separate left bar tiles for the login section so anyone could edit their login page directly.

Everything is working very well. However, when integrating, I need to give permissions and manage many things manually when creating users with multi-tenancy. For instance, I first create the connection, then the organization, enable the connection at the application level, allow some permissions, and create the default user. Improvements could be made so that when someone creates an organization, a default user is available from Auth0 Platform to log in, and they could use those credentials to create further users. This is also dependent on functionality and user requirements. For my use case, that was lacking.

The initial setup was somewhat complex. Since I was doing it for the first time, I needed to create an application, allow permissions, integrate it, and set redirect variables and URLs for logout. Although documentation is available, it does not specify the exact format for multiple logout URLs or multi-tenant URLs. Sometimes I had to try different methods until it worked. Improvements in documentation are needed for first-time setups.

When connecting with Auth0 Platform, if there is a failure or error, I do not receive a specific message to identify if it is a bug or another type of issue. I suggest having clearer error messages, such as indicating what is missing or providing expected formatting for values.

I have been working with Auth0 Platform for the last one year.

When connecting with Auth0 Platform, if there is a failure or error, I do not receive a specific message to identify if it is a bug or another type of issue. I suggest having clearer error messages, such as indicating what is missing or providing expected formatting for values.

I previously used Google provider and Okta separately, but I find everything with Auth0 Platform in one place.

The initial setup was somewhat complex. Since I was doing it for the first time, I needed to create an application, allow permissions, integrate it, and set redirect variables and URLs for logout. Although documentation is available, it does not specify the exact format for multiple logout URLs or multi-tenant URLs. Sometimes I had to try different methods until it worked. Improvements in documentation are needed for first-time setups.

I did the initial setup and integration by myself without any integrators or consultants.

The pricing is good for now because I am using the developer account. I will evaluate the production account next week to see what features I need and check the pricing based on that. For now, I am utilizing mainly default features, but I customized the login page, which incurs some pricing. However, it is manageable.

I evaluated a couple of options, but I chose Auth0 Platform because it looks very good to me.

Everything is good for me now, and I have no additional recommendations. I would rate this review ten out of ten.