mirror of
https://github.com/better-auth/better-auth.git
synced 2026-05-24 16:11:53 -05:00
docs: simplified comparisons page (#2867)
This commit is contained in:
@@ -9,29 +9,25 @@ Here are non detailed reasons why you may want to use Better Auth over other aut
|
||||
|
||||
### vs Other Auth Libraries
|
||||
|
||||
- You need more features from your auth library.
|
||||
- We support almost all frameworks out of the box.
|
||||
- You need advanced features like two-factor authentication, multi-tenancy, multi-session, admin tools, rate limiting, etc.
|
||||
- You want to have more control over your auth flow.
|
||||
- You prefer more comprehensive documentation.
|
||||
- You like the idea of a plugin system to extend the library.
|
||||
- You want to use a library that is actively maintained and has a growing community.
|
||||
- **Framework agnostic** - Works with any framework, not just specific ones
|
||||
- **Advanced features built-in** - 2FA, multi-tenancy, multi-session, rate limiting, and many more
|
||||
- **Plugin system** - Extend functionality without forking or complex workarounds
|
||||
- **Full control** - Customize auth flows exactly how you want
|
||||
|
||||
### vs Self Hosted Auth Server
|
||||
- You want to keep your users in your main database (the same database as your app).
|
||||
- You need more control over your auth flow.
|
||||
- You don't want the hassle of self-hosting your auth server.
|
||||
- And there's a high possibility that we already cover the features you need. Additionally, you can always extend it using our plugin system.
|
||||
### vs Self-Hosted Auth Servers
|
||||
|
||||
### vs Managed Auth Services (Paid)
|
||||
- **No separate infrastructure** - Runs in your app, users stay in your database
|
||||
- **Zero server maintenance** - No auth servers to deploy, monitor, or update
|
||||
- **Complete feature set** - Everything you need without the operational overhead
|
||||
|
||||
- You don't want to give up user data to a third party.
|
||||
- You want a single source of truth for your users.
|
||||
- You don't want to pay for every user.
|
||||
- You want to keep your users in your own database (the same database as your app).
|
||||
### vs Managed Auth Services
|
||||
|
||||
### vs Roll Your Own Auth
|
||||
- **Keep your data** - Users stay in your database, not a third-party service
|
||||
- **No per-user costs** - Scale without worrying about auth billing
|
||||
- **Single source of truth** - All user data in one place
|
||||
|
||||
- You don't want to maintain a lot of code that isn't your core business.
|
||||
- You want to delegate the security to a community of people who probably care more than you do.
|
||||
- We probably cover most of the features you'll need, and you can always extend it using our plugin system.
|
||||
### vs Rolling Your Own
|
||||
|
||||
- **Security handled** - Battle-tested auth flows and security practices
|
||||
- **Focus on your product** - Spend time on features that matter to your business
|
||||
- **Plugin extensibility** - Add custom features without starting from scratch
|
||||
Reference in New Issue
Block a user