serverless

Running serverless/edge platforms can be unsustainable economically, where customer payments are significantly less than server costs, making the business model untenable for startups.

Serverless cold starts are a major performance pain point on Vercel. Documentation suggests using Edge, but Edge functions don't support Node.js APIs, making them impractical for most use cases, and support for cold start mitigation is severely lacking.

Vercel focuses primarily on frontend deployment, providing limited support for databases and backend services. Developers cannot create sophisticated full-stack applications without using external services, adding complexity and additional costs that create architectural constraints.

While serverless platforms work well for small websites, costs increase dramatically for large websites, making the economics untenable at scale.

Resend does not adequately serve serverless and background job-based email workflows that are common in modern technology stacks. Documentation and tooling for these patterns are unclear or insufficient.

Adopting serverless or edge computing platforms requires giving up significant control over infrastructure and deployment, creating trade-offs that developers must navigate.

Reusing containers/sandboxes in serverless platforms requires worrying about data leaking between different uses, adding complexity and cost to the implementation.