Website and backend with a separate auth service
FreeSystem map@rabbinatix/login-auth-service-architecture by Rabbinatixupdated Oct 13, 2026
Logins live in their own service. The website gets a token there; the backend checks the token with it.
3 systems and 8 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
3 connections · 8 APIs
- Web App → Auth Service
POST /api/v1/auth/registerCreate an accountPOST /api/v1/auth/loginLog in with email and passwordPOST /api/v1/auth/logoutLog outPOST /api/v1/auth/refreshSwap a refresh token for a new sessionPOST /api/v1/auth/password-resetEmail a password reset link
- Web App → Backend API
GET /api/v1/meThe signed-in userGET /api/v1/itemsThe user’s items
- Backend API → Auth Service
POST /api/v1/tokens/verifyCheck a token and say whose it is
Systems (3)
Web App
The website people use.
Auth Service
Sign up, log in, tokens. Nothing else.
Backend API
The app’s data, for signed-in users.
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
Versions
