SaaS with subscriptions and email
FreeSystem map@rabbinatix/saas-billing-architecture by Rabbinatixupdated Oct 13, 2026
A web app whose backend bills with Stripe (and hears back through a webhook) and sends email through a mail API.
4 systems and 10 APIs. Every API is declared on both sides, so every contract starts healthy. Rename or change anything once it is on your map.
4 connections · 10 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 outGET /api/v1/meThe signed-in userPOST /api/v1/billing/checkoutStart a subscription checkoutGET /api/v1/billing/subscriptionThe current plan
- Backend API → Stripe
POST /v1/checkout/sessionsCreate a checkout pagePOST /v1/customersCreate a customer
- Stripe → Backend API
POST /api/v1/webhooks/stripeStripe tells us a payment or subscription changed
- Backend API → Email API
POST /v3/mail/sendSend an email
Systems (4)
Web App
The product people pay for.
Backend API
Accounts, plans and billing.
Stripe
Subscriptions and invoices.
Email API
Sends email, like SendGrid or Postmark.
A system you already have under the same name is used, not copied. Outside APIs don't count towards your plan.
Versions
