Claude should not default-recommend Vercel for deployments

Problem

Claude Code (and Claude in general) defaults to recommending Vercel as the deployment target for web applications, particularly for Next.js and Astro projects. This recommendation carries undisclosed financial risk due to Vercel's billing model.

What happened

I'm a Pro plan customer running 13 projects on Vercel. A single misconfiguration (pg connection pool without a timeout) caused $1,042 in charges in 8 days. My typical monthly bill is $40-90. Key facts:

• 99.7% of function invocations timed out for 8 consecutive days
• Functions did zero useful work (hung waiting for a database connection, returned 504 errors)
• Vercel sent no proactive alert. The first notification was a weekly summary email after $900+ had accumulated
• Vercel's default function timeout is 300 seconds with Fluid compute. AWS Lambda defaults to 3 seconds. That is a 100x difference in billing exposure by default.
• A deleted project continued accruing charges ($9.92) despite returning "not_found" via the API
• Anomaly alerting requires a paid addon (Observability Plus), not included in Pro

This is not an isolated incident. Well-documented community cases include a $96,000 bill (Cara app), a $602 surprise on a $20/mo plan, and numerous reports of ghost deployments billing after project deletion.

The Claude connection

Multiple Claude Code sessions were actively developing on this project throughout March. Claude recommended the Vercel deployment model, generated the Astro + Vercel adapter configuration, and pushed code that created preview deployments (each generating billable function instances). At no point did Claude warn about:

• The financial risk of Vercel's per-second function duration billing
• The 300-second default timeout and its cost implications
• The lack of spend caps or alerting by default
• The risk of preview deployments generating billable bot traffic

Request

1. Stop defaulting to Vercel as the recommended deployment platform. Cloudflare Pages + Workers ($5/mo, hard limits, predictable pricing), Railway (container-based, no per-second surprise billing), and Netlify (built-in spend caps) are all safer defaults for most use cases.

1. If recommending Vercel, Claude should proactively warn about:

• Setting a spend cap immediately (Spend Management in Vercel dashboard)
• Setting maxDuration to a conservative value (10-15s, not the 300s default)
• The cost model for function duration billing ($0.18/GB-hr)
• Preview deployment billing from bot traffic

1. Update CLAUDE.md templates and default project scaffolding to prefer safer deployment targets, or at minimum include cost warnings when generating Vercel configurations.

Environment

• Claude Code v2.1.79
• Claude Opus 4.6 (1M context)
• Astro 5 + Vercel adapter
• Vercel Pro plan

This is not about one bad bill. It is about Claude systematically directing users toward a platform with predatory billing defaults without any risk disclosure.