From daffy0208-ai-dev-standards
Choose deployment strategy and infrastructure. Use when deciding where to deploy applications, setting up CI/CD, or configuring production environments. Covers Vercel, Railway, AWS, Cloudflare Workers, and Docker.
npx claudepluginhub joshuarweaver/cascade-content-creation-misc-1 --plugin daffy0208-ai-dev-standardsThis skill uses the workspace's default tool permissions.
Choose the right deployment strategy for your application scale and requirements.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Choose the right deployment strategy for your application scale and requirements.
Start simple, scale when needed. Don't over-engineer infrastructure for 10 users that won't arrive for months.
Cost: $0-$20/month Time to Deploy: 5-15 minutes Best for: MVPs, prototypes, side projects, marketing sites
Recommended Platforms:
Vercel (Next.js, React, static sites):
Netlify (Static sites, Jamstack):
Railway (Full-stack, databases):
Cloudflare Pages (Static + Workers):
Cost: $20-$500/month Time to Deploy: 1-4 hours Best for: Validated products, growing startups, paid customers
Recommended Platforms:
AWS Amplify (Full-stack web apps):
Google Cloud Run (Containerized apps):
Fly.io (Distributed apps):
Render (Simpler alternative to AWS):
Cost: $500-$5,000+/month Time to Deploy: 1-4 weeks Best for: High traffic, enterprise, compliance requirements
Recommended Platforms:
AWS ECS (Containers, no Kubernetes complexity):
AWS EKS / Google GKE (Kubernetes):
DigitalOcean App Platform (Mid-tier simplicity):
Static site (HTML, CSS, JS): → Vercel, Netlify, Cloudflare Pages
Next.js app: → Vercel (best integration), Netlify
React/Vue/Angular SPA: → Vercel, Netlify, Cloudflare Pages
Node.js API: → Railway, Render, Fly.io, AWS Amplify
Python API (FastAPI, Flask, Django): → Railway, Render, Fly.io, Google Cloud Run
Go/Rust API: → Fly.io, Railway, Google Cloud Run
Full-stack (Frontend + Backend + DB): → Railway, Render, AWS Amplify
Microservices: → Fly.io, Google Cloud Run, AWS ECS
No database: → Vercel, Netlify, Cloudflare Pages
Serverless database (PostgreSQL, MySQL): → Railway, Render (integrated), AWS RDS, Supabase
Redis/caching: → Railway, Render, AWS ElastiCache, Upstash
MongoDB: → MongoDB Atlas, Railway, AWS DocumentDB
<100 users (MVP): → Free/cheap tiers: Vercel free, Railway $5
100-1,000 users: → Vercel Pro ($20), Railway ($20-50), Render
1K-10K users: → Railway ($50-100), AWS Amplify, Cloud Run
10K-100K users: → AWS Amplify, Cloud Run, Fly.io ($100-500)
100K-1M users: → AWS ECS, GKE, dedicated servers ($500-5000)
Single region (US/Europe): → Any platform
Global (low latency worldwide): → Cloudflare Pages/Workers, Vercel Edge, Fly.io (multi-region)
China/Asia: → Cloudflare, Fly.io Hong Kong, Alibaba Cloud
Compliance (HIPAA, SOC 2, GDPR): → AWS, Google Cloud, Azure (compliance certifications)
Long-running jobs (>15 min): → Railway, Render Background Workers, AWS ECS
WebSockets/real-time: → Railway, Render, Fly.io, AWS ECS
High compute (video processing, ML): → AWS ECS/EKS, Google Cloud Run, dedicated GPUs
Platforms: Vercel, Netlify, Railway, Render
Setup (5 minutes):
npm run builddist or .nextEnvironment Variables:
DATABASE_URL=postgresql://...
API_KEY=secret_key
NODE_ENV=production
Preview Deployments:
Use when: Custom tests, security scans, multi-stage deploys
# .github/workflows/deploy.yml
name: Deploy to Production
on:
push:
branches: [main]
jobs:
test:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: actions/setup-node@v3
with:
node-version: '18'
- run: npm ci
- run: npm test
- run: npm run lint
deploy:
needs: test
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v3
- uses: amondnet/vercel-action@v20
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.ORG_ID }}
vercel-project-id: ${{ secrets.PROJECT_ID }}
vercel-args: '--prod'
Features:
Pipeline Stages:
Build → Test → Security Scan → Stage Deploy → Integration Tests → Prod Deploy
Tools:
Stack: Next.js (Vercel) + API (Railway/Supabase)
Pros: Fast, cheap, scales easily Cons: Not suitable for real-time or server-heavy apps
Frontend (Vercel) → API (Railway) → Database (Supabase)
Stack: Vercel Functions + Serverless DB (Supabase/PlanetScale)
Pros: Zero server management, pay per use Cons: Cold starts, vendor lock-in
Frontend (Vercel) → Edge Functions (Vercel) → Serverless DB
Stack: Railway (Node.js + PostgreSQL)
Pros: Simple, everything in one place Cons: Single point of failure
Railway: Node.js API + PostgreSQL + Redis
Stack: Multiple Cloud Run services + Cloud SQL
Pros: Independent scaling, fault isolation Cons: Complex, higher cost
Frontend (Vercel) → Service 1 (Cloud Run) → Database
→ Service 2 (Cloud Run) → Queue
Total: $0-5/month for MVP
Simple marketing site: → Vercel + Contentful CMS
SaaS MVP: → Next.js (Vercel) + Supabase (DB + Auth) + Stripe
Internal tool: → React (Netlify) + FastAPI (Railway) + PostgreSQL (Railway)
Mobile app backend: → FastAPI (Cloud Run) + Cloud SQL + Firebase Auth
E-commerce: → Next.js (Vercel) + Shopify/Stripe + PostgreSQL (Supabase)
Related Skills:
frontend-builder - For building apps to deployapi-designer - For API architectureperformance-optimizer - For optimizing deployed appsRelated Patterns:
META/DECISION-FRAMEWORK.md - Platform selection guidanceSTANDARDS/architecture-patterns/deployment-patterns.md - Deployment architectures (when created)Related Playbooks:
PLAYBOOKS/deploy-to-vercel.md - Vercel deployment guide (when created)PLAYBOOKS/setup-cicd.md - CI/CD setup procedure (when created)