I use the solution in my company for authentication. The tool has many other features, but I use it for authentication management. The tool provides users with the ability to sign up and log in, and it is very easy. You can also integrate login and sign-up for all of the products like Google or Twitter, on which you can allow others to sign up. You can use the permissions to restrict others from viewing some pages, and you can allow others who want to view a page. If they are logged in or signed up, they have access to some pages you can restrict. Another thing is the WebSocket, so if you are working on a feature that depends on it, it is very easy to use Clerk.com to set it up. You can do the same thing in all your apps, and it applies to whichever app you create through Clerk.com. I think that really improves the development process, so you don't have to think about many things.
What is our primary use case?
What needs improvement?
I can say that the apps that I have tried on Clerk.com are mainly in JavaScript. So it's some kind of desk JavaScript application. I am not sure if Clerk.com provides different languages. I usually use LIXA for Phoenix LiveView. I also use Python. I am not sure if there could be the use of other languages, like Python, Django, and Slack. If I could do so, then I think that would be great.
For how long have I used the solution?
I have been using Clerk.com for six months. I am a customer of the solution.
What do I think about the stability of the solution?
I have not faced any stability issues with the product.
What do I think about the scalability of the solution?
Scalability-wise, I rate the solution a nine out of ten.
There are around 2,000 to 3,000 people in the company who use it.
How was the initial setup?
The time required to deploy the product depends on how the app you are creating and how well you have written JavaScript. Writing a script in JavaScript and Excel provides a certain level of security during deployment. You won't get any errors when deploying the applications since everything is already secured and checked. I think that just by connecting with Clerk.com, everything can be done smoothly.
What's my experience with pricing, setup cost, and licensing?
The price of the product depends on the project you are working on at present. If you are working on a personal project, there is a free tier version for up to a few thousand users. For production, or maybe for a company, it is different. I think with the free-tier version, you can really do most of your projects unless you want to go big or if you work for a company. Just for a company project, the free-tier version will not be an issue, especially if it is just a personal project. I think that it is an affordable tool.
What other advice do I have?
Speaking about Clerk.com and how it handles data security and user privacy, I would say that the security features are managed by another team in my company, and they are the ones who know how it works. I am confident that so far, I haven't got any complaints of any data leaks. I don't really know the specifics of how the security is implemented. Even if I consider the documents I got with the product, I would say that I really don't know how it works.
If one is managing the integration process associated with the product for the first time, then one may face some challenges. If you have done it a couple of times, then it is going to be the same thing for you, meaning that you will be basically doing the same thing in multiple apps. Only the first time I had to face some challenges, going to which I had to go through some tutorials and YouTube videos to be able to figure out the product
I would want to tell others to either go big or go home.
I recommend the product to other people.
I rate the tool an eight out of ten.
