Sign in Agent Mode
Categories
Your Saved List Become a Channel Partner Sell in AWS Marketplace Amazon Web Services Home Help

Auth0 Platform

Okta, Inc

Reviews from AWS customer

8 AWS reviews

External reviews

265 reviews
from and

External reviews are not included in the AWS star rating for the product.


    Amit Sethi

Identity platform has secured our cloud APIs and now protects AI and microservices reliably

  • March 24, 2026
  • Review from a verified AWS customer

What is our primary use case?

We are a review website for enterprise IT. We publish reviews for other people to read, either publicly or anonymously, and we also work directly with vendors. The vendors for Auth0 Platform are Okta, and we are working with them. They read these reviews to better understand what is right and what is wrong with their product.

What is most valuable?

Our main idea is to help vendors understand their product better through direct feedback from users.

For how long have I used the solution?

How long have you been working with Auth0 Platform?

How was the initial setup?

The deployment of Auth0 Platform is straightforward.

Which other solutions did I evaluate?

I have used other alternatives aside from Auth0 Platform.

What other advice do I have?

Auth0 Platform secures APIs, microservices, serverless applications, and containerized workloads in our cloud environment. We use Auth0 Platform to secure AI-powered and generative AI applications, as well as agent-based applications. AWS services including Lambda, API Gateway, ECS, EKS, and DynamoDB integrate well with Auth0 Platform.

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)


    Nate B.

Critical Issues Overshadow User-Friendly Interface

  • March 24, 2026
  • Review provided by G2

What do you like best about the product?
I find Auth0's UI very easy to navigate and use, which made onboarding and configuration very easy. Their user management for my customers via a SaaS model is very powerful and extremely useful for triaging authentication issues with our applications. The initial setup of Auth0 was very easy.
What do you dislike about the product?
Their support is the worst of any software vendor I've ever had the displeasure of having to engage with. They don't have any support route if you are locked out of your account, forcing you to create a new account to even create a support ticket to try and get access to your official tenant account. Their own authentication service is also broken very badly as if you use a federated login option without ever setting a password, then no longer have access to those federated service(s), you are permanently locked out of your account. There is no way to do a password reset if you simply never had a password set on your account. Their official support response was to simply re-create everything with our new account we used to open the support ticket originally. We abandoned them for this.
What problems is the product solving and how is that benefiting you?
Auth0 saves us from building and maintaining our own auth solution. Its user management is powerful for handling auth issues, and the UI makes onboarding and configuration easy.


    Elisa F.

Identity management we built once and never had to rebuild

  • March 20, 2026
  • Review provided by G2

What do you like best about the product?
The speed at which we got secure authentication running across our applications was genuinely surprising for a team that had previously attempted to build auth in house. Social login enterprise SSO and MFA were all live within days rather than the weeks we had budgeted for. The documentation is thorough enough that our developers rarely needed to go beyond it which kept the integration work moving without constant blockers.
What do you dislike about the product?
Pricing scales up faster than expected once user volumes start growing and the jump between tiers is noticeable.
What problems is the product solving and how is that benefiting you?
Building and maintaining authentication infrastructure internally was pulling engineering time away from product development on a consistent basis. Every time a security requirement changed or a new integration was needed it landed on our core engineering team as unplanned work. Auth0 absorbed all of that complexity and gave us a stable identity layer that our team does not have to think about anymore which has had a compounding effect on how much product work actually gets shipped each quarter.


    Sargam Panwar

Centralized authentication has improved security, streamlined roles, and accelerated testing

  • March 19, 2026
  • Review provided by PeerSpot

What is our primary use case?

I have been using Auth0 Platform for more than a year for authorizations, login, and sign-up functionality in my application for my current project.

My main use case for Auth0 Platform involves registering all existing users to Auth0 and onboarding new companies and users, which all feed into Auth0. When I need to update any organizational units, such as the name or trading name, I use Auth0. If I need to change the MFA for any existing user or to check roles and permissions granted to a particular user, I use Auth0.

As a software engineer, I do not use Auth0 that often; I work with the basic, generic flow which I have already mentioned. The developers in my company would use Auth0 on a day-to-day basis. I have used it to handle login, signups, and user identities, so it is a nice tool to work with.

What is most valuable?

Auth0 Platform offers good security features, such as MFA, and the role-based access that can be granted to users is easy to manage with a dropdown and simple access to different permissions and roles. There were times when there was an issue logging in a user, so I had to reset the MFA, and it was straightforward, taking less than a second to complete. These three features are particularly valuable.

The role-based access feature impacts my daily tasks the most because when we onboard a new company, that company needs to be approved by the company admin user. If the user does not have those rights, then the new company would not be able to perform any other task in the product. The role feature was a major breakthrough and was straightforward to use.

