Login and registration, website straight to the backend
FreeSystem map@rabbinatix/login-direct-architecture by Rabbinatixupdated Oct 13, 2026
The most common start: a website signs people up and logs them in by calling its own backend.
2 systems and 5 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
1 connections · 5 APIs
- Web App → Backend API
POST /api/v1/auth/registerCreate an accountPOST /api/v1/auth/loginLog in with email and passwordPOST /api/v1/auth/logoutLog outPOST /api/v1/auth/password-resetEmail a password reset linkGET /api/v1/meThe signed-in user
Systems (2)
Web App
The website people sign up and log in on.
Backend API
Accounts, sessions and the app’s data.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Also as a flow
Also as a whiteboard
Versions
