Clerk

1. Learn it

• ▸Authentication is 'who are you'; authorisation is 'what are you allowed to do'. Different jobs.
• ▸A session is the proof you stay signed in between page loads.
• ▸OAuth is signing in with Google or GitHub instead of a new password.
• ▸Never write your own password storage. Not once.

Cost: Free up to a few thousand users.

Split auth from permissions

A signed-in user opens another user's invoice. Which layer should stop them — sign-in or permissions?

1. 1Create a Clerk app, copy the keys into secrets, wrap your app in its provider.

MessyDev never signs you up, spends your money, or touches your accounts. You do that part.

4. Use it

Any app with user accounts where you do not want to build login yourself.