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.
Auth0 Platform
Okta, IncExternal reviews
256 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Centralized authentication has enabled granular access control and efficient growth management
What is our primary use case?
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.
How would you rate customer service and support?
Negative
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.
Authentication has become seamless across platforms and has reduced integration time significantly
What is our primary use case?
We use Auth0 Platform for our clients, and we started in 2019, which means we have been using it for around four years.
Auth0 Platform is used for user authentication. We use it for our clients who are using Google authentication. We have integrated with Azure Connect for another client from outside. Basically, we use Auth0 Platform for authentication.
Regarding the flexibility of customizable authentication, we do not have a specific need because we only authenticate, and the endpoint sends the verification, which is really easy. We have even tried SAML connection because another client suggested that there should be more clients with SAML connection.
The impact of Auth0 Platform's centralized, customizable universal login on the user experience is significant because we have to adapt to the client's email since most clients are from Google with a Google IDP. In that case, we use the universal login to separate them and cooperate with that.
We do not utilize the Fine Grained Authorization feature as we only use it for authentication. For authorizations, we use our internal system.
What is most valuable?
The best features of Auth0 Platform are that it is easy to integrate and is cross-platform. We use it with the Angular front end and the UWP application, and it also works with the iOS application, so it is really easy to integrate within the dashboard without any complications.
Regarding the flexibility of customizable authentication, we do not have a specific need because we only authenticate, and the endpoint sends the verification, which is really easy. We have even tried SAML connection because another client suggested that there should be more clients with SAML connection.
What needs improvement?
Auth0 Platform could improve by allowing more than three enterprise connections, as I remember it being three. We are stuck with that because I am not sure how the plan works, but it should be at least five.
The areas for improvement in Auth0 Platform include the UWP functionality, which works fine with the SDK. The support is also good as we read the documents available. In comparison to Keycloak, Auth0 Platform is my ultimate choice due to the ease of integration and strong support when we raise a ticket.
The amount of enterprise accounts could be improved, as that is my concern.
For how long have I used the solution?
We use Auth0 Platform for our clients, and we started in 2019, which means we have been using it for around four years.
What do I think about the stability of the solution?
The reason I rate scalability a seven is not due to downtime, bugs, or glitches, as we have not experienced any. My concern is more about scaling connection-wise. For the last four years, we have not experienced any bugs from Auth0 Platform.
What do I think about the scalability of the solution?
When assessing scalability, I would rate it around a seven, but the plans raise some concerns for me.
Auth0 Platform is scalable, and I would rate it around ten for being able to downsize or upsize based on our requirements.
How are customer service and support?
Auth0 Platform requires maintenance as we have done some updates, and recently we have not done anything. However, we are in touch with Auth0 Platform team for any required security updates.
Maintenance is easy because we can handle everything using their Auth0 Platform configuration site.
I would rate the technical support of Auth0 Platform around nine, as it is one of the perfect supports I have had.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I have been using Keycloak for around two years, and we worked with it for around one year for that project. Now we are not working at the moment, but for the support, we are working on that.
Regarding the use case, we do not use Okta platform; we use Keycloak instead. Okta and Keycloak are two different things.
When comparing Auth0 Platform to other solutions and vendors on the market, it stands out for being easy in terms of integration, which is the main thing as a developer. It supports all the libraries, and when going to Angular, there are NPM packages and the SDK available. In comparison to Keycloak being a free open-source option, I prefer Auth0 Platform.
The pricing of Auth0 Platform is a consideration when choosing the technology. While comparing Auth0 Platform and Keycloak, I note that they are two different things—one is free and the other is paid. Therefore, we cannot directly compare a free option to a paid one, but I prefer Auth0 Platform's pricing.
How was the initial setup?
For others looking to implement Auth0 Platform, I recommend that it is very easy to integrate, and they offer free plans to support everything. While pricing might be slightly higher than other options, the support and documentation provided are perfect. The only concern remains the plans, as small organizations like us just need around four to five connections.
What was our ROI?
I would estimate that the return on investment with Auth0 Platform saves around thirty to forty percent of my time in comparison to integrating with Keycloak.
Modern identity access has unified customer logins and strengthened risk‑based protection
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been dealing with Auth0 Platform for more than one year.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What about the implementation team?
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.
What was our ROI?
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.
What's my experience with pricing, setup cost, and licensing?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
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.
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.
• 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.
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.
Simple, Versatile Dashboard with Powerful AI Agents and Apps
What do you like best about the product?
its dashboard and simplicity and diversity of services like authentication and authorization of my applications
What do you dislike about the product?
i dont like the pricing and the platform sometimes stuck
What problems is the product solving and how is that benefiting you?
i like the Passwordless Authentication which help my app users login directly using emails
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.
Fast, Secure Identity Management with Easy MFA and Strong IAM
What do you like best about the product?
We use Auth0 for smooth identity management and it ensure fast and secure authentication.
The MFA feature is easy to setup and makes authentication process easy and fast.
I like that Auth0 also offers freat IAM features which ensures smooth access to business resources/apps/data.
We also leverage Auth0 when it comes to customer identity and access management and I must agree it offers best capabilities.
The MFA feature is easy to setup and makes authentication process easy and fast.
I like that Auth0 also offers freat IAM features which ensures smooth access to business resources/apps/data.
We also leverage Auth0 when it comes to customer identity and access management and I must agree it offers best capabilities.
What do you dislike about the product?
So far Auth0 has been awesome. No serious flaws.
What problems is the product solving and how is that benefiting you?
We use Auth0 to protect identities and to ensures smooth access management. The tool also features amazing SSO and IAM features thus handling access and identity management smoothly.
Secure, Standards-Based Identity with Straightforward, Developer-Friendly Integration
What do you like best about the product?
Auth0 provides a secure, standards-based identity platform with strong support for OAuth2, OIDC, SSO, and MFA, while keeping integration and ongoing management straightforward and developer-friendly.
What do you dislike about the product?
While Auth0 is a powerful platform, some customizations and more advanced features are locked behind higher pricing tiers. Also, when authentication flows get complex, debugging can sometimes feel less transparent and harder to trace.
What problems is the product solving and how is that benefiting you?
Auth0 provides SSO, risk-based authentication, and CIAM out of the box, making it easier to deliver secure, scalable user access without having to build and maintain complex identity infrastructure from scratch.
Auth0: Fast Setup, Flexible Security, and Clear Docs That Scale
What do you like best about the product?
Auth0 makes handling authentication much simpler and more secure without adding unnecessary complexity. What i like best is how quickly you can set up login, signup and social authentication without having to build everything from scratch. It also gives a lot of flexibility with security features like multi-factor authentication, role-based access, and integration with different identity providers. The documentation is clear and the platform scales well as applications grow. Overall, it saves a lot of development time while still keeping security strong and reliable.
What do you dislike about the product?
Auth0 can feel a bit complex once you move beyond basic authentication. There are a lot of settings, rules and configurations, which can be overwhelming at first and take time to fully understand. Another downside is pricing. As your user base grows or you need advance features, costs can increase quickly which may not be ideal for similar teams or early stage products.
What problems is the product solving and how is that benefiting you?
Auth0 solves the tricky problem of building and maintaining secure login and user access systems from scratch. Instead of spending weeks writing and maintaining your own authentication logic, you get a flexible platform that handles sign-ups, logins, social logins, multi factor authentications, SSO and access control out of the box. This means you don't have to reinvent the wheel every time you launch a new app or service. For me, this is super helpful because it takes one of the most complex and security sensitive parts of app development off my plate. I can integrate secure authentication quickly, support different login expertise. It also gives my users a smoother, more reliable login experience, while i spend more time building core features instead of wrestling with identity and access code.
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.
showing 1 - 10