Engineering Notes — How SaaSQuickStart Is Built
Deep-dive engineering notes on how SaaSQuickStart works internally — webhook delivery, multi-tenant data isolation, and more. Written from the real code.
- System Architecture — SaaSQuickStart Engineering — The architecture of SaaSQuickStart: entry points, the request lifecycle through the middleware chain, the backend module map, the frontend provider stack, and the key flows.
- Auth Token Lifecycle & Silent Refresh — SaaSQuickStart Engineering — How SaaSQuickStart renews expired JWT access tokens invisibly: a 30-min access token, a 7-day rotating refresh token, and concurrent requests queued behind a single refresh in client.ts.
- Billing Subscription Lifecycle — SaaSQuickStart Engineering — The six-state subscription machine (none/active/canceling/paused/past_due/canceled) that governs paid access, and the Stripe/LemonSqueezy events that drive each transition.
- The Document Pipeline — SaaSQuickStart Engineering — How SaaSQuickStart turns a file into reviewed, structured data: OCR and LLM field extraction as separate paid jobs, credits charged once and only after a result is saved, and the guardrails around private documents and deletion.
- Multi-Tenant Data Isolation — SaaSQuickStart Engineering — How SaaSQuickStart keeps one customer's data from another: two independent layers — membership-checked tenant resolution plus a per-query tenantId filter, guarded by a CI audit.
- Webhook Delivery — SaaSQuickStart Engineering — How SaaSQuickStart delivers signed webhooks: HMAC-SHA256 signatures, SSRF-guarded transport, a 10s timeout, and durable retries (1m/5m/30m) that survive a restart.