While working on modern web projects, I realized that setting up authentication, backend services, and databases separately takes a lot of time. That’s when I came across Anti-Gravity. It made the whole workflow much simpler by working smoothly with Supabase and Clerk.
Instead of spending hours configuring everything manually, I could focus more on building the actual project. The integration felt clean, beginner-friendly, and surprisingly fast. Whether you are building a SaaS product, dashboard, or personal project, Anti-Gravity helps reduce unnecessary setup work and keeps development organized.
Top comments (2)
@afkkrishna interesting stack choice. We went Supabase Auth instead of Clerk to avoid the dual-source-of-truth problem (Clerk user.id vs Supabase auth.uid in RLS policies). Curious how you handle the sync — do you mirror Clerk users into a public.users table, or rewrite RLS policies to reference Clerk JWT claims? The first felt fragile; the second was hard to debug.
That’s a fair point honestly. The Clerk + Supabase setup can definitely feel tricky because of the dual auth flow. In my case, I mainly use Clerk for authentication, user management, and subscriptions, while Supabase handles the database/backend side.
I also move pretty fast with AI-assisted development, so a lot of the integration and RLS setup becomes easier to manage and iterate on. I still review and customize the logic later, but overall Clerk has felt more flexible and production-ready for the kind of projects I build.