The solution's deployment is easy. 

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 initial setup was easy, and I rate it a ten out of ten. Our company uses Terraform to build up infrastructure from AWS, and we used a partner to build the product. We needed around five people for deployment, and they were mainly engineers and senior developers.

Initial setup is easy. Deployment took less than an hour.

The initial setup and deployment of Auth0 was pretty straightforward. But to be honest, we are only using 40 to 50 percent of the features they provide. And when we started, we were only using about 20 percent of the features, only the authentication part of it. Our use of it was fairly simple. 

We initially started down this path with Cognito from Amazon. We wrote the whole integration with Cognito and, about two months into that integration, we found a critical issue that we couldn't live with. We didn't get a decent answer from Amazon about it, so we decided to move on to another vendor.

Auth0, obviously, didn't have that issue. The bottom line is that it took us something like two or three weeks to migrate the whole thing from Cognito to Auth0. So in terms of the setup, that was pretty fast. Even migrating from an existing, competitive service, another IDP, was not that complicated. Again, it depends on how many of the features you are going to use. We decided not to go with features that couple us to the vendor so that we would not be locked in. That is what allowed us to migrate to Auth0 in two weeks.

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

The setup is straightforward. We've deployed it in a number of applications, some of those would have taken less than a couple of days of development and deployment, and some of them would have taken weeks. But it's dependent on the complexity of the deployment. That's not a function of Auth0, it's a function of what our digital transformation is trying to do. We used an Auth0 consultant for deployment. 

It was extremely simple and their site even generates sample code in various languages.

It is very easy to use the public cloud instance.

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.

The initial setup was very good, and we set it up in a few hours.

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.