vercel-optimize skill just roasted my $47 ISR bill

Ran the Vercel Optimize skill against our side project Friday night. It pulled real metrics and pointed at two ISR routes that were basically never caching — every hit was a full regenerate.
Also flagged an Edge Function that was doing a Postgres roundtrip on every request for a config JSON that changes once a week. Moved that to a 1h cache and the preview already looks less embarrassing.
Anyone else tried this on a real project, or is it mostly demo-ware?


5 comments
Join the discussion
Log in to comment.
ran something similar on our marketing site last week. skill spat out "~$31/mo regenerating the same blog slug every hit" and i almost didn't believe it until i checked the vercel invoice.
moved those routes to a 24h revalidate + one edge config pull. not glamorous but the bill stopped looking like a growth experiment gone wrong. curious if anyone's seeing false positives where it flags stuff that actually needs to stay dynamic?
got a false positive on a webhook status page that legit needs to stay dynamic — skill yelled about "~$12/mo never caching" but that route hits stripe every time on purpose.
i started tagging routes with a
// vercel-optimize: keep-dynamiccomment before running it. not official, just a sticky note for myself so i don't "fix" the wrong thing at 1am.ha, that postgres-on-every-request pattern. i had the same on a stripe webhook status page. skill told me it was ~$18/mo just for looking up a boolean. moved to kv, cancelled the panic.
did it actually write the code for you or just dump recommendations?
for me it mostly dumped ranked fixes + file paths. i still had to tell cascade to apply the cache headers. worked though, preview deploy dropped like 40% on those routes overnight
client side project last month — skill flagged a docs route regenerating on every /changelog hit. vercel dashboard said ~$22/mo for what was basically a markdown folder.
i still had to write the revalidate myself; the skill ranked the leaks but didn't open the PR. worth the friday night though. that edge postgres lookup you mentioned is the one that keeps showing up on my invoices.