We just raised a $30M Series A: Read our story

Auth0 OverviewUNIXBusinessApplication

Auth0 is #3 ranked solution in top Customer Identity and Access Management tools, #5 ranked solution in top Access Management tools, and #6 ranked solution in top Single Sign-On (SSO) tools. IT Central Station users give Auth0 an average rating of 8 out of 10. Auth0 is most commonly compared to Amazon Cognito:Auth0 vs Amazon Cognito. The top industry researching this solution are professionals from a comms service provider, accounting for 26% of all views.
What is Auth0?
You can easily and quickly connect your apps, choose identity providers, add users, set up rules, customize your login page and access analytics from your Auth0 dashboard. It really is identity made simple for developers.
Buyer's Guide

Download the Single Sign-On (SSO) Buyer's Guide including reviews and more. Updated: October 2021

Auth0 Customers
JetPrivilege, Safari, Schneider Electric
Auth0 Video

Pricing Advice

What users are saying about Auth0 pricing:
  • "I am pretty happy with the pricing model of Auth0. It is very clear for me. Considering our scale, the features that we are using, and additional features that we bought, we still find it great. If you split the costs for the whole year and calculate the number of people you needed to hire, it always comes out to be much lesser than what we would have spent on building our own solution."

Auth0 Reviews

Filter by:
Filter Reviews
Industry
Loading...
Filter Unavailable
Company Size
Loading...
Filter Unavailable
Job Level
Loading...
Filter Unavailable
Rating
Loading...
Filter Unavailable
Considered
Loading...
Filter Unavailable
Order by:
Loading...
  • Date
  • Highest Rating
  • Lowest Rating
  • Review Length
Search:
Showingreviews based on the current filters. Reset all filters
Jakub Wozniak
Principal Architect at a computer software company with 201-500 employees
MSP
Top 20
Shortens the development time, takes care of compliance, and saves a lot of money

Pros and Cons

  • "The most important thing for me is compliance. Everything that they have developed in Auth0 is already certified by many regulators such as ISO. So, we do not need to take care of that. We have the shared responsibility model to share assets with other products we are using in the cloud."
  • "There is a possibility to improve the machine-to-machine authentication flow. This part of Auth0 is not really well documented, and we could really gain some additional knowledge on that."

What is our primary use case?

We are building a software as a service platform of products, and we wanted our customers to be able to have the same seamless experience in terms of how they log into our products. We wanted it to be secure, and we didn't want to use our own development resources in building our own solution. We wanted something that is secure and ready at the beginning of our development so that we have a very short time to market. We wanted it to be a very extensible solution and building something on our own wasn't an option for us. We wanted something that was already there. We also wanted a company that is highly committed to delivering state-of-the-art solutions for identity management.

It is deployed in the cloud. This is a software as a service. So, our workloads work in the cloud. We are mostly using AWS, but we also have Azure and GCP. We are a multi-cloud company.

How has it helped my organization?

I was able to pass the ISO audit smoothly. When they asked me for identity management, I just told them that it is Auth0, and it was passed. So, it has helped with compliance.

We are using Auth0 Rules during the authentication process to contact our internal APIs and extend the token that Auth0 generates with additional information that comes from our database. Auth0 Rules are pretty important because by using Auth0 Rules, we are able to shorten the development time. We didn't need to do any workarounds and so on. We could quickly deploy some code into Auth0, and our use case was covered in less than one day. We are also using Actions, which is the new thing that came after Rules and Hooks.

It provides the flexibility and the customizability that we need. I did a webinar on Auth0 in AWS, and I said that we know that the software-as-a-service products are not designed to cover 100% of use cases. They are just trying to solve 90% of them, but with Auth0's Rules engine, Actions engine, and many different features, I am able to code something around Auth0. So, I can bend the existing functionality exactly for my use case. For me, this extensibility of the software or the software as a service model is very important because then I know that I won't face any roadblocks that I cannot really go around.

It allows us to tailor the user experience flow. We find the user experience with Auth0 really great, and we could customize it exactly as per our needs. The new features that they released during the last year since we have signed the contract have been helpful. The additional hosted login page that splits the authentication into two different steps and the Auth0 organization features are really great for us.

It has saved us the development time and money by not having to deal with authentication or identity management. It has shortened the development time and saved a lot of money for us. We did a case study on Auth0, and we had a 300% return on investment in terms of money. We have also reduced the development time by about two months. We also don't need people dedicated to our own solution, which is an ongoing process of saving money.

