Ayush Anand: I build premium websites & full-stack products.I build premiumwebsites &full-stackproducts.

For engineers and hiring teams: the decisions behind the screens above. Security, money, AI, state and scale, each tied to a real build.

1. SecurityQuit Gambling

   Authorization lives in the database

   Row-level security on every Postgres table, and anonymous posts have their author nulled in a database view, so a real name never crosses the wire.

   17 / 17tables behind RLS
2. PaymentsQuit Gambling

   Money that can't be double-spent

   Razorpay signatures are verified server-side and session credits are deducted in one atomic statement, so concurrent bookings can't oversell a slot.

   Atomiccredit deduction
3. AI · RetrievalAI Chatbot

   RAG that stays in character

   Two-tier retrieval over a creator's whole video library, with HyDE query rewriting to beat semantic dilution, and a versioned persona that holds its voice.

   ~20%lower latency · 95%+ adherence
4. StateAI Chatbot

   2,000+ users, no crossed wires

   One Redis key per user: the app and the agent stay stateless and pass a session id, so every conversation stays isolated with sub-millisecond reads.

   2,000+isolated conversations
5. ReliabilityBareThreads

   Serverless without cold-start failures

   A cached database connection awaited inside each request keeps the API reliable on Vercel. Ownership checks close IDOR holes and every write is field-whitelisted.

   1 APIstorefront + admin, two origins
6. ScaleClanFlare

   APIs under real traffic

   At ClanFlare: normalized PostgreSQL / Prisma schemas with indexed hot queries, and REST APIs on Bun and Hono serving production traffic every day.

   ~40%lower latency · 10,000+ requests a day