A SaaS backend without a backend team

Most SaaS MVPs die in the auth-and-CRUD swamp. Here's the escape route.

1 · Auth in one click

Project Auth → Setup defaults (or ask your AI to call setup_auth). You get twelve endpoints: register, login, refresh, me, logout, verify-email, reset/change password, social OAuth, and passwordless request-otp / verify-otp for email or SMS codes. JWTs are signed per project.

2 · User-scoped data

Create your resources (e.g. workspaces, notes) and add an auth_scope relationship to the auth user. The gateway then filters every read by the logged-in user automatically; user A can never list user B's rows, and you wrote zero authorization code.

3 · Billing events

Add an inbound webhook endpoint with Stripe signature verification. Checkout events land in your project, can be forwarded to an internal endpoint, and trigger notifications.

4 · The client side

// login
POST /api/gateway/my-saas/login   { email, password }
→ { access_token, refresh_token, user }

// authenticated request
GET /api/gateway/my-saas/notes
Authorization: Bearer <access_token>   // returns ONLY this user's notes

5 · What you skipped building

Password hashing, token rotation, OTP rate limiting, lockouts, email templates, CORS, per-user data filtering, request logging, API docs. It's all in the platform; your time goes into the product.