The measurable improvements I have seen since implementing Auth0 include faster feature deliveries for developers with fewer auth-related bugs. We have never been uncertain regarding user security, and the traffic has been great without downtime. Auth0 provides 100% centralized authentication, which reduces unauthorized access. The MFA adoption increased by 60 to 70%, and automation shifted from UI-based to token-based authentication using Auth0, reducing test execution time by 20 to 30% and eliminating most flaky tests related to login flows. After migrating to Auth0 from a custom authentication system, we noticed substantial improvements in developer productivity, auth-related implementations, and reduced login flow flaky tests.

What needs improvement?

I find the process of managing roles, permissions, or MFA changes in Auth0 to be straightforward; it has a very user-friendly UI. However, at times I find it difficult to understand the role. In my previous experience a couple of months ago, I checked and the permissions assigned to the user were not working, but then I had to update it by going to its company and then providing the particular permissions. That was one thing I found as a limitation of Auth0, but apart from that, Auth0's UI is very user-friendly and easy to navigate.

I think additional documentation would be beneficial for Auth0.

Now that I am switching into automation, token handling is needed from Auth0, as well as session handling and error handling with invalid and expired tokens. A better layout or a better way to handle those would be helpful. Additionally, improvements can be made around the authorization code flow, refresh tokens, and expired tokens.

What do I think about the stability of the solution?

Auth0 Platform has been highly stable and reliable in my experience; I have never faced downtime or technical issues. It handles increased loads and more users very well, and there may be occasional minor issues, but those are rare and do not significantly impact users. Overall, the platform has proven to be dependable and highly scalable, successfully managing increased traffic due to its stateless JWT-based authentication.

How are customer service and support?

I personally do not reach out to Auth0 Platform customer support because developers or the customer support team handle that for us. However, in minor cases, we did reach out, and they were proactive in replying and helping us. My experience was good.

What other advice do I have?

Security incidents related to the companies and users we onboarded were an issue, as they were not able to access the platform. Debugging that using Auth0 Platform was very effective, and we previously were not using one of the features of Auth0 Platform, but now we are using it and really enjoying it.

My advice for teams considering Auth0 Platform would be to clearly understand the authentication and authorization requirements before implementation. Auth0 Platform is a powerful tool, so it is essential to configure it correctly and use it wisely, especially around token usage, roles, and security policy. I would recommend investing time to understand Auth0 Platform 2.0 and JWT flows. From a testing and performance standpoint, using token-based authentication instead of UI can significantly improve automation speed and reliability. Overall, I believe Auth0 Platform is a great choice, but it should be implemented thoughtfully with proper planning in mind. I would rate this product a 9.


    Ashish Jha

Identity platform has simplified social logins and has accelerated travel app development

  • March 16, 2026
  • Review from a verified AWS customer

What is our primary use case?

My use case is mostly identity management. I used Auth0 Platform to build my personal projects, and they have a very good free tier, so I just use Auth0 Platform to add identity, such as login boxes to my apps.

The industry that my applications serve is travel-related, so it is mostly for end users, not a B2B application. I am building a trip planning app, and it will be a travel industry application.

What is most valuable?

The best features in Auth0 Platform are the social login aspect because they have a lot of out-of-the-box integration and also they have something called Actions, which allows doing different file logins in itself. Actions is another feature I really appreciate.

The secure APIs, the microservices, the serverless applications, and the workloads impact my cloud environment because most of the hosting is done on Auth0 Platform itself, and the Actions I mentioned is where I can write microservices to connect to my other APIs or my backend system, providing quite an intuitive interface. They use JavaScript, which is the language I am also familiar with, so that makes it easy.

The measurable improvements I have seen in scalability, security, and velocity since implementing Auth0 are mostly that I don't have to worry about adding new features because a lot of features are available out of the box when it comes to identity-related features. Rather than me thinking about how to build it from scratch, I just have to search whether this is something supported by Auth0, and more often than not, the answer is affirmative, and then I just have to find out how to enable it and it is done.

What needs improvement?

In Auth0 Platform, one area that has room for improvement is on-premises deployment because one major thing that I see some other vendors do is give on-premises deployment, basically allowing me to have my own version of Auth0. Auth0 currently does not offer that; it is just a SaaS offering. That is something they could add, but other than that, they cover most of the boxes for my requirements.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

I find it scalable for my business. So far, so good, as I have not had any issues and I do not think there will be scalability issues because they offer a free tier for twenty-five thousand users. Until I reach that number, I think I am good.

How are customer service and support?

I would rate the technical support at nine or ten; I would say nine because most documentation is up-to-date and I can get answers in their forums. When I need to get support on something which is not there, then it takes some time, such as one to three days at times to get a response.

How was the initial setup?

The deployment is easy; since it is a SaaS offering, I do not need to push any updates or anything of that nature.

Auth0 Platform from my end does not require maintenance. I cannot worry about authentication and I just focus on building my own plans.

What was our ROI?