It has helped us in setting up authentication without having to hire additional staff. We were able to do that with our own resources. We don't need to have a dedicated team that is working only on identity management.

What is most valuable?

The most important thing for me is compliance. Everything that they have developed in Auth0 is already certified by many regulators such as ISO. So, we do not need to take care of that. We have the shared responsibility model to share assets with other products we are using in the cloud.

I am very pleased with the number of features that came with Auth0. I am also very happy with how Auth0 developed since we have been using it. The number of features is really great for me, and it really covers almost all of the needs that we have when deploying it into our product.

Their documentation and SDKs are great when it comes to helping developers and application builders set up authentication. On a scale of zero to 10, I would rate it a strong eight because their documentation is really good. They are able to explain a pretty complex process of authentication and authorization in simple words. Their documentation is a really great resource of knowledge, even if you are not using Auth0. That's because the process that they have implemented is a well-known standard in the industry, and they have described it really well. Their documentation is really great for us. We had no problems with SDKs, and their SDKs are also pretty good.

What needs improvement?

There is a possibility to improve the machine-to-machine authentication flow. This part of Auth0 is not really well documented, and we could really gain some additional knowledge on that.

For how long have I used the solution?

I have been using Auth0 for a year.

What do I think about the stability of the solution?

Its stability has been great. We didn't have any issues with Auth0 so far.

What do I think about the scalability of the solution?

It has been working really well for us. We don't see any issues in terms of scalability. We are going to increase its usage because this is our business.

How are customer service and support?

I really like the customer support of Auth0. I really like the people I'm working with from Auth0. They are really helpful. So, I'm very happy with them. I would rate them a nine out of 10. I didn't give a 10 because there is always room for improvement. So, a 10 is not really achievable.

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

We were using a different solution from a cloud provider. We switched because we felt that the solution that we were using was not really well maintained. It was working, and it was stable, but the customer experience wasn't great. The number of features that were released when we were working with that solution was close to zero.

How was the initial setup?

It was very easy. We were able to onboard it with the first application in less than two weeks.

We had an implementation strategy. We started with a very simple PoC. We had a small dedicated team for that. I and my colleague researched and reviewed what is Auth0 capable of and designed a very small framework for working with Auth0. We quickly onboarded the first one of the five applications that we have. So, the first application was our battleground. We saw what is working and what is not working. We decided how we should work with Auth0 and how to shift everything that is possible in our case to Auth0. After that was done, we tested it on the small user base. We then, one by one, went with other applications.

What was our ROI?

We had done an Auth0 case study, and we had stated there that we had a 300% return of investment in terms of money.

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

I am pretty happy with the pricing model of Auth0. It is very clear for me. Considering our scale, the features that we are using, and additional features that we bought, we still find it great. If you split the costs for the whole year and calculate the number of people you needed to hire, it always comes out to be much lesser than what we would have spent on building our own solution.

Which other solutions did I evaluate?

We did some evaluation. We evaluated the solutions that are available from various cloud providers such as AWS, GCP, and Azure.

We also looked into Okta, which was its competitor at that time. Now, Okta is the owner of Auth0. At that time, we felt that Auth0 had a big advantage over Okta. Auth0 was focused on the external users' experience. Okta, for example, was more focused on internal employees logging into the systems. It was more about internal entity management. We wanted something for external users, and Auth0 was really great at that.

We went with Auth0 also because it is a company that is fully committed only to identity management. With cloud providers, this is just another service that can be maintained. So, we wanted to go with a provider that is really focused on delivering only external identity management solutions for customers like us.

What other advice do I have?

To someone who says we can build authentication in-house, I would say that you can try it, but you will probably fail at it. The authentication and authorization process is really complex. You need to be really focused on that to be able to deliver a solution that is really secure and compliant with different standards. You can sleep peacefully having Auth0 deployed. With solutions that are built in-house, you will probably have some basic functions, but in my opinion, there is a vulnerability that will probably be exploited in the future. Auth0 is hiring people who are committed only to one particular area of computer science, which is authentication and authorization. They really understand the different algorithms that are behind that. So, if you do not have such engineers in-house, you will probably have a solution that is not 100% bulletproof.

For us, MFA is required every time someone logs in. Even though I like the idea of Adaptive MFA, it is not a good fit for our business model. 

Auth0 allows us to turn on or off features like social logins, MFA, or Anomaly Detection with the flip of a switch, but it is hard to assess the importance of this feature. The ability to customize the flow for authentication and authorization is very important for us, but as a company, we don't need social logins and so on. Having them enabled would be considered unprofessional in our area, and we don't need to turn them on. So, this is very important for us that things that we do not use can be turned off.

