Cheap but manual     vs    Expensive but automated
─────────────────────────────────────────────────
Self-hosted DB            Managed database
Manual deployments        CI/CD platform
DIY monitoring            SaaS observability

Rule: Automate only when manual becomes painful.
Your time has value, but cash constraints are real.

## Infrastructure Budget: [Project Name]

### Compute
- Web server: $X/month
- Background workers: $X/month
- Serverless functions: $X/month

### Data
- Database: $X/month
- Object storage: $X/month
- Redis/cache: $X/month

### Services
- Email: $X/month
- Error tracking: $X/month
- Analytics: $X/month

### Operations
- Domain: $X/year ÷ 12 = $X/month
- SSL: $0 (Let's Encrypt)

### Total: $X/month
### With 2x buffer: $X/month

Users    Requests/mo    Est. Cost
─────────────────────────────────
100      10k            Free tier
1,000    100k           $20-50
10,000   1M             $100-200
100,000  10M            $500-1000

Note: Costs vary wildly by architecture.
These are rough estimates for typical web apps.

Static-first
- SSG/SSR to static files
- CDN-served (often free)
- API only for dynamic data

SQLite + Litestream
- Single-file database
- Replicated to S3 ($0.023/GB)
- No managed DB costs

Serverless for bursty
- Pay per request
- Scale to zero
- Good for side projects with variable traffic

Always-on compute for variable traffic
- Kubernetes cluster (overkill for small apps)
- Multiple redundant servers (before you need them)

Managed services for simple needs
- Managed Redis for basic caching (use in-memory)
- Managed Kafka for simple queues (use Postgres)

Premium tiers before limits hit
- Upgrading "just in case"
- Features you don't use yet

Solo Project Stack ($0-20/month)
├── Frontend: Vercel/Cloudflare Pages (free)
├── Backend: Fly.io free tier or Railway
├── Database: Turso/Supabase/PlanetScale free
├── Auth: Built-in or Clerk free tier
├── Email: Resend free tier
├── Monitoring: Sentry + UptimeRobot free
└── DNS/CDN: Cloudflare free

Growth Stack ($50-100/month)
├── Frontend: Same (still free)
├── Backend: Fly.io/Railway paid ($10-20)
├── Database: Managed Postgres ($15-30)
├── Cache: Upstash Redis ($10)
├── Storage: S3/R2 ($5-10)
└── Monitoring: Basic paid tiers ($10-20)

Configure before you need them:
- 50% of expected budget: Notification
- 80% of expected budget: Warning
- 100% of expected budget: Alert
- 150%: Hard limit if possible

AWS
- Enable AWS Budgets
- Set billing alarms in CloudWatch
- Consider AWS Organizations for hard limits

GCP
- Set budget alerts
- Enable quota limits
- Use committed use discounts carefully

General
- Remove unused resources monthly
- Check for orphaned storage/volumes
- Review bills line by line monthly

Data transfer (egress)
- Often free in, expensive out
- CDN can reduce origin egress

Storage that accumulates
- Logs that aren't rotated
- Old backups not deleted
- Unused container images

Idle resources
- Dev/staging environments left running
- Load balancers with no traffic
- Reserved capacity unused

1. Delete unused resources
   - Old deployments
   - Test databases
   - Orphaned volumes

2. Right-size running resources
   - Drop to smaller instance
   - Reduce over-provisioned storage

3. Use spot/preemptible (where appropriate)
   - 60-90% discount
   - Good for stateless workers

4. Reserved instances (only if stable)
   - 30-60% discount
   - Requires commitment

Don't optimize prematurely:
- Traffic < 10k requests/day: Focus on building
- Cost < $50/month: Not worth the time
- Pre-product-market-fit: Features > cost

Do optimize when:
- Costs growing faster than revenue
- Hitting provider limits
- Architecture clearly wasteful

Best value: Fly.io, Railway, Render
- Simple deployment
- Generous free tiers
- Good developer experience

Best for static: Vercel, Cloudflare Pages
- Free for most use cases
- Built-in CDN
- Edge functions available

Best for full-stack: Supabase, PocketBase
- Database + auth + storage
- Single provider simplicity

Consider:
- AWS/GCP/Azure for complex needs
- DigitalOcean/Vultr for simple VPS
- Hetzner for best price/performance (EU)

Evaluate:
- Actual feature needs (not marketing)
- Egress costs for your traffic pattern
- Support quality for your tier