The return on investment I have seen is that it has saved me quite a lot of time which would have instead gone into implementation, as they have good documentation and quite a few quick starts and examples. I can just give tools such as Cursor or Claude the link to those documentations, and they help add Auth0 Platform to my project, so a lot of time has been saved on implementation.

I estimate it is at least twenty to thirty percent because that part would have involved me writing application code, but that I offloaded to Auth0 Platform. At least thirty percent I would estimate.

Which other solutions did I evaluate?

I would compare Auth0 Platform to other solutions, and I think on the UI side, they are definitely one of the better ones, and they have good documentation. The only downside to them is the pricing, which is a bit expensive.

Regarding the pricing, it is expensive, but I will say the value comes when you use most of its features. Then you can make value out of that price. If you are just using it for basic login and just MFA, then the pricing might be too much and there are other vendors out there who might be better suited.

What other advice do I have?

Approximately three hundred users use Auth0 Platform right now because it is in beta, so I am just testing with a closed group.

I would advise others looking to implement this product that if they do not have any on-premises regulatory requirements, they can definitely look at Auth0 Platform, as they have a really good developer ecosystem. Someone can just download their example projects and play around with it and if it fits the purpose, go ahead. I would highly recommend that. I give this product a review rating of nine.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)


    Kaeleigh Stroud

Strong authentication has improved our enterprise trust and supported rapid ISO certification

  • March 16, 2026
  • Review provided by PeerSpot

What is our primary use case?

Auth0 Platform serves as our primary authentication platform for public-facing websites, and we use it primarily for two-factor authentication.

We only use Auth0 Platform for user authentication and do not use it for API-based authentication.

We currently use Auth0 Platform to secure three applications, and our next phase is introducing multi-tenancy.

What is most valuable?

We chose Auth0 Platform for two main reasons. First is their tenant and segregation capabilities, and the second is their reputation in the industry, which made it much easier to sell our product to enterprises since they had already heard about Auth0 Platform.

The multiple options for two-factor authentication with Auth0 Platform were really easy to set up and integrate into our system. The entire process, including migration of users, took about a week and a half.

Thanks to Auth0 Platform, we are ISO 27001 certified.

What needs improvement?

Managing federated identities for our customers to onboard their own users in Auth0 Platform would be a great enhancement.

For how long have I used the solution?

I have been working with Auth0 Platform for about eight months.

What do I think about the stability of the solution?

We have experienced some crashes, downtimes, and performance issues with Auth0 Platform, but it was not their fault.

What do I think about the scalability of the solution?

Currently with Auth0 Platform, we only have one tenant, and we are planning on implementing multi-tenant architecture.

We are not using multi-tenant architecture yet with Auth0 Platform, as we are planning to use it in our next phase.

How are customer service and support?

Our experience with customer service has been a mixed bag. We had a contact at Okta previously, but because we are on a subscription-based plan, we can only use the community support. Unfortunately, their hours are outside of our working hours, making it difficult to get support from them.

Which solution did I use previously and why did I switch?

Our biggest issue with Auth0 Platform was the cost. From a feature perspective, they had everything we needed compared to the other options. They have the reputation within enterprises. There was another competitor that had a better developer experience, but when it came time to actually using Auth0 Platform, their developer experience was great.

How was the initial setup?

Auth0 Platform was really easy to use, and I honestly do not have any complaints.

We used Auth0 Platform's own documentation and tooling for the deployment.

What other advice do I have?

Explore the documentation for Auth0 Platform, as it is better than you might think. I would rate this product a 9 out of 10.


    reviewer2809026

Security has become faster to implement and supports AI-powered apps across platforms

  • March 13, 2026
  • Review provided by PeerSpot

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.


    reviewer2805510

Identity workflows have transformed how we secure logins and manage user access daily

  • March 13, 2026
  • Review from a verified AWS customer

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What about the implementation team?

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

What was our ROI?

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.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?

Amazon Web Services (AWS)


    Sebastian Micu

Platform has strengthened user security, improved sign-on journeys, and supported future growth

  • March 13, 2026
  • Review provided by PeerSpot

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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.

What do I think about the stability of the solution?

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.

What do I think about the scalability of the solution?

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.

How are customer service and support?

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.

How would you rate customer service and support?

Positive

Which solution did I use previously and why did I switch?

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.

How was the initial setup?

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.

What was our ROI?

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.

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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.

What other advice do I have?

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.

Which deployment model are you using for this solution?

Public Cloud

If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?


    Piyush Tripathi

Unified identity platform has reduced dev time and secures multi-tenant cloud microservices

  • March 13, 2026
  • Review provided by PeerSpot

What is our primary use case?

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.

What is most valuable?

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.

What needs improvement?

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.

For how long have I used the solution?

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

What do I think about the stability of the solution?

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.

Which solution did I use previously and why did I switch?

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

How was the initial setup?

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.

What about the implementation team?

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

What's my experience with pricing, setup cost, and licensing?

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.

Which other solutions did I evaluate?

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

What other advice do I have?

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