It hasn't helped to increase new-user conversion due to less sign-up or login friction because that is not in our business use case. We do not allow people to sign in to our solutions. We are business-to-business. Similarly, it has not decreased customer support tickets due to password issues because that's not applicable to us.

I would rate Auth0 an eight out of 10. I will always say that I am a really big fan of Auth0.

Which deployment model are you using for this solution?

Public Cloud
Disclosure: IT Central Station contacted the reviewer to collect the review and to validate authenticity. The reviewer was referred by the vendor, but the review is not subject to editing or approval by the vendor.
Flag as inappropriate
Siddhit Renake
Platform Engineer - Linux at a tech services company with 201-500 employees
Real User
Top 20
Easy and flexible integration regardless of the codebase

Pros and Cons

  • "The most valuable feature is that it is simple to integrate, irrespective of your codebase."
  • "This is a costly solution and the price of it should be reduced."

What is our primary use case?

We were evaluating Auth0 as centralized authentication solution for our in-house development. We are searching for the best solution to take care of this because our product development is ongoing, and we want to find just the right fit. Ultimately, we did not choose Auth0.

What is most valuable?

The most valuable feature is that it is simple to integrate, irrespective of your codebase.

What needs improvement?

This is a costly solution and the price of it should be reduced.

For how long have I used the solution?

We had been evaluating and testing Auth0 for between three and four months.

What do I think about the stability of the solution?

It is pretty much stable. We did not encounter any issues with respect to integration and testing.

What do I think about the scalability of the solution?

Considering we are conducting a PoC, we are not able to fully test scalability. However, our understanding is that it scales well.

How are customer service and technical support?

My team was in touch with their counterparts from marketing and technical resources, but because it was a PoC engagement, we did not take it further.

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

We did not use another SSO product before our current PoC began.

Which other solutions did I evaluate?

We have been evaluating multiple single sign-on solutions including Auth0 and Okta.

We run a successful proof of concept but we did not select Auth0 because their entire structure is hosted on AWS, and we are a data center company so we thought that having the backend hosted on AWS was not the right choice for us.

Had this same solution been available as a private deployment then it would have been the right fit for us.

What other advice do I have?

During our exploration and evaluation, Auth0 and Okta were the top contenders from a pure authentication point. My advice for anybody who is considering such a system is to have multiple authentication systems evaluated from a technical point of view, and adopt the one which rightly suits your use case and requirements. Different products have different features sets, but what matters most is that it is purely compatible with your use case. Scalability is probably the most crucial factor.

I would rate this solution an eight out of ten.

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)
Disclosure: I am a real user, and this review is based on my own experience and opinions.
Find out what your peers are saying about Auth0, OneLogin, Atlassian and others in Single Sign-On (SSO). Updated: October 2021.
552,027 professionals have used our research since 2012.
AM
Security Architect at a construction company with 10,001+ employees
Real User
Secure, developer-friendly, and the support is good

Pros and Cons

  • "The valuable features are that it is extremely secure and that it's developer-friendly."
  • "In the past, there was an issue with the multi-tenant where there wasn't the ability to manage them."

What is our primary use case?

The primary use case of this solution is to authenticate APIs, customer authentication, and business-to-business authentication.

What is most valuable?

The valuable features are that it is extremely secure and that it's developer-friendly.

What needs improvement?

In the past, there was an issue with the multi-tenant where there wasn't the ability to manage them. For example, if you have three tenants you couldn't have different managers, but that has been sorted out through the release tool.

For how long have I used the solution?

I have been using Auth0 for three years.

What do I think about the stability of the solution?

This solution is stable, we have not had any issues.

What do I think about the scalability of the solution?

It's a scalable product.

How are customer service and technical support?

We have contacted technical support and find that they are good.

How was the initial setup?

The initial setup of the solution was simple, but our requirements were complex.

The deployment time varied depending on the complexity. Some would have taken a week while others would have taken three months.

What about the implementation team?

We used external consultants and consultants through Auth0 to help with the implementation.

What other advice do I have?

This solution does what we want it to do. It's good and I don't see any issues.

For anyone wanting to use this solution, make sure that your developers are fully engaged. They have to know how Auth0 works and what the best way to leverage it.

I would rate this solution an eight out of ten.

Disclosure: I am a real user, and this review is based on my own experience and opinions.
Buyer's Guide
Download our free Single Sign-On (SSO) Report and find out what your peers are saying about Auth0, OneLogin, Atlassian, and more!