Effortless Authentication Management with Robust Integration
What do you like best about the product?
I like how Auth0 offers a very simple integration into Next.js applications compared to other auth providers. The SDK is robust and easy to work with, which is a huge plus for me. I also appreciate that Auth0 provides a much more complete set of features than if we were to write everything ourselves. Additionally, the initial setup was a 10/10 for us, making the transition smooth and efficient.
What do you dislike about the product?
It was a bit difficult to update sessions when they expire on Next.js server components. While this isn't necessarily an Auth0 issue, they could provide a complete solution for these cases.
What problems is the product solving and how is that benefiting you?
I use Auth0 for easily managing authentication types and roles. It offers simple integration into Next.js applications and has a robust SDK. We switched from a custom provider for its more complete set of features than writing everything ourselves.
Auth0 Made Multi-Tenant SSO and MFA Actually Manageable
What do you like best about the product?
What I like best about Auth0 is how effortlessly it handles complex identity requirements without making your life complicated. I used feature like SSO integrations, user access management and MFA
What do you dislike about the product?
The biggest pain point for me has been the complexity around multi-tenant architecture setup. While Auth0 supports it well in theory, the initial configuration can be quite tricky, especially when you're trying to manage tenant-specific SSO connections
What problems is the product solving and how is that benefiting you?
We struggled with users needing separate credentials for every application they accessed, but now with SSO, users authenticate once and move seamlessly across all connected applications , which has resulted in a noticeably better user experience and fewer password-related support tickets
Auth0 Keeps Our Business, Employees, and Customers Secure
What do you like best about the product?
Using Auth0 helps keep our business, employees, and consumers secure.
What do you dislike about the product?
Sometimes it can be time-consuming to sign in and access my accounts.
What problems is the product solving and how is that benefiting you?
It provides security and protection from hackers. Not only me, but anyone in cyberspace needs this kind of protection.
Auth0 Simplifies Secure Authentication with Powerful, Customizable Features
What do you like best about the product?
What I like the most about Auth0 is that it enables simplifying authentication and authorization without necessarily developing everything on your own. The platform provides a rich set of capabilities such as social logins, multi-factor authentication, and single sign-on, and thus can be highly customizable to various applications. It is also developer friendly, has good documentation and SDKs that facilitate easier integration. Generally, it conserves much time and maintains high levels of security.
What do you dislike about the product?
One downside of Auth0 is that it can feel a bit complex when you first start using it, especially for beginners. The pricing structure can also become expensive as you scale, which might not be ideal for smaller businesses. Additionally, customizing certain workflows or debugging issues sometimes requires deeper technical knowledge, which can slow things down if you’re not very familiar with the platform.
What problems is the product solving and how is that benefiting you?
Auth0 helps solve the challenge of securely managing user authentication and access control. Instead of building and maintaining login systems internally, it provides a reliable and scalable solution. This reduces development effort, improves security, and allows teams to focus more on core business functionalities. It also enhances user experience with seamless login options, ultimately saving time and reducing operational risks.
Unified identity platform has reduced dev time and secures multi-tenant cloud microservices
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.
Simple, Reliable Authentication Solution for Years
What do you like best about the product?
It's simplicity. I have been using it for at least 5 years now for my authentication solution. A true plug-and-play, and it just works.
What do you dislike about the product?
Sometimes the community docs are out of date. But for the most part, it gets me where I need to be.
I do wish they add a wayt o make the Action Trigger code editor bigger or resizable!
What problems is the product solving and how is that benefiting you?
I'm using Auth0 for an app that has a Desktop side and web/chrome extension side. They make it easy to separate your app in seperate applicaitons within the same tenant and then have decent tutorials on configuring it. The real-time logging is very useful when some errors aren't surfaced on the failed auth response in the client. The action triggers I find extremely easy to use and deploy.
Centralized authentication has enabled granular access control and efficient growth management
What is our primary use case?
I use Auth0 Platform as our authentication platform to allow our customers into the app that we provide, so it's essentially our authentication piece.
What is most valuable?
The ability to manage multiple customers and assign roles within Auth0 Platform is the most valuable feature I have found. It allows certain users access only to specific pages or data sets in our application. We can have all our customers in different buckets. I also maintain separate production and staging environments with distinct setups, making it central for authentication management across different environments and customers.
The flexibility of Auth0 Platform's customizable authentication flows in adapting to our organization's specific needs is commendable. Being able to execute custom code snippets within Auth0 Platform to set different access levels or provide messages to users who lack access to requested pages, along with tracking and notifications, is very beneficial.
The impact of Auth0 Platform's centralized, customizable universal login on our organization's user experience is significant, as it is essential for hosting our application effectively.
What needs improvement?
The reporting in Auth0 Platform could use improvement. Currently, most of the reporting is contained within Auth0 Platform, but it would be useful to have notification streams sent to email or Teams. Enhancing notification features and their ease of use would be beneficial.
I do not have any specific recommendations for improvements as I utilize features I need, such as actions and triggers, as needed. Much in Auth0 Platform remains unutilized by us due to lack of needs, highlighting scalability.
I am not using Bot Detection and Attack Protection enhancements actively; it might be part of Auth0 Platform that I am not familiar with. Additionally, I lack enhanced B2B features implementation, focusing instead on applications and user management.
For how long have I used the solution?
I have been working with Auth0 Platform for approximately seven or eight years.
What do I think about the stability of the solution?
I have not often communicated with the technical support specialists at Auth0 Platform. I remember maybe once or twice experiencing outages that seemed global. During those instances, I waited for service restoration without contacting support.
What do I think about the scalability of the solution?
Auth0 Platform scales exceptionally well with us. I find the built-in Zanzibar and Spide authorization engine robust. As I continuously add users, customers, and refactor for other applications in Auth0 Platform, it supports my application growth efficiently.
I would rate the scalability level of Auth0 Platform as a 10. Scalability is crucial for us, with business directives requiring flexible and manageable platforms such as Auth0 Platform. Its intuitive interface supports seamless build-outs as needed without problems.
How are customer service and support?
I have not often communicated with the technical support specialists of Auth0 Platform, except possibly during rare outages. Otherwise, I have not needed to engage with tech support.
Which solution did I use previously and why did I switch?
I used a different solution for similar use cases before Auth0 Platform, through Microsoft. It was contained in Microsoft Azure's federation service, though the exact name escapes me as it has been a long time.
I switched to Auth0 Platform as part of migrating from Azure to Google Cloud seven years ago, driven by dissatisfaction with Microsoft Azure due to billing issues. My move to the Google stack included incorporating Auth0 Platform.
I considered options such as Okta at one point, but Auth0 Platform was a better fit.
How was the initial setup?
From what I remember, the initial setup process with Auth0 Platform was straightforward. I had guides and consultants familiar with Auth0 Platform who provided a white-glove service, aiding my team in establishing connections and setting up my application. The scalability since then has been admirable.
What about the implementation team?
I participated in the initial setup and deployment of Auth0 Platform.
What was our ROI?
I feel it has been a very prudent investment. I get everything I want and more from it for what I invest.
Currently, I feel that Auth0 Platform is very affordable.
What other advice do I have?
In my Confluence environment, I have instructions for setting up new applications, adding, and managing users, so I maintain my custom documentation for Auth0 Platform.
I think it is somewhat difficult to suggest enhancements for Auth0 Platform as I choose features based on necessity and have always found needful accommodations when required.
Smooth Developer Experience with Flexible Setup and Strong Security Defaults
What do you like best about the product?
The developer experience is smooth, especially when it comes to the SDKs and the docs. I like that it’s flexible without feeling chaotic: we can set things up simply at first and then grow into more advanced features and libraries, like rules and actions, without having to rip everything apart later.
The security defaults are also very strong—MFA and everything else they introduced.
What do you dislike about the product?
Honestly? A few things kinda bug me about Auth0:
• Pricing feels sneaky sometimes — it’s fine at first, then suddenly you’re like “wait… why is this so expensive now?”
• It can get confusing fast — lots of settings, tabs, rules, actions… easy to lose track of what’s doing what.
• You’re pretty locked in — once everything depends on Auth0, leaving feels… painful.
• Debugging is meh — when login stuff breaks, it’s not always clear why, and that’s frustrating.
It’s solid overall, just not as “set it and forget it” as it sometimes claims to be.
What problems is the product solving and how is that benefiting you?
Auth0 solves the “I really don’t want to build auth myself” problem.
It takes care of logins, signups, passwords, MFA, social stuff — all the boring but dangerous parts — so I don’t accidentally mess up security. That alone saves a stupid amount of time and stress.
For me, it means I can focus on actually building the product instead of babysitting auth, fixing edge cases, or worrying that I missed something critical. It just removes a whole category of headaches.
Seamless Security and Integration with Auth0
What do you like best about the product?
I like the incredibly helpful community around Auth0, which has been amazing during our transition to a modern platform. The employees are very quick to answer any questions, and the eager community members are incredibly knowledgeable and always ready to help. Some of the hidden features are impressive, such as bot detection and dynamic threat assessment, which keep our financial service applications secure and reduce a lot of manual stress. The initial setup was incredibly easy.
What do you dislike about the product?
I think the advanced personalization for universal logins could be enhanced even further. It's a new feature, but being able to customize every single screen and journey would be amazing.
What problems is the product solving and how is that benefiting you?
Auth0 provides scalability and integrates our clients into a secure identity platform without tying them to various SaaS and PaaS platforms. This allows us to add or remove apps seamlessly without requiring our clients to re-register, giving them one identity to access all services.
Effortless Authentication with Robust Security and Seamless Integration
What do you like best about the product?
What I like best about Auth0 is that it removes a huge amount of authentication complexity. Instead of building login, signup, password reset, MFA, and social login from scratch, Auth0 handles all of this in a clean and secure way. As a backend developer, I really appreciate how well documented the APIs and SDKs are. Whether I am working with Node.js, Java, Python, or another stack, integrations are straightforward and predictable. Another song's point is security by default. Features like MFA, brute force protection, anomaly detection, and secure token handling come built in. This gives confidence that user authentication is handled properly. I also like the flexibility of the authentication flow. Auth0 support email/password, social login, enterprise SSO, and passwordless login, all in one place. The dashboard is clear and practical. Managing users, roles, permissions, and applications is simple and doesn't feel overwhelming. Auth0 feel like a reliable foundation that you can build on without constantly worry about security issues.
What do you dislike about the product?
The biggest downside is pricing. As the number of users grows, costs can increase quickly, which can be difficult for a startup or fast-growing product. Another issue is that customization can get complex. While Auth0 is flexible, advanced customization often requires writing rules or actions, which adds learning overhead. The dashboard sometimes feels too crowded, especially for new users who are not familiar with the authentication concept. Debugging authentication issues can also be challenging. When something goes wrong, it's not always easy to trace the exact cause without checking logs carefully. Another small downside is vendor lock-in. Once deeply integrated, migrating away from Auth0 can take effort.
What problems is the product solving and how is that benefiting you?
Auth0 solves the problem of building and maintaining secure authentication systems. Authentication is critical, but it is also time-consuming and easy to get wrong. The biggest benefit is time saving. Instead of spending weeks building an auth flow, I can focus on actual product features and business logic. Auth0 also reduces security risk. Authentication vulnerabilities can cause serious damage, and Auth0 handles many of these risks out of the box. From a backend perspective, Auth0 makes identity management centralized. User identities, roles, and permissions are handled in one place, which keeps the system clean and organized. It helps with scalability. As the per-user base grows, Auth0 scales without requiring backend changes or infrastructure upgrades. Another major benefit is consistency across applications. Multiple services or apps can share the same authentication system, which simplifies architecture. Auth0 also supports compliance and audits. Logs, security settings, and access control help meet enterprise requirements. It improves developer confidence during release. Authentication doesn't need to be heavily retested with every release, reducing stress. Auth0 also helps teams move faster. New login methods or security features can be added without major code changes. It improves user experience by providing a smooth login flow, social login options, and fewer friction points. Another benefit is better collaboration between teams. The backend, frontend, and security teams can rely on a shared authentication layer. For long-term projects, Auth0 becomes a stable core service that rarely needs attention once set up properly. Another benefit is less pressure during security reviews. Since Auth0 already follows strong security practices, audits and reviews feel smoother and less stressful for the team. Auth0 also helps with handling edge cases like account recovery, locked users, or suspicious logins. These cases are hard to design correctly, and having them handled centrally saves a lot of effort. It reduces maintenance work over time. once Auth0 is set up properly. There are fewer auth-related bugs, fewer hotfixes, and less firefighting in production. Another useful point is better consistency across environments. Local, staging, and production environments follow the same authentication rules, which avoid "works on my machine" issues. It also helps when integrating third-party tools. Many SaaS tools already support Auth0 or standard OAuth flows, so integrations feel smoother and faster. Finally, Auth0 gives peace of mind as the product grows. Whether the user count increases or new apps are added, authentication does not become a bottleneck or constant worry. Auth0 also helps with clean separation of responsibilities; authentication logic stays outside the core backend code, which keeps services simpler and easier to maintain. Another helpful point is fewer production surprises. Since Auth0 handles many edge cases internally, unexpected login or token issues happened less often after deployment. It also makes future changes easier. If login rules, security policies, or auth methods need to change later, the most updated can be done in Auth0 without touching much application code.
