---
title: "Comment by jai takkar on \"Effortless Next.js App Authentication using Clerk Auth\" | Hashnode"
description: "Are there any limitations or potential security concerns with Clerk Auth? 🔒"
url: "https://hashnode.com/posts/effortless-nextjs-app-authentication-using-clerk-auth/64aec0339b6f7761817ead41/comment/64aece07de430d632252a1ee"
---

[Discussion](https://hashnode.com/posts/effortless-nextjs-app-authentication-using-clerk-auth/64aec0339b6f7761817ead41)

Comment [Effortless Next.js App Authentication using Clerk Auth](https://hashnode.com/posts/effortless-nextjs-app-authentication-using-clerk-auth/64aec0339b6f7761817ead41)

[jai takkar](https://hashnode.com/@Mage6679)

[Jul 12, 2023](https://hashnode.com/posts/effortless-nextjs-app-authentication-using-clerk-auth/64aec0339b6f7761817ead41/comment/64aece07de430d632252a1ee)

Are there any limitations or potential security concerns with Clerk Auth? 🔒

[Arjun](https://hashnode.com/@dotarjun)

[Jul 12, 2023](https://hashnode.com/posts/effortless-nextjs-app-authentication-using-clerk-auth/64aec0339b6f7761817ead41/comment/64aece07de430d632252a1ee#reply-64aecf9dde430d632252a231)

One is that your authentication logic moves out of your app and into Clerk's systems. This can make debugging and customization harder compared to a self-managed auth system.
