DEV Community

Atlas Whoff
Atlas Whoff

Posted on

Vercel vs AWS: When the Platform Tax Is Worth It

#devops #javascript #saas #beginners

The Platform Tax

Vercel charges more per compute-hour than AWS Lambda. This is not a coincidence—it's the business model.

You pay the platform tax in exchange for not paying the infrastructure tax: the time, expertise, and ongoing maintenance cost of managing AWS directly.

When is this trade worth it?

What Vercel Gives You 

# Deploy a Next.js app
git push origin main
# That's it. Vercel handles:
# - Build system (optimized for Next.js)
# - CDN (edge network in 70+ regions)
# - SSL certificates (auto-renewing)
# - Preview deployments on every PR
# - Environment variable management
# - Analytics and Web Vitals
# - Edge Functions (runs at CDN nodes)
Enter fullscreen mode Exit fullscreen mode

Infrastructure surface area you don't manage:

  • Load balancers
  • Auto-scaling
  • CDN configuration
  • SSL renewal
  • Server provisioning
  • Network security groups

Cost example (small SaaS):

  • Vercel Pro: $20/month
  • Equivalent AWS setup (ALB + EC2 + CloudFront + Route53 + ACM): $40-80/month + 10+ hours setup

At small scale, Vercel is often cheaper than AWS when you factor in time.

What AWS Gives You 

// Full control over your infrastructure
// But you build everything:

// VPC configuration
// Security groups
// ECS/EKS cluster setup
// Load balancer rules
// Auto-scaling policies
// CloudWatch dashboards
// IAM roles and policies
// Certificate Manager
// Route53 DNS
// ... 40 more things
Enter fullscreen mode Exit fullscreen mode

Where AWS wins:

  • Compliance requirements (SOC2, HIPAA, GDPR with specific data residency)
  • Extreme scale (millions of requests/day)
  • Complex infrastructure (databases, queues, ML pipelines)
  • Existing AWS expertise in the team
  • Cost optimization at high scale

The Hybrid Architecture Most Startups Use 

Vercel → Next.js frontend + API routes
AWS RDS → PostgreSQL database
AWS S3 → File storage
AWS SES → Transactional email
Upstash Redis → Rate limiting, caching, queues
Enter fullscreen mode Exit fullscreen mode

This gives you Vercel's DX for the application layer while using AWS managed services for the data layer—where AWS is cheap and not operationally complex.

When to Stay on Vercel

  • Solo founder or small team
  • Less than $50k MRR
  • No compliance requirements demanding specific infrastructure
  • Next.js application (Vercel is literally Next.js's creator)
  • Moving fast is more important than optimizing costs

When to Move to AWS

  • Enterprise customers requiring SOC2 or specific data residency
  • Monthly infrastructure bill > $500 on Vercel
  • Need services Vercel doesn't offer (ML training, complex queues, IoT)
  • Significant backend compute that doesn't fit the serverless model

Cost Comparison at Scale 

10k MAU SaaS:
  Vercel Pro: $20/month
  AWS equivalent: $30-50/month (but takes time to set up)
  → Vercel wins

100k MAU SaaS:
  Vercel: $150-400/month
  AWS (well-architected): $100-200/month
  → AWS starts winning, but needs ops expertise

1M MAU SaaS:
  Vercel: $2000-5000/month
  AWS: $500-1000/month
  → AWS wins, but you need a dedicated DevOps engineer
Enter fullscreen mode Exit fullscreen mode

The Decision Framework 

Ask yourself:
1. Do I have ops expertise? → No → Vercel
2. Do I have compliance requirements? → Yes → AWS or Vercel Enterprise
3. Is my infra bill > $500/month? → No → Vercel
4. Do I need services Vercel doesn't offer? → No → Vercel

Default: Start on Vercel. Migrate AWS services as specific needs arise.
Enter fullscreen mode Exit fullscreen mode

The worst outcome is spending weeks on AWS infrastructure when you should be building product. The second worst is being stuck on Vercel when you've outgrown it.

Start simple. Migrate deliberately.

Deploy to Vercel in one command with the Whoff Agents AI SaaS Starter Kit — includes Vercel config and AWS migration guide for when you need it.

Top comments (0)