IdeaWell

Project ideas from Hacker News discussions.

From Supabase to Clerk to Better Auth

Original Article

Hacker News Discussion

📝 Discussion Summary (Click to expand)

3 Dominant Themesin the Discussion

1️⃣ Own your auth data – self‑hosted libraries win

"you get all of your auth data in your own db in 1 cli command. You are not tied to any on db provider." – azyc
"Better auth stores everything in your DB. It’s the equivalent of Django auth for the Typescript ecosystem." – jonas21

2️⃣ SaaS‑based auth brings lock‑in, reliability worries, and hidden costs

"Clerk is just a mess… their JS blob is slow, they’re cramming Web3, Stripe, etc., and debugging their libraries is an unreliably obfuscated mess." – cyberax > "I’ve been through the exact same migration path and I'm so incredibly happy with Better Auth… It just works." – vevoe

3️⃣ Modern auth libraries let you focus on core product, not auth plumbing

"We were able to add a plugin to allow auth via iframe postMessage and everything worked seamlessly." – supermdguy
"Laravel (or Rails, Django, ASP.NET Core) can provide all those auth features OOTB, free and lives in my database wherever I want." – giancarlostoro

These three threads capture the community’s main take‑aways: prefer libraries that keep data under your control, be skeptical of vendor‑managed auth services that introduce complexity and downtime, and leverage today’s mature open‑source frameworks for simpler, faster development.

🚀 Project Ideas

AuthShift: Multi-Provider Auth Migration & Orchestration CLI

Summary

  • A CLI that automates migration of user tables and auth configurations between SaaS providers (Clerk, BetterAuth, Auth0) while preserving SSO, roles, MFA, and other custom settings.
  • Core value: One‑click, zero‑downtime provider switch with full data integrity and rollback safety.

Details

Key Value
Target Audience Backend engineers, SaaS founders, DevOps teams looking to avoid vendor lock‑in
Core Feature Multi‑provider import/export, schema mapping, validation checks, CI/CD integration
Tech Stack Node.js/TypeScript, Prisma ORM, PostgreSQL, Docker, OpenAPI
Difficulty Medium
Monetization Revenue-ready: Subscription ($9/mo per user)

Notes

  • HN commenters repeatedly asked for a way to escape Clerk/BetterAuth and cited migration pain – this tool directly answers that need.
  • Potential for discussion: open‑source contribution model, CI pipeline integration, community‑driven provider adapters.

OfflineAuth SDK for Mobile (BetterAuth Offline)

Summary

  • An SDK that enables offline‑first authentication on iOS/Android by persisting JWT refresh tokens and allowing token issuance without network connectivity, fixing the lack of offline support highlighted in discussions.
  • Core value: Seamless fallback to cached credentials with automatic token refresh, eliminating crashes when connectivity is lost.

Details

Key Value
Target Audience Mobile developers, cross‑platform engineers, early‑stage startups
Core Feature Token caching, offline login flow, automatic sync on reconnect, JWT refresh handling
Tech Stack Swift, Kotlin, React Native, Node.js backend, SQLite
Difficulty Medium-High
Monetization Revenue-ready: Freemium core, managed service $15/mo

Notes

  • Directly addresses a question raised by users about “offline auth on mobile” – a clear unmet need.
  • Community interest evident from repeated mentions of offline support gaps in auth providers.

AuthVigil: Audit & Versioning Service for Auth Providers

Summary

  • A SaaS that continuously logs every change to auth configuration, user role mappings, and provider credentials, giving searchable audit trails and one‑click rollback for services like Clerk.
  • Core value: Guarantees compliance and rapid troubleshooting by preserving immutable version history of all auth settings.

Details

Key Value
Target Audience Security engineers, ops teams, product managers using SaaS auth solutions
Core Feature Immutable audit log, change monitoring, webhook alerts, UI for rollback
Tech Stack Python (FastAPI), PostgreSQL, Redis, Grafana, Docker
Difficulty Low
Monetization Revenue-ready: Pay‑as‑you‑go $0.01 per audit entry (tiered pricing)

Notes

  • Mirrors concerns expressed about Clerk’s missing audit logs and reliability incidents – users would value transparent versioning.
  • Potential for discussion: integration with existing CI/CD pipelines, open‑source audit log format, extensibility for custom policies.

Read Later