Auth0 Platform Reviews

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.

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.

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

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

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

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.

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.

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.

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.

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

Google

We are an enterprise IT services provider delivering cloud solutions to our clients. We implement Auth0 (Okta) to secure API integrations, enable SSO for client websites, and support passwordless authentication, MFA, and RBAC. It helps us standardize identity and access management across applications.

Auth0 makes it easy to secure APIs, microservices, and modern applications with a consistent identity layer. Features like SSO, MFA, and RBAC are straightforward to configure and work reliably across environments.

We have been using Auth0 for about 5–6 years. We initially deployed it in test environments and integrated it for user authentication and SSO access to client applications.

The setup was straightforward. Documentation is clear, and integration with both Azure and AWS architectures was smooth.

We evaluated Microsoft Entra ID and some custom-built authentication solutions. Auth0 was easier to integrate and more flexible for our use cases.

Auth0 works well for securing APIs, microservices, serverless, and container-based workloads. We also use it for AI and agent-based applications. It integrates well with AWS services like Lambda, API Gateway, ECS, and EKS.

Amazon Web Services (AWS)

I am a reseller, and our customers primarily use Auth0 for B2B purposes. Auth0 is mainly used for their employees.

The most valuable feature of Auth0 is its customizability. It allows customers to go beyond what's out of the box and customize their experience to meet their needs. Auth0's multi-factor authentication is effective. Passkeys and threat protection are also excellent features.

The pricing should be lower. A reduction of 20-25% would be great.

I have been working with Auth0 for three years already.

There are no deployment issues. Deployment is very quick. A simple setup can be live in 15 minutes.

There are no issues with stability. I would rate stability a ten out of ten.

The tool is very scalable and meets our customers' needs. I would rate scalability a ten out of ten.

Auth0 has the best support ever. The support staff are engineers, not just frontline personnel, ensuring expert assistance. Multiple channels are available to get help.

Positive

Setting up Auth0 is very easy. On a scale from one to ten, it is a ten in terms of ease of setup.

I can recommend Auth0 and hope it becomes cheaper in the future. The tool is not just for taking money but for making users productive, allowing customization for login, branding, and revenue-driving functionalities. Overall, I rate Auth0 a ten out of ten.

Public Cloud

Other

Auth0 is used as an identity provider for our new SaaS platform to manage the identity of users.

Auth0 is cost-effective because it provides all the features we need, and it was very easy to integrate into our platform. The documentation is comprehensive, and their support team is highly helpful.

The most important feature for me was the ease of use, as it needed to be easy to integrate into my platform. Additionally, the usual features such as social media integration are beneficial.

I find it surprising that there is no access to a standard user profile. By default, the user profile does not contain the name, first name, or address, which I would expect. I have to implement these features myself if I want to include them.

Their support is excellent. I had an issue, and their response was very helpful.

Positive

The initial setup was straightforward due to the ease of use of the solution.

The cost of the solution itself was cost-effective enough that I didn't even need to compare it with EntraID.

I looked into Auth0 and EntraID. I chose Auth0 due to its positive reputation.

I recommend Auth0 to others. It really fulfills my requirements.

I'd rate the solution nine out of ten.

Other

We have user management, role management, and tenant concepts for multi-tenant applications. We use organizations in Auth0. For Okta, we mostly use it for internal SSO to provision users to internal tools.

Auth0’s multifactor authentication enhances our security posture.  They are GDPR compliant, and they provide us with a way to host in multiple regions. We use a European region to be GDPR compliant. 

For performance, we can also choose different regions, like China or North America. They are also HIPAA compliant, but we don’t deal with HIPAA. They are ISO certified, so it’s easy for us to convince our security team. They manage key rotation and things like that on their end in the backend, which helps us.

Auth0 doesn’t have a great way of providing self-managed user management tools. If I have to provision my customers to manage their tenants, they don’t do it out of the box. 

We are wrapping a solution around it to make that happen. There are some marketplace plugins available, but they are not so great. We have developed our own custom solution to expose user management to our customers.

I have been using it for around seven years. I use the latest version. 

It’s highly scalable. We just have to pay more for more users.

For enterprise, I would rate technical support a nine out of ten. 

For any kind of lower starter package, I would rate the technical support somewhere around six out of ten.

So, on an average it is an eight out of ten.

Positive

Within our organization, we use only Okta. We have hooked it up to Active Directory. That’s our single sign-on here.

Okta is mostly provisioned and used through DevOps. Role management and user grouping are mostly easy. There are directional integrations as well, including Azure AD and other tools. We get out-of-the-box solutions to integrate with actionable tools that we are using.

It's straight out of the box. So, the deployment time is almost half an hour to an hour in our case.

It will probably take one day to integrate. We also use IAC for automation. Once that is done, we mostly forget about it.

We have to do user management, like provisioning the users, de-provisioning, when they leave the organization and so on.

It’s easy to integrate and deploy. 

We use the cloud solution. We don’t deploy anything. We use the cloud solution, and we have automated the configuration. That is the deployment that goes on. Like, if we are adding a new tenant and things like that, it all happens through infrastructure as code.

The general deployment and integration took us around one day. Probably one day because we requested it from the DevOps team, and they have to get in touch with someone from the tooling side, and they get it done. So we usually hear back within a day that it’s done.

The point is that we did all the heavy lifting in the initial days. After that, we hardly notice anything. It’s all working well together. The only thing is that we have to wrap up a solution for user management. Other than that, I don’t see any issues.

