#Vercel -> Railway Migration

Migrate Eko's hosting from Vercel to Railway, consolidating web apps and workers onto a single platform.

#Motivation

• Unified hosting: Railway natively hosts long-running workers alongside web apps
• Simpler ops: One platform, one billing surface, one deploy pipeline
• Claude Code integration: Railway's native MCP server integration

#Audit Summary

• 0 hard blockers, 5 config swaps (trivial), 1 code change (small)
• Not used (no migration needed): @vercel/blob, @vercel/edge-config, @vercel/analytics, AI Gateway, OIDC, Edge Functions, Vercel Firewall

#Contents

• Migration Plan — 5-phase migration with Cloudflare, Railway setup, cron migration, and cutover
• Environments Guide — Dev/preview/production workflow, PR environments, config as code, and efficiency methods
• TODO.md — Overall migration progress tracker
• worker-TODO.md — Worker deployment progress (formerly railway-worker-deploy project)
• worker-challenges/ — 6 challenge docs for worker deployment