I shipped my first AWS + Vercel product in 7 days during a Meta attribution crisis 👋

Hi dev.to 👋

I'm Andres. Long-time builder, first-time dev.to poster. (Pretty sure I should have done this years ago.)

Just shipped Ad Engine — a 24/7 AI ad-ops monitoring tool for DTC telehealth brands — in 7 focused days for the H0 hackathon. The build had teeth because there was a real reason for it: on February 14 this year, Meta enforced new health-data restrictions that killed pixel-based conversion tracking for the entire DTC telehealth space. At 11 PM the day it happened, I watched a single ad set at Bliss Health burn $4,200 with no alert. The tool I wanted didn't exist, so I built it.

The stack

• Amazon Aurora PostgreSQL Serverless v2 (us-east-2, 0.5–1.0 ACU)




• Next.js 16 — App Router, Server Components, Server Actions




• Vercel Fluid Compute + Cron — 15-min polling cadence on Meta + Google APIs




• Claude Sonnet 4.6 with schema-enforced structured output via Zod + AI SDK Output.object()




• Drizzle ORM with postgres-js driver

What I'd love your thoughts on

The juiciest engineering decision was rejecting DynamoDB for Aurora Serverless v2. The workload turned out to be multi-entity joins + time-series windowing for 7-day baselines, and DynamoDB's GSI-design tax made that worse than a relational engine's OVER ROWS BETWEEN 336 PRECEDING window function.

Wrote the full decision matrix + schema + SQL + the postgres-js Fluid Compute connection-pool pattern prepare: false, max: 1) here:

→