hey I have built daptin for this and been running all of my projects with daptin as the sole backend server for data/authn/authz.
1. oauth/account management -> daptin can serve itself as a oauth provider as well as allow "login via oauth" on 3rdparty oauth servers. you get a full managed account including forget/reset password
2. permissions -> this involves more than rate limits, like who's the owner of what and you can manage permissions at user/guest/group level
3. handling payments -> fraud monitoring is usually part of the payment processor and you are not supposed to do much about it
and these days you can point your llm agent to the wiki to get most of the stuff done without needing to read the docs yourself. you just need a cheap vps (the $5 ones on digital ocean will be more than fine).
100x.bot is completely powered by daptin, canaster.in (work in progress, i am redoing the frontend in webgl) is also running on daptin. there are various internal company services which are running on daptin which i cannot name here.
almost any project which matures to requiring a user authn/authz (and there are always assets owned by users) i default to using daptin
I have hardened it a lot over the last 10 years, especially in terms of transaction/concurrency/security. happy to help you setting it up in your project. you can dm me ( x.com/phparth ) or leave an issue on the github repo
hey I have built daptin for this and been running all of my projects with daptin as the sole backend server for data/authn/authz.
1. oauth/account management -> daptin can serve itself as a oauth provider as well as allow "login via oauth" on 3rdparty oauth servers. you get a full managed account including forget/reset password
2. permissions -> this involves more than rate limits, like who's the owner of what and you can manage permissions at user/guest/group level
3. handling payments -> fraud monitoring is usually part of the payment processor and you are not supposed to do much about it
and these days you can point your llm agent to the wiki to get most of the stuff done without needing to read the docs yourself. you just need a cheap vps (the $5 ones on digital ocean will be more than fine).
https://github.com/daptin/daptin/wiki
https://github.com/daptin/daptin/wiki/Permissions
Thanks for the detailed reply. I'll definitely check this out. What type(s) of projects have you created that use this?
100x.bot is completely powered by daptin, canaster.in (work in progress, i am redoing the frontend in webgl) is also running on daptin. there are various internal company services which are running on daptin which i cannot name here.
almost any project which matures to requiring a user authn/authz (and there are always assets owned by users) i default to using daptin
I have hardened it a lot over the last 10 years, especially in terms of transaction/concurrency/security. happy to help you setting it up in your project. you can dm me ( x.com/phparth ) or leave an issue on the github repo