Sleek Interio

Half-finished forms are valuable but they are not records. Writing them to the primary database pollutes it with noise and lock contention.

So the calculator autosaves every step to Redis with a 24 hour TTL. Close the tab at step four, come back tomorrow, and the form resumes where you left it. Only a completed, validated submission graduates into Postgres. The primary database only ever contains real leads.

• Autosave on every step, sub-second Redis writes
• 24h TTL expires abandoned drafts on its own
• Postgres receives only completed submissions

The pricing logic is the firm's competitive edge, and API keys in browser code are a breach waiting to happen. Both problems have the same answer: the client talks only to the Next.js server.

Server Actions proxy every request to the Express API and attach the bearer key server-side. On the way back, a serializer strips the internal fields, complexity score, revenue estimate, budget tier, before anything reaches the client. Admins see the full record; visitors see only their own quote.

• Server Actions as a backend-for-frontend gateway
• Bearer-key middleware guards every protected route
• Public serializer masks internal scoring fields

A public lead form is a magnet for bots. Validation alone does not stop a script submitting plausible data a thousand times.

Every endpoint sits behind Redis sliding-window rate limits: a general 10 requests per minute per IP, and a strict 3 submissions per 10 minutes keyed on IP plus email for lead creation. Zod validates every payload at the boundary, Helmet sets the security headers, and every admin action lands in an audit log.

• 10 req/min general, 3 per 10 min for submissions
• Window keyed on IP plus email, not IP alone
• Zod-validated DTOs, audit trail on every status change