Authentication & abuse controls
Verified email flows, OAuth, password recovery, MFA, Turnstile, Redis rate limits, and authentication event history.
MIT licensed · Production-minded
The plumbing is done. Build the product.
Authentication, organizations, Stripe billing, a credit ledger, private storage, background jobs, and a separate admin console—connected through one enforceable architecture.
Replay-safe moneyIdempotent checkout, webhooks, ledger grants, and refunds.
Organization-firstBilling, members, storage, and credits share one tenant boundary.
No-leak errorsCatalogued server failures resolve to localized browser copy.
Tests as architectureLayering, auth gates, replay behavior, and DB constraints are executable.
A backbone, not a demo.
The starter focuses on the parts that become expensive after launch: ownership, retries, reconciliation, operational access, and explicit boundaries.
Billing & entitlements
Stripe Prices drive checkout; lifecycle webhooks update organization subscriptions and capability checks.
Credit accounting
An append-only, traceable ledger connects purchases, grants, task spending, reversals, and balances.
Organizations & teams
Personal and shared workspaces, invitations, roles, last-owner protection, and pooled resources.
Storage & jobs
Private S3-compatible uploads, signed access, lifecycle state, and a durable retryable database queue.
Operator console
A separately deployed admin application with MFA, read/write roles, audit events, and billing visibility.
One direction through the codebase.
Routes translate HTTP. Services own invariants. Models own queries. The database owns constraints. Tests stop those boundaries from quietly dissolving.
Routes
Authenticate, validate, and translate HTTP into a business operation.
Services
Coordinate invariants, idempotency, authorization, and side effects.
Models
Provide typed, tenant-aware persistence behind one query boundary.
Database
Enforce uniqueness, ownership, references, and durable state transitions.