We don't do the maintenance. It's Auth0 that manages the maintenance. We don’t usually do anything. They have great availability SLAs. We don’t even notice if there are any updates and things like that. 

It’s definitely beneficial. If we had to develop our own and manage it, it would take years of development and maintenance. In those terms, it’s definitely beneficial.

But once you cross that barrier of being a startup and growing, and if you have to move to an enterprise solution, that’s where it becomes expensive. But at that point, I think you’ll be okay to pay anyway.

The pricing depends on the tier you are in. If you’re in enterprise support, there’s always someone who can support you. But if you’re in lower tiers or starter tiers, we have crossed that barrier anyway. 

In the initial days, if you’re not aware of how the OpenID solutions work, it’s probably hard to get started. Once you cross that barrier, it becomes easy. 

But you have to pay extra for technical support, which makes sense, but adoption might become harder for people who might not have experience with either Auth0 or Okta before.

As a developer, I would rate it at nine out of ten. That’s because it’s very flexible. Developers can easily learn the system and get used to developing on it, like configuring automation, configuring integration, and things like that. 

But, again, it’s for developers. You should know how the API integrations work and things like that. But if you are a user in general, I think I would rate it at six or seven, probably seven, because if you’re not a developer, you need to spend time exploring more. 

Also, the scoped user management for a specific customer is not available out of the box with Auth0. So that’s something which, if you are a product manager, you would definitely look at. But if you’re a developer, that’s just an opportunity to build something on top of that.

Public Cloud

We use the solution for API security and management. We implement our solution with almost ten to fifteen vendors' APIs, like Salesforce and HubSpot. 

It involves generating leads, invites, adding contacts, and opportunities, mostly challenging with Salesforce integration due to limited documentation.

The solution is cost-effective and beneficial in terms of security. It enhances secure API requests, improving user management efficiency.

It offers stronger security and flexibility with API keys, which are generated on runtime. This is valuable as they are reusable and can be used for confidential applications.

There is no immediate need for improvement. However, better documentation for Salesforce integration is suggested. Multi-factor authentication could be considered for future research.

I've been working with the solution since 2017, which is approximately seven to eight years.

There have been no issues with performance or stability.

I haven't explored scalability extensively, as it hasn't been required.

We haven't escalated any questions to customer support.

Positive

Google Authenticator and Duo are used for multi-factor authentication.

The initial setup was simple and not complex, involving key or username authorization.

The solution brings security benefits and efficiency.

I recommend the solution as it provides strong security with more control over access. It supports various authentication methods.

I'd rate the solution ten out of ten.

Public Cloud

Other

Developers use the solution to build log-in and sign-up experiences. Auth0 provides an API key that is integrated with the code. We provide sign-in and sign-up instead of making our sign-up, sign-in, invite-user, and forgot-password. We buy Auth0 and integrate it; they run it on their cloud.

The solution offers simplicity of use. They have too much enterprise onboarding when you want a B2B login. The first quick start is the easiest thing. You have too many tutorials and YouTube guides to help you integrate it with your code.

It is expensive and not friendly to small developers. On the other hand, Clerk is user-friendly for smaller companies. 

Auth0 could become more easier. B2B organizations need to catch up with the price. Multi-tenancy needs to be less expensive, and the ease of use and onboarding must also be better. Three tenants are allowed for every account. They have to improve their organizational features.

I have been using Auth0 for one year. We are using the cloud version of the solution.

The product’s stability is fine.

I rate the solution’s stability a nine out of ten.

Our clients' products have close to 200-250 active users. It is charged based on the number of active users. It has more significant customers like Jira.

I rate the solution's scalability a nine out of ten.

Customer service used to be very responsive. Now, the community support is helping us for a long time. Whatever you are looking for, you will get it in the community support forum. Auth0 has community forums, help documentation, and Q&A. The user community of Auth0 is very supportive when you need help. The dedicated support forum is overwhelmed. It's becoming harder to reach someone unless you have a bigger account.

Neutral

We have used Keycloak for a very long time.

Auth0 has an SDK that calls their servers. We have to install the SDK in our codebase, and our developers must integrate it with our sign-in and sign-up pages. It takes the least amount of time compared to alternatives. It is well-documented and is the best solution in the market.

The product is expensive.

I rate the product’s pricing a seven out of ten, where one is cheap and ten is expensive.

We are evaluating SuperTokens and Lock. If Auth0 becomes expensive, we can host another solution.

It is a good product if you are a B2C or B2B solution or any app or consumer product.

Overall, I rate the solution an eight out of ten.

Public Cloud

We use the tool for Single Sign-On (SSO) feature.

Auth0, being deployed on the cloud, provides all the functionality in a single place. We don't need to maintain machines, inventory, or procurement. It has a lot of customization and out-of-the-box features as well. We can quickly plug it into products like Active Directory or other identity broker solutions.

There could be an easy integration with IoT devices for the product.

We have been using Auth0 for four or five years.

It is a stable platform.

We have 100 users for the platform in our organization. It is very scalable.

We deployed the product on a private cloud by Auth0. Its initial setup process is user-friendly.

It is a relatively inexpensive product in the industry.

Auth0 is quite a low-cost and stable product. It provides a lot of good functionality as well. It is easy to use, manage and is very intuitive. Additionally, we can look at the logs and troubleshoot the issues.

I rate it an eight out of ten. 

Private